This article is part of the R365 Financial Report Writer training. Click here for more information on R365 Financial Report Writer.
Only Users with the following Permissions will be build Custom Financial Reports and Templates:
Reporting → Custom Financial Reports → Reports → Create/Edit Custom Financial Reports
Reporting → Custom Financial Reports → Templates → View/Create/Edit/Delete CFR Templates
Templates vs. Reports
In the R365 Financial Report Writer you will find lists for both 'Templates' and 'Reports'.
Understanding the distinction between the two is essential for your success in using your Custom Financial Reports. Similar to the Report and Report Views relationship that exists in 'My Reports', each 'Template' will also have an associated 'Report' that can be ran.
In this relationship, you can think of the 'Reports' as saved views of the Template. Each time you create a new Template, an associated Report will be created as well. You can then create multiple Reports in addition to the generated Report file.
Each Template can have many Reports, while each Report can only belong to a single Template, as shown below:
Each Report can be setup to unique specifications with set parameters, such as which Legal Entity, Region or Concept is included. You can then save the Report and it will be available to be ran at any time going forward. Each time you then run that Report, it will be ran using the previously saved parameters.
Templates
The R365 Financial Report Writer includes several example Templates and Reports that can be ran 'out-of-the-box' once the service has been enabled and provisioned. These Templates are a great starting point for you as your start building your own Custom Financial Reports. As described above, each Template also has an associated Report that is generated once the Template is saved. Click here for more information on Creating and Editing Templates.
Working With Rows & Columns in Templates
Due to the complex nature of the R365 Financial Report Writer, we have split up the training for Templates, Rows and Columns. Each element is interconnected, and essential in the Report Building process. You can take a 'Row first, Column second' approach, or create your Columns first, followed by your Rows. Either way, both elements of the Template need to be addressed for you to have the desired result. Click the following links for more information on:
Creating Reports based off of Templates
The final step in creating your Reports is to make any parameter specifications, and save them as individual Reports. Click here for more information on Creating Reports.
Sharing Report Templates
When a Report is finalized, Partner Channel Users can share its Template across multiple instances. Click here for more information on Sharing Report Templates.
FAQ
What's the difference between a Template and a Report in the Financial Report Writer?
A Template defines the structure — its rows and columns. A Report is a saved, parameter-specific view of a Template that can be run repeatedly. Each Template can have many Reports, but each Report belongs to only one Template. Learn more about creating and editing Templates.
If I create a new Template, do I automatically get a Report too?
Yes. Saving a new Template automatically generates an associated Report. From there, you can create additional Reports off the same Template, each with its own saved parameters. Learn more about creating Reports.
Do I need to build rows before columns, or columns before rows?
Either order works. Both rows and columns must be configured before the Template produces the desired result. Learn more about building report rows.
Who has permission to build Custom Financial Report templates?
Only users with both the "Create/Edit Custom Financial Reports" and "View/Create/Edit/Delete CFR Templates" permissions can build them. Learn more about CFR Writer security.
Can we reuse a report template across multiple R365 instances?
Yes, but only Partner Channel users can share finalized report templates across instances. Learn more about sharing report templates.