From the Microsoft Dynamics 365 Finance & Operations Blogs: Batch jobs; Fixing issues; Workflow signing limit; Positive pay functionality

September 2 2022

Listen to article:

FREE Membership Required to View Full Content:

Become a Member Login
Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates. 
Learn more about us here

This week on the Dynamics 365 Finance and Operations blog roundup:

  • How to handle batch jobs when disabling or deleting a user in D365FO
  • Workflow signing limit for a purchase order in D365FO
  • Positive pay functionality impacted by XSLT scripting feature deprecation on version 10.0.27
  • Options for fixing segregation of duties and licensing issues in D365FO

How to handle batch jobs when disabling or deleting a user in D365FO

Writing on his blog, Alex Meyer stated that someone reached out to him asking about the "right" way to handle batch jobs when disabling or deleting a user from Dynamics 365 Finance and Operations. Meyer explained that batch jobs within D365FO allow for a way to execute a set of instructions that can be scheduled to run on a periodic basis.

However, since each batch job runs under the context of a user within the system, if that user is disabled, the batch jobs tied to that user will not be able to execute and will fail, Meyer said. Additionally, if a user is deleted, any batch job associated to that user will also be deleted.

Meyer said that there are two ways users could deal with these issues:

  • Use table events to capture when a change occurs to the UserInfo table (either disabling a user or deleting a user) and assign all batch jobs for that user to an ‘admin’ type user
  • Build a custom form to allow you to reassign batch jobs to any user you would like, using this you can be proactive about reassigning batch jobs before you actually disable or delete a user

He then went on to explain each of these solutions in detail.

Workflow signing limit for a purchase order in Finance and Operations

Writing on his blog, Saurabh Bharati discussed the signing limit policy that users can set up and attach to a workflow. He also pointed users to his earlier posts on this topic.

First, Bharati explained that a signing limit defines the largest financial commitment that a worker is authorized to make on behalf of an employer. He added that there are two types of signing limits: spending limits and approval limits.

However, since signing limits can vary depending on the transaction type, purchase requisitions, expense reports, purchase orders, and invoices can have different signing limits. In his blog post, Bharati offered the approval signing limit with purchase order example. He noted that the same information could also apply to purchase requisitions, invoices, and expense reports.

Positive pay functionality impacted by XSLT scripting feature deprecation on version 10.0.27 of Dynamics 365 Finance and Operations

About MSDW Reporter

More about MSDW Reporter