Skip to main content

Why D365 F&O

 This question is usually asked and I see this question again couple of days ago in the community forum. So rather than to give an answer that has been explained technically, I would like to give that my answer for this question. 


1. Newness: While it is a Microsoft product, innovation is everywhere. The team is open for new technologies and improvements.

2. Documentation: Has a huge documentation , in which is updated and is easy to understand.

3. User Support: Supports users with the ticketing system.

4. Project Support: It is not only the programme that you but but also guides on how to process your project. Microsoft also cares on the project to success. This is why you can use Success by design documentations and LCS tools to decide your project models and processes.

5. Reporting Tools: There are various reporting tools that you can use within or outside of the programme. For internal use, I can give example of standard queries, SSRS reports, Excel add - ins, Management reporter tool as financial reporting and Embeded BI reports. For external reporting you can use the Power BI tools or any other sources. For the reporting you may use Dataverse, Azure Data Lake Storage Gen 2, BYOD functionalities.

6. Integration: You can integrate with 3 rd part easily, by using tools like Logicapp etc.

7. Power Platform: Can use Power Platform tools in which that have hundreds of solutions nd new solutions can be generated and embedded to the system. With Power Platform tools (Power BI, Power Automate, Power Apps, Power Virtual Agents) it is easy to manage flows, integrations, communication while it is generated with no code, low code technology.

8.Security: There is a huge security options that can be used a predefined or can be modified according to the need.

9. Dynamics 365  to Integrate: You may use other tools of D365 Umbrella as well whenever you need like Customer Engagement, HR etc.

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