Skip to main content

Reporting in Microsoft Dynamics F&O

     Today, I would like to share the reporting possibilities of D365 FO. There are various ways to report;


1. SSRS: Most of the SSRS reports are in the system ready to be used. But if there is a need to add a new report or a field/grouping etc to the current report, there is a need for a developer. This kind of reports are mostly used for internal needs and maybe sent to 3 rd parties in a proper shape.

2. Embedded Power BI: There are Power BI reports that are already created in the system and embedded in the modules. These reports are easy to use and is more focused on the visual. 

3. Power BI: Power BI reports can be created with the Power BI desktop application and easy to manage.

4. Management Reporter: Management Reporter tool is a user efficient tool that users can create reports  from COA, transactions, budget and dimensions. Users can create their own reports or use/change the ones that are already offered in the system like audit trail, balance sheet, cash flow etc.


5. Inquiries: These are forms that have data shown in grid view and can be exported to Excel. To find data through filtering options make it user friendly. So I use this functionality most common rather than the prepare a static report.

6. Excel: You can export data to Excel via Data Migration tools and can create the reports through. 

7: Electronic Reporting (ER): This is the most out of imagine tool which can be used for reporting with none or low code methodology. There is already set up reports but standard ones can be changed or new added.

8: Word Templates: This is not a reporting tool but for some documents can be managed as an out put to be sent to customers etc with the interaction of the user.

Labels:

Comments

Post a Comment

Popular posts from this blog

Manage ERP with Success - Blockers of Success

  To manage an ERP process with success is not easy at all. Even there has been processes that have been published by companies, it is mostly depend on the people. In this blog , I am going to share the reasons I see as blockers of during the projects. This is not a scientific measure but just my opinions. Sales Team:  ERP project starts from even before the sales documents are finalized. So company needs (not user/not management etc.) need to be understood wisely and to be checked if the tools can manage these needs and details need to be documented in the contract. Expectations:  Unfortunately, ERP is a software but not a hardware. So expectation management is very important. If it was a hardware, then you will be able to return and to document specific details.  Project Team:  By project team, mostly we understand the consultancy firm but project team does consist of also from customer project managers, users, power users etc. All project team need to be well...
Post a Comment
Read more

Allocation ways in D365 FO

 When we say allocations of expenses through accounts and dimension, there are various ways that can be used in D365 FO. In this blog you can find these ways and their differences from one to another. Cost Accounting Module:  If you do not need/require to post any transaction or you think that there will be too many transactions appear on voucher transactions, then you can use cost accounting module to report on your balances. This module works separate from the GL module. Data is transferred from GL module and you prepare your allocation rules in this module and do your reporting. also you can use this module for to report different versions. Allocation Rules : You can define allocation rules and within the period you want to use, system will allocate the balance to the relevant account and dimensions. The pros of this type is that, you can trigger and change the rules whenever you want to . The cons of this type is, you need to trigger each rule one by one, wait for the repo...
Post a Comment
Read more

Fast Track Recognized Solution Architect

      You may be a fast track recognized solution architect. Fast track is best practices to succeed on the project.(Called Success by Design) This process is documented by the fast track solution architects. When applied to be a fast track solution architect, evaluation is done by D365 engineering team.      Earning Criteria The architect must be nominated by the partner Must have a minimum of 5 years of experience with Dynamics CRM or ERP products Must have a minimum of 3 years of experience as a solution architect Must be the lead architect on at least 2 FastTrack governed customer implementation projects Must be responsible for the architecture and design of at least 2 FastTrack governed customer implementation projects Even if you can not fill these requirements above, you are still able to read the detailed documentation from the links below to succeed. https://docs.microsoft.com/en-us/dynamics365/fasttrack/implementation-guide/overview https://www.d3...
Post a Comment
Read more