Dynamics Community Forum Thread Details

Financial Reporter Reporting format

I have extensive experience with FR in D365 finance. I have a question about formatting. I have a client that has multiple entities (32). In one report, they have 5 entities in a holding company. for their consolidated TB, I used a standard TB row and column definition and then built are porting tree for the 5 entities. The report works fine. However, the client wants the entities to report in columns and not rows. Typically, you would have the 5 entities in row format and drill down accordingly. The client wants the accounts down the 1st row, but entities across the top in separate columns. Is this possible?

Categories:

Dynamics 365 Finance

Hi CU01041802-0,

1) Issue
- The client has multiple legal entities and already uses a reporting tree to consolidate and display them in rows
- The requirement is to change the layout so that accounts are displayed in rows and entities are displayed across columns
- The standard approach in Financial Reporter typically places entities in rows via the reporting tree, not in columns
- The question is whether Financial Reporter supports displaying multiple entities as separate columns in a single report

2) Reason
- In Financial Reporter, the reporting tree is designed to expand data primarily across rows, not columns
- Column definitions are generally used for time periods or calculations rather than entity separation
- The system does not natively pivot reporting tree units into columns within a single report definition
- This limitation exists because entity segmentation is driven by the reporting tree structure, which inherently controls row expansion

3) Resolution
- Use the column definition with dimension filtering to manually assign each entity to a separate column by filtering on the company or legal entity dimension
- Create individual columns for each entity by specifying the company or dimension value in each column definition
- Maintain the row definition for accounts and avoid using the reporting tree for this specific requirement
- If consolidation logic is required, add additional calculated columns to sum or compare entity columns
- For large numbers of entities, consider whether usability and maintenance are manageable, as this approach does not scale well
- Alternatively, export the report to Excel and use pivoting if a more dynamic column layout is required
- As a best practice, use reporting trees for entity comparisons whenever possible, and only use column-based entity separation for specific presentation requirements

For a more detailed answer, please provide more information.

Rg,

Alexander

*Due to the complex and different possibilities of deploying Dynamics 365 I highly recommend not to setup the application without some expert/partner or support. (For more information contact me under anassl@inno-solutions.info or visit www.inno-solutions.de)

*The Information comes directly from the manufacturer or provider and are validated (not guaranteed) up to date of creation of the posting.

References: