Consider the following scenario. You try to print a report in Dexterity in Microsoft Dynamics GP. Report Writer is unable to resolve the relationship between two or more tables that are used in the report. In this scenario, a table hierarchy inconsistency error occurs.
Consider the following example:
Two tables are used in a report.
Table A is the main table.
Table B is linked to table A by a relationship.
If the relationship between these tables is removed, an error occurs when you print the report. The error occurs because Report Writer is unable to find a path down the hierarchy of the tables that are used in the report.
A Dexterity developer may have to add data from a new third-party table to the report. To do this as easily as possible, the developer follows these steps:
The developer adds a relationship from one of the original Microsoft Dynamics GP tables to the new table.
The developer attaches the new table to the report.
The developer drags the appropriate field into the report layout.
This technique works in Test mode in Dexterity. However, this method produces table hierarchy inconsistency errors as soon as the customization has been chunked and then added to a runtime environment.
Table relationships are used only to help Report Writer create links between tables. Table relationships are extracted during the chunking process only when one or more of the tables to which the relationships have been added are also extracted. Because the relationships have been added to one or more original Microsoft Dynamics GP tables, and because those tables were not extracted during the chunking process, the relationships that existed in Test mode do not exist in Runtime mode. Therefore, the error occurs.
Because of this situation, you must use a different method to add extra fields to the report. You can use one of the following methods:
Use Report Writer functions.
Duplicate Microsoft Dynamics GP tables definitions or Microsoft Business Solutions - Great Plains table definitions, and then change the main table on an alternative report.
Note The second method does not work when you are using temporary tables.
For more information about these methods and about table hierarchy inconsistency errors, click the following article number to view the article in the Microsoft Knowledge Base:
856203 Table hierarchy inconsistency errors
For more information about how to add third-party table information to Microsoft Dynamics GP reports, click the following article number to view the article in the Microsoft Knowledge Base:
857273 Adding third-party table information to Dynamics/eEnterprise temp table-based reports
For more information about how to link third-party tables by using Dexterity, click the following article number to view the article in the Microsoft Knowledge Base:
935380 How to link third-party tables to the SOP Blank Invoice Form report by using Dexterity for Microsoft Dynamics GP
For more information about how to improve the performance of Report Writer functions, click the following article number to view the article in the Microsoft Knowledge Base:
920830 How to improve the performance of user-defined Report Writer functions in Microsoft Dynamics GP 9.0 or in Microsoft Great Plains