Pro Trust Reports and Adding Branch Grouping
Posted: Mon May 09, 2011 10:06 pm
On many of the custom reports we are writing, the client would like to add grouping on Branch level which corresponds to a Profile.ProfileID --> Profile.Name Fields. For the Pro Trust Transaction Reports, if one wanted to do same reports yet group by branch in addition to Trust Account, what would be the proper way to join Profile.ID to the existing Report data?
For example, is TrustAccountsByProfile the correct Place to join ProfileID which would then enable Branch grouping in custom reports? It seems when I do this that I end up with Branches that are NULL which then causes problems for data on reports.
Is there any documentation that explains how all the Transaction, Adj, Ledger, etc Tables, Views, and Functions relate to each other? I have an idea how these tables relate to each other from existing reports, yet still a little bit unclear on reasoning of Adjustments, Transactions, Ledger Tables? Where I would think Transactions would be the main table to drive a report, I many times see Adjustments? If this is confusing let me know and I rephrase my question.
For example, is TrustAccountsByProfile the correct Place to join ProfileID which would then enable Branch grouping in custom reports? It seems when I do this that I end up with Branches that are NULL which then causes problems for data on reports.
Is there any documentation that explains how all the Transaction, Adj, Ledger, etc Tables, Views, and Functions relate to each other? I have an idea how these tables relate to each other from existing reports, yet still a little bit unclear on reasoning of Adjustments, Transactions, Ledger Tables? Where I would think Transactions would be the main table to drive a report, I many times see Adjustments? If this is confusing let me know and I rephrase my question.