AMEN.

This could really standardize our Crystal Reports structures across prospect assignment (relationship), actions and proposals based reports and sub-reports. Currently handling solicitor selections has to be structured differently by assignments versus by actions or proposals. The reporting could be quite streamlined and more consistent with this fix. It forces even reporting end users to experience the reports differently, because of ways that parameter fields need to be set up and filled in differently based on where the report is searching for a specific solicitor or group of solicitors. We're left trying to reason with end users by attempting to explain database structure differences to our colleagues. Not to mention having to save lists of solicitors inside Crystal Reports rather than being able to utilize the same formats possible with solicitor relationship reports/data structures. Inevitably those lists are only updated when a new solicitor points out that he/she isn't showing up on the report (because the solicitor's name has to be updated in the report itself on top of updating RE). If the canned reports don't provide what you need, then you're really up against a massive challenge to report on moves management across solicitor assignments to prospects, proposals and actions.