From the Microsoft Dynamics 365 Finance & Operations Blogs: User roles; Workflow approvals; 1099 vendor updates; Dual-write

April 9 2021

In this review of Microsoft Dynamics AX and Dynamics 365 Finance and Operations blogs:

  • Should you apply company restrictions to all user roles?
  • How to configure automation of approval in workflow
  • Managing 1099 vendor updates in Dynamics 365 (and AX 2012)
  • Develop custom data entities for dual-write

Should you apply company restrictions to all user roles?

Writing on his blog, Alex Meyer explained that he recently noticed a security issue in D365FO, particularly for users who've updated from Dynamics AX 2012.

The idea is that company/legal entity restrictions only need to be applied to the system user role and no other user role.

What is the rationale behind this? What issues arise if this is done? And what can be done to address this?

In his blog post, Meyer answered the questions: Why apply company restrictions to only the system user role? He then explained why this idea is flawed in many ways and wrote about the main reasons the idea is flawed. Finally, Meyer offered some advice on how to address this issue.

How to configure automation of approval in workflow in MSD365 F&O

On his MsDynamics365 Empowered Community blog, Ramit Paul wrote about a function called Automatic Actions on workflow that enables the system to auto approve/reject the workflow if the given conditions are met.

He noted that while an organization's basic requirement can work with various workflows while booking transactions, there are few criteria/conditions where the company wants the system to approve/reject the workflow automatically.

He then explained how to configure the automation of approval in workflow.

Managing 1099 vendor updates in Dynamics 365 (and AX 2012)

An author writing on the Ellipse Solutions blog noted that sometimes you may need to update a vendor based on new information you've received about the vendor or when the 1099 requirements change. 

If this happens during the 1099 reporting year, there is an extra step required to apply that change to any 1099 transactions that have been recorded.

In the blog post, the author offered an example of a recent 1099 requirement change that made this extra step necessary.  The author stated that Microsoft provided a hotfix for this tax law change and explained what you needed to do to manage the vendor update in this case.

Develop custom data entities for dual-write

Writing on the blog, Adrià Ariste Santacreu stated that dual-write, which is one way to integrate Dynamics 365 Finance and Operations and Dataverse, has been around for about two years.

The standard solution comes with many out-of-the-box entities available to synchronize. This has been one of the great improvements since Dual-write was made available in preview.

Santacreu asked what if you needed to develop a new custom data entity in D365FO and use it in dual-write. He stated that although it's not difficult, there are some things you need to remember when you do it. In his post, he described exactly what those things are.


Image copyright: Florian Klauer on Unsplash

FREE Membership Required to View Full Content:

Become a MemberLogin
Joining gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more, and it’s all FREE. You’ll also have the option to receive periodic email newsletters with the latest relevant articles and content updates. Learn more about us here
About MSDW Reporter

More about MSDW Reporter