> The drill down filters are working really well now. I have several > child list forms with embedded search forms and if you drill down from > them from a parent and there are no children, you just click on the > Display All button and voilà , the filter is removed and the first x > records are displayed. This is how I would expect it to work. Now, if > that list form (child) has a link back to the parent, I expect it to > work the same way, but it doesn't. If you drill back up to the parent > you drilled down from, a filter is set for that one parent record. > Clicking on the Display All button does not do anything. IMO, it should > behave just like the child does.
This is a bug that we'll fix in the next release. Thanks for catching it. > This brings me to another point about interface issues. (remember when > I am telling you this that I have been using Database Blocks in > production apps for over 3 years now, so I have a lot of feedback from > clients, and your drill downs/up behavior existed in DBB also). I think > we need to think about implementing at some point, some kind of inherent > breadcrumb trail that keeps track of these drill downs and allows the > user to see where he came from. If you have a complex database > structure and drill down several levels, it is easy for a user to get > lost. I recognize that you can just go over to the navbar menu and > select the top level list again, but it is not that apparent to users. > When I look at the navbar menu, I know how the database is structured, > so it makes sense to me. But your average user has no idea about data > modeling, and just wants to be able to go back and forth where he came > from by clicking on a breadcrumb. Sounds good. We have this on the V1.1 enhancement request list for discussion. > I actually implemented this behavior manually in an app, but it was a > major pita, and of course once you do all that regenerating that list is > off limits. I am just talking about module level lists for > breadcrumbs; not tracking every form they went to. Just so they can > select a point in the drilldown/up heirarchy. This sounds like a good candidate for adding in V1.1. Respectfully, Adam Phillip Churvis Member of Team Macromedia Advanced Intensive Training: * C# & ASP.NET for ColdFusion Developers * ColdFusion MX Master Class * Advanced Development with CFMX and SQL Server 2000 http://www.ColdFusionTraining.com Download CommerceBlocks V2.1 and LoRCAT from http://www.ProductivityEnhancement.com The ColdFusion MX Bible is in bookstores now!
