The Common Data Service(CDS) and Prospect to Cash integration between Dynamics 365 For Sales and Dynamics 365 For Finance & Operations

Dynamics 365 as a platform has so much to offer for your organization. Be it, best in class Talent management, Sales & Marketing, Customer Service management, Field Service, Project Service automation(PSA), Retail, Finance & Operations management, Microsoft Dynamics 365 offers purpose built apps for each of these areas for organizations of any size, ranging from 5 – 10 employees to large enterprise organizations with 10,000 + users.

All D365 Apps

Any Tier 1 cloud ERP in the market today will probably provide you pretty much the major functionalities, that you would expect for your organization. However, what sets Microsoft Dynamics 365 apart from the crowd, is the platform itself. Along with purpose built, best-of-breed apps and functionality for all areas of your businesses, you also get the tools, services, technology and the best of Microsoft cloud. A few to name are,

  • Common data Services for integrating business apps seamlessly.
  • Microsoft PowerApps to build mobile apps and extend business processes easily with minimal or no coding needed .
  • Microsoft Flow to automate routing, approvals, event based actions and notifications etc.
  • Power BI for incredibly stunning data visualizations and data intelligence.
  • Microsoft Azure technology stack, such as Azure functions, Artificial intelligence, Machine learning and much more.

Probably, no other business application platform provides this breadth of technology and functionality that Microsoft Dynamics 365 provides today.

In my last post, I explained the Common Data Service and the capabilities, what is coming etc. In this post today, I will share some of my findings of testing of Prospect to Cash integration scenarios between D365 Sales and D365 Finance & Operations.

One of the most common requirements of every ERP implementation is the integration of the Sales and marketing application with the Finance and operations application, to exchange business data such as Customer accounts, contacts, quotations, sales orders, products, invoices and more, so that the respective team members from different teams can get a 360 degree view of the customer’s data. The Microsoft Common data service aims to make it possible to integrate Dynamics 365 For Sales and Dynamics 365 For Finance and Operations out of the box, with various data project templates readily available for use.

Why Common Data Service?

You may argue why use Common Data Service to build integration between the apps/services  Vs. just leveraging OData Service or even Customer services (REST/JSON). Sure, you can always leverage either OData Service or the Custom Services to build your integrations between Dynamics 365 for Finance and Operations with other Dynamics 365 or other 3rd party services if you feel more comfortable with that approach. However, leveraging the CDS will give you advantages such as, voiding significant investments in writing custom integration that you need to maintain at a cost. Additionally surfacing business data from multiple business applications of your organization into CDS provides you the capability to create mission critical business intelligence using Power BI or even build custom apps with ease leveraging PowerApps.

Connection Sets in CDS:

Connection Sets defines what apps/services/systems you are going to connect for data exchange.

In PowerApps Admin center, I have already created my Connection Set, that establishes connection between my D365 For Sales and D365 For Finance and Operations apps. I also have done the Organization(s) mapping between these two apps, so that my data will surface in the required entities/organizations. Screenshot below shows the Connection set I have established. This is the first thing you need to setup, before you actually setup the data integration projects.

Connection Set

Data Integration projects in CDS: 

The Data integration projects defines what entities are being integrated/synced between the two apps defined in the Connection set. It contains the following information.

  • A template of the project (Predefined list of Data integration projects provided by Microsoft). Note: Currently, when you create a new data integration project, you are required to select a predefined template. This might change in future, where you can create your own mapping.

DataIntegrationProjects

  • Connection Set: Select the connection set you want to use within the data integrator project.

ConnectionSetInDataIntegrator

  • Organization Mapping: Since you could define more than one organization mapping within one connection set, you will can select a organization mapping that is applicable for the data integrator project.

DataIntegratorOrgMapping

  • Tasks: The data from the source app (D365 For Sales ) flows through the Common Data Service(CDS) to the Destination app(D365 For Operations). The tasks under the project contains the individual data field mapping between the entities in source app, CDS and destination app. It also contains the information such as how frequently the project should run (Manually Vs in Batch).

TaskDataMapping

DataIntegrationProjectRunSchedule

DataMapping

A default task comes automatically when you use a template to create a data integrator project, however, you can add your own tasks to the project, where you can map additional entities.

NewTaskUnderProjectCDS

 

Now that the Data Integrator Project and the Connection sets are configured, let us see how the Customer account data automatically flows from D365 Sales to CDS and then from CDS to D365 For Operations. In this case, I will just run the project manually ( I could set it to run automatically also)

Below screenshot shows the new customer I have setup in D365 For Sales.

NewCustomerInD365FroSales

I ran the data integrator project now manually in CDS admin center. In an ideal scenario, you would set it up to run automatically.

RunDataProject

When the project run successfully , you can see the detailed execution history which will tell that the data got successfully transmitted from source to destination (D365 Sales to D365 For Operations in this case). See screenshots below. This execution log helps you identify issues with data sync if any and take necessary actions.

Execution History1

Execution History2

Now that the execution happened successfully, let us go verify if the Customer account got successfully created in D365 For Operations.

D365CustomerAccount1

D365CustomerAccount2

This was my testing just for one scenario of passing Customer account data from D365 from Sales to Operations for this blog post. There are other templates that addresses the full picture of Prospect to cash scenario(See screenshot below) such as syncing,

  • Contacts from Sales to Operations
  • Products Operations to Sales”,
  • Quotes from Sales to Operations
  • Sales orders from Sales to Operations
  • Sales Invoice details from Operations to Sales.

IntegrationTemplates

I am continuing my testing of all these other entities to see how the overall data flow looks between Sales and Operations. I will share results and findings later 🙂

A few important Notes (Just my thoughts) about these out of the box integrations in D365  using Common Data Services:

  1. The Common Data Service platform seems to be very promising and is absolutely the right step in the right direction for enabling integrations and extension scenarios for Dynamics 365.
  2. With all honesty, CDS platform and functionality is fairly new and we are seeing new capabilities being added frequently. At this point, I have some important questions such as the below, for which I have still trying to get answers . I certainly need to learn more.
    • How does data updates/modifications/deletions sync.
    • Why do I need to select a template always to create a new data project.
    • What about notifications on execution history/results.
    • What happens to Bi-directional data update for an entity.
    • what is the data size/volume limitations for the Data integrator.
  3. I am also not very clear on the data security management of CDS . It looks like there are security roles and permissions that Microsoft provides in CDS, but looks like this needs to mature more.
  4. Right now, it seems like you can connect only Azure based services/apps. I don’t know how this will work with non-azure/external apps/services. At least, I have not tried yet.
  5. In my view, it does not look like the out of the box integration is ready for prime time, that customers can simply deploy and get going smoothly without issues. This will change significantly for sure in the months to come, when more features are released and bug fixes are out. I would imagine by the Fall of 2017, we should see a much robust out of the box integration using the CDS.
  6. Customers who are flexible to adopt the platform with a long term vision for success, can adopt the CDS integrations right away and go through the process of learning and will certainly get return on the investments in long term.

Thanks // Sandeep

Sandeep Chaudhury is a Dynamics AX enthusiast with over 10 years of experience in functional consulting, Solutions architecture and systems integration, with expertise in the areas of Professional services automation(Project Management and accounting), Financials Management, Services Management, Sales and Marketing, Human resource management, Travel and Expenses Management and Procurement & Sourcing modules of Microsoft dynamics AX ERP. He has experience working with the new Dynamics AX (AX 7), AX 2012 R3, AX 2012 R2 and more.

 

My favorite features from July 2017 update of Microsoft Dynamics 365 For Finance and Operations – Enterprise Edition

One of the most awaited releases of Dynamics 365 For Finance and Operations is now available (The July 2017 and Platform Update 8). Lot of new capabilities and exciting new features across all the functional modules and quite a few technology stack improvements!!In this post, I will highlight some of the most important new features that are my favorites so far, that I think are going to helpful for customers in big time.

First thing first! Starting with the July release, there is a change in the naming of the Dynamics 365 apps . Earlier we had “Dynamics 365 For Operations”, which basically represented the Enterprise edition of Dynamics 365 and “Dynamics 365 For Financials’ which represented the Business edition targeted for SMB customers.

Starting with the July release, the naming will be as below.

Dynamics 365 For Operations => Dynamics 365 For Finance and Operations – Enterprise Edition (For Enterprise Customers)

Dynamics 365 For Financials => Dynamics 365 For Finance and Operations – Business Edition  (Suitable For SMB Customers)

You should notice this name changes, when you login to the new version.

Default Landing Page

Here are some of my personal favorite features and functionality fro this latest update of Dynamics 365 For Finance and Operations.

Embedded PowerBI and Analytical Workspaces for all D365FO licensed users:

Microsoft Power BI is the backbone of Dynamics 365 for delivering critical business intelligence to all users of an organization with rich interactive visuals, dashboards and reports, with appropriate drill downs, data filter options etc. When Dynamics 365 was first released, users had the option of consuming preconfigured or customized Power BI dashboards and reports from their PowerBI online workspaces right into their workspaces within Dynamics 365. This is a great capability and allowed users to mash up data from Dynamics 365 or even from external data sources and then see them all together right on their workspaces. However, this required every users to have at least a free PowerBI.com subscription to be able to do this.

With the July 2017 update, Power BI Embedded services are integrated into Dynamics 365. Embedded Power BI is a Microsoft Azure Service that allows to embed the dashboards and reports directly into Operations workspaces of Dynamics 365. Embedded Power BI is an ideal way of presenting near real time data insights, with Direct Query to the Entity Story (Data warehouse for Dynamics 365). These embedded dashboards and reports are available for all users with the base license of Dynamics 365 for Finance and Operations and does not necessarily require the user to have a PowerBI.com subscription.

The diagram below shows the key difference between the PowerBI Online and PowerBI Embedded services.

power-bi-embedded-overview

The good news is, Microsoft has already shipped several out of the box PowerBI asset files within Life Cycle Service starting with the July 2017 release, which can be simply included in the Dynamics 365 deployment options to get instant access to readily available dashboards and reports across all major business areas. Below are some of the sample examples of these embedded Power BI dashboards and workspaces in Dynamics 365.

This slideshow requires JavaScript.

Prospect to Cash Integration between Dynamics 365 for Sales and Dynamics 365 for Finance and Operations using Common Data Services:

This one is a HUGE step forward!! Since Dynamics 365 launched back in February 2016, the Primary objective and goal for Microsoft was to combine the best of Dynamics CRM and ERP worlds and provide a unified experience to end users, so that they can advantage of best of breed functionalities within the Modular apps for Sales and Financials & Operations and still be able to integrate the data flow between these apps seamlessly to get a 360 degree view of their business. We have seen steps Microsoft has taken in last several months to get the Common Data Service (Azure Public Cloud data storage) Platform ready for prime time along with the supporting surrounding services such as Microsoft Flow and PowerApps. With the July release, these all are coming together as a first significant step towards truly unifying the CRM and ERP worlds. This is the beginning of the departure from the traditional custom 3rd party integrations between CRM and ERP.

The following key scenarios are supported currently with this integrations, primarily in the Supply Chain side. More to come in future. I have not got chance to test this end to end yet. Will share some details when I am able to test it in coming weeks.

  • Maintain accounts in Dynamics 365 for Sales and sync them to Finance and Operations as customers.
  • Maintain contacts in Dynamics 365 for Sales and sync them to Finance and Operations.
  • Maintain products in Finance and Operations and sync them to Dynamics 365 for Sales.
  • Create quotes in Dynamics 365 for Sales and sync them to Finance and Operations.
  • Generate sales orders in Dynamics 365 for Sales for existing products and sync them to Finance and Operations.
  • Generate invoices in Finance and Operations and sync them to Dynamics 365 for Sales.

Mobile Apps/Workspaces:

Mobile workspaces/apps were introduced with the Update 3 release of Dynamics 365. Since then, these workspaces have been evolving and Microsoft continues to deliver more and more mobile workspaces covering various mobile business process scenarios. Some of the key mobile workspaces that were released in the July 2017 update are as below.

This slideshow requires JavaScript.

The highlight of these workspaces is the mobile app for Project Timesheet Entry and the Expense Management app. I provided my views on the preview version of these mobile workspaces in my earlier post. These workspaces have added significant amount of new features with the July 2017 release. The Expense management workspace now support end to end expense management from receipt capture, new expense report creation, submission, expense approvals and expense status inquiry and so on. Below are some screenshots of the mobile workspaces released in the July Update.

Employee Expenses Management and Reimbursement related enhancements:

There are several new features and usability enhancements that are introduced for Employee Expenses management in the July Update. From all these features and enhancement, my favorites are as below.

  • Dedicated Expense management workspace

expense-workspace

  • Grouping of vendor invoices for different expense lines of an expense report, as opposed to create separate vendor invoices for each expense line, for reimbursement. This was one of the most talked about concerns in the earlier version (AX 2012), since it was causing problems creating individual invoices for each expense lines and there by causing issues in Check printing etc. Now with this release, you can optionally group all expense lines with the same method of payment to post as grouped vendor invoice instead of individual invoices. If you enable the grouping of vendor invoices, this functionality basically posts all the expenses of the expense report with same payment method on the recent transaction date from the list of expense lines.

  • Several usability enhancements in some key screens. Also, Employees can now track payment information for their expense reimbursements. Nice and very useful functionality, as this is one point that customers usually ask and they used to customize it in AX 2012.

This slideshow requires JavaScript.

OCR interface for capturing vendor invoices automatically:

One of the most common asks from customers in the AP invoicing area is the functionality of OCR and vendor invoice automation. Organizations often offload the paper invoice processing to 3rd party OCR reader service providers. These service providers provide machine readable metadata for the invoice along with scanned imaged the invoice headers and lines. In the July 2017 release, the solution/standard interface to read these invoice metadata and invoice scanned attachments is in-built into the AP invoice process of Dynamics 365. 3rd party OCR service provider systems will be able to send metadata feed for invoices directly to D365FO.

This new functionality basically provides the following.

  • Out of the data entities invoice header, invoice lines, and invoice attachments.
  • Exception processing for invoices. A frontend UI for users to make it easy to track failed invoice imports.
  • A side by side invoice attachment viewer to imported invoices and exceptions.

Vendor Invoice

PowerBI reporting with Financial Dimensions:

This feature will be available with July 2017 Update and you will also need to have the most recent Platform update of Dynamics 365, which is Platform Update 8. This features let’s the power users or the BI report creators to add financials dimensions to the readily available aggregated measurements or custom built aggregated measurements in the Entity store.

With that, when the Entity store is periodically updated/refreshed, the financial dimension information of all the General ledger transactions will automatically be included in it. Then you can use those aggregated measurements to write joins, queries within Power BI to create any sort of financial report/dashboard within Power BI itself. Screenshot below shows just an example.

Publish financial reports from Dynamics 365 to SharePoint:

In the earlier versions/releases, you could generate financials reports and export/save it to your local computer. With the July 2017 release, you can now save financial reports directly to a SharePoint document library. The benefit of this is, you can setup alerts within SharePoint to notify you when new reports are available.

Note: I don’t have SharePoint configured in the demo environment, so not able to show the full experience.

FInancials Statement to Sharepoint

You could also extend this further and write a Microsoft Flow, to automatically send the reports directly to your inbox from SharePoint. Endless possibilities !!

Tools for upgrade from AX 2012 or AX 2009 to Dynamics 365:

You can upgrade from Dynamics AX 2012 to Dynamics 365 for Finance and Operations, Enterprise edition. The complete Dynamics AX 2012 database can be brought forward, and your AX 2012 codebase can be upgraded to Finance and Operations. You can migrate from Dynamics AX 2009 to Finance and Operations via a migration toolset to bring forward master data and opening balances. It would be interesting to test these upgrade experiences and tools as opportunity comes !! 

The Upgrade is now more predictable, which reduces the overall cost of the upgrade process. Upgrade starts with an automated analysis phase, which defines the preparation tasks required to reduce the time and cost to upgrade, as well as the ongoing future cost of Finance and Operations. Post upgrade, an automated validation phase provides statistics and metrics on the success of the upgrade process. The validation details can be used to quickly assess the state of the upgrade, so you can continue with functional testing and sign off.

In Finance and Operations there are no expensive upgrades needed to stay current and take advantage of continuous innovation. You can update to the latest versions of the product with a click of a button.

Support for Hybrid Cloud (Cloud + Edge) and Op-premise (Local Business Data) Deployment scenarios:

In one of my earlier posts, I explained some details about the 3 different deployment options that Dynamics 365 is going to provide. Starting with the July 2017 Update, both these deployment options are available. Customers who are keen on having an On-premise deployment of Dynamics 365 for Finance and Operations to capitalize on their existing infrastructure investments or due to data security and compliance requirements, will have the option to deploy D365FO in Hybrid as well as On-Premise model.

d365-opr-deployment-scenarios

Microsoft published system requirements documentation explaining the detailed system requirements for an On-premise deployment of D365FO. You can find the information at this URL

There was system requirements document also that Microsoft published. See URL below.

https://www.microsoft.com/en-us/download/details.aspx?id=55496

I will share more info about this in future as we move with some testing and some actual deployments for customers.

That was a long enough post :). There are several other features and functionalities across technology stack, Retail and manufacturing modules, that I have not highlighted here in this post. There is a lot to explore and learn!!!

Stay tuned and stay current !! Till next time..

Thanks // Sandeep

Sandeep Chaudhury is a Dynamics AX enthusiast with over 10 years of experience in functional consulting, Solutions architecture and systems integration, with expertise in the areas of Professional services automation(Project Management and accounting), Financials Management, Services Management, Sales and Marketing, Human resource management, Travel and Expenses Management and Procurement & Sourcing modules of Microsoft dynamics AX ERP. He has experience working with the new Dynamics AX (AX 7), AX 2012 R3, AX 2012 R2 and more.

Manage your Project Resources efficiently with Resource request workflow in Microsoft Dynamics 365 For Operations

In some of my earlier posts, I discussed about the various capabilities of the Project resource management feature of Dynamics 365 For Operations and how it can help Professional Services firms manage their project resources, to ensure optimum resource utilization, and drive better project profitability, by deploying the right people at the right time in the project..

Continuing the conversation the this topic, I will discuss about some of the additional features that you can take advantage of, to manage your central pool of project resources even more efficiently. Your Project managers can better coordinate with Resource Managers, for finding and deploying the right resources by having visibility into resource’s capability and availability in real time.

Resources

In Dynamics 365 For Operations, you can optionally enable the Resource request workflow. When you enable the workflow, project managers can create and submit requests for resources whom they want for their projects. The Workflow can be configured to assign the resource requests to the required Resource Managers. Let us see in the few screenshots below, how this experience looks like for the Project Managers and Resource Managers.

Resource Request approval Workflow :

I have a very simple workflow setup, where the project resource request will be assigned to a designated Resource Manager of the Organization.

Workflow

Project Manager creates Project Team and submits request for resources: The Project managers can create the Project Team, where they can select available resources and submit the request for approval of the resources. The project manager requires 2 Software developers for this project. He is able to view the Resource pool of developers and testers and is able to view their availabilities.

Developers

The project manager then submits the request for these resources by soft booking (Tentative booking) them on the project.

Create Resource request

After the resource request is submitted, notice that the indicator shows that these resources have been requested.

Resource Requested

Resource Manager gets notified and reviews the resource request and approves the request:

Under My Resource Requests page, the resource manager gets to see all the resource requests where they can review the requests and approve/reject them. The resource manager also gets to see the other available resources and their current reservation details, in case they want to refer to those information. They can also see the details of resource request by clicking the Request details button.

Resource Approval

At this point, the Resource Manager approves the request and as soon as this is done, the resources will be automatically hard booked (Committed/booked to the project) and can be assigned to Tasks of the project further.

Developers Booked

That was a quick post about the new Resource request workflow feature for better project resource management in Dynamics 365 for Operations. Keep exploring !!

-Sandeep Chaudhury

Sandeep ChaudhurySandeep Chaudhury is a Dynamics 365 enthusiast with over 10 years of experience in functional consulting, Solutions architecture and systems integration, with expertise in the areas of Professional services automation(Project Management and accounting), Financials Management, Services Management, Sales and Marketing, Human resource management, Travel and Expenses Management and Procurement & Sourcing modules of Microsoft Dynamics 365 ERP. He has experience working with the Dynamics 365, AX 7, AX 2012 R3, AX 2012 R2, Dynamics 365 for Operations and more.

Dynamics 365 For Operations Tip: Vendor Prepayments and Revenue Recognition for Fixed Price Projects

Hello, Good to be back here on the blog !!! Jumping straight into the topic here today about a new addition of a feature for vendor prepayments in relation with fixed price project revenue recognition !!

Issuing large amounts of prepayments to vendors is often a common business requirement for large scale, long-term fixed price projects, which involves a lot of sub-contracted work. Vendors often request prepayments for the subcontracting services they are contracted to deliver for these projects. These prepayments can sometimes be just a flat amount based on mutual decisions, or it can sometimes be a percentage of the total cost of the subcontracting service. There can be several months of gap between when the prepayments are issued and when the vendors actually deliver the services.

For such projects, customers usually recognize revenue on a percentage completion basis and need the ability to include these vendor prepayments in the project percentage completion calculation of the project for revenue recognition/revenue estimates calculations.

In this post, we will evaluate one of the new features of Dynamics 365 For Operations (Referred as D365 – Operations from here on), which allows us to consider these vendor prepayments automatically when running the monthly revenue recognition/estimates for fixed price projects for calculating the % completion of the project.

For this demonstration, I have setup a fixed price project and the associated contract already. This project is setup to recognize revenue on a % completion basis.

Contract Setup

Project Setup

The Project Manager has created and submitted the purchase requisition for approval so that the services can be procured from Rebar Supply Co. Ltd. See screenshot below.

PR Submitted

The purchase requisition gets approved by the designated manager and the Purchase order is automatically created. See screenshot below.

PR Approved

The Project procurement team/Project manager then sets up the prepayment details on the project purchase order that was automatically created upon approval of the requisition.

PrepaySetupOnPO

Finance and Accounting team now processes the prepayment invoice to initiate the prepayment to the vendor.

Prepay Invoice

Prepayment

Now that the finance team has processed the vendor prepayment for the subcontracting work, let us now go ahead and see what happens when they run the monthly revenue recognition process for this project.

Notice that system was able to consider the vendor prepayment cost for the project and was able to determine the percentage completion based on the total project budget/forecast defined. See screenshot below

PComp

When this revenue recognition entry is posted, the revenue amount (based on Percentage complete and the total contract value) will be posted to general ledger. We all know how it works from here 🙂

That’s it for today !!

Sandeep

Sandeep ChaudhurySandeep Chaudhury is a Dynamics 365 enthusiast with over 10 years of experience in functional consulting, Solutions architecture and systems integration, with expertise in the areas of Professional services automation(Project Management and accounting), Financials Management, Services Management, Sales and Marketing, Human resource management, Travel and Expenses Management and Procurement & Sourcing modules of Microsoft Dynamics 365 ERP. He has experience working with the Dynamics 365, AX 7, AX 2012 R3, AX 2012 R2, Dynamics 365 for Operations and more.

Dynamics 365 For Operations Tip: Now you can use Position based hierarchies in all workflows

Using a Reporting manager hierarchy for routing workflow documents has always been possible in Microsoft Dynamics AX and Dynamics 365 For Operations. This worked great in cases where you were required to route all of an employee’s workflow documents, such as timesheets, expense reports, purchase requisitions and more, to the manager they report to.

Now in Dynamics 365 For Operations, you can use Custom configured position hierarchies to route workflow documents. So, let’s say  you have a scenario where you need to route timesheets of an employee to the reporting manager, but route the expense reports to a manager they report to in a specific project hierarchy, you can configure this in Dynamics 365 For Operations ! Let’s see how?

On the Position Hierarchy Types, you can select the workflows which can use the selected position Hierarchy for outing documents. For example, in the screenshot below notice that the Matrix based hierarchy can be used by the expense report – USMF and Timesheet workflow.

dynamics365-position-hierarchy-types

NOTE: Note that a workflow can use only one custom hierarchy.

Additionally, you will notice that, on the workflow setup form, you can now view and manage the associated configurable hierarchies.

dynamics365-associate-hierarchy

On the workflow setup/configuration, you can select the steps to be assigned to a Configurable hierarchy. See screenshot below.

dynamics365-workflow-step-1

So, when an employee submits their expense report/timesheet, this workflow setup is going to look for the Matrix Position Hierarchy and assign the workflow document to the worker to whom the employee reports in the Matrix hierarchy instead of the managerial hierarchy.

dynamics365-position-hierarchy

dynamics365-ar-administrator

Small, but useful enhancement !! Hope this quick tip is useful.

Sandeep

Sandeep ChaudhurySandeep Chaudhury is a Dynamics 365 enthusiast with over 10 years of experience in functional consulting, Solutions architecture and systems integration, with expertise in the areas of Professional services automation(Project Management and accounting), Financials Management, Services Management, Sales and Marketing, Human resource management, Travel and Expenses Management and Procurement & Sourcing modules of Microsoft Dynamics 365 ERP. He has experience working with the Dynamics 365, AX 7, AX 2012 R3, AX 2012 R2, Dynamics 365 for Operations and more.

%d bloggers like this: