Skip to main content
Post a question

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id : 8fSbLgYD7abdBAgAtEcC7d
Dynamics 365 Community / Forums / Small and medium business | Business Central, N... / Workflow User Group Qu...
Small and medium business | Business Central, N...
Suggested answer

Workflow User Group Questions

Like (3) ShareShare
ReportReport
Posted on 12 Mar 2025 16:51:00 by JGarcia123 490
How do workflow changes affect currently entered batches.  Using General Journals as an example, we are finding that if a workflow is altered after a journal is created, but prior to posting then the batch tends to produce a workflow error.  
 
As such is there a best practice for making workflow changes.  Do existing batches need to be posted first prior to the change?  Please advise.  Thank you.
 
JG
Categories:
Dynamics 365 Business Central
  • Suggested answer
    Jainam M. Kothari Profile Picture
    Jainam M. Kothari 929 on 13 Mar 2025 at 04:27:10
    Workflow User Group Questions
  • Suggested answer
    YUN ZHU Profile Picture
    YUN ZHU 78,625 Super User 2025 Season 1 on 13 Mar 2025 at 00:58:23
    Workflow User Group Questions
    As far as I know, modifying the Workflow will not change the Approval Entries that have been submitted, so the previous records are still the original approval flow.
    It is recommended that all approvals be completed before making any changes.
     
    Thanks
    ZHU
  • Suggested answer
    Holly Huffman Profile Picture
    Holly Huffman 2,845 on 13 Mar 2025 at 00:17:48
    Workflow User Group Questions
    Hi there! Good morning, evening, or afternoon - depending on where you are :) Hope you are well today!
     
    Workflow changes can impact existing batches, especially if the logic or conditions were altered after batch was created but before it posts. To minimize errors and ensure smooth operations you can follow some best practices: 
     
    - post existing batches first before making any changes, this prevents conflicts between old workflow logic and the new one
    - communicate changes to all users so they are fully aware 
    - review dependencies to check if changes affect any fields, conditions, or approvals tied to existing batches. adjust as needed to avoid errors. 
    - test, test, test! in a sandbox environment before applying (and test scenarios of a batch entered and new ones as well of course) to indicate the behavior which can be expected if the batches can't be posted before (although ideal)
     
    hope this helps some! 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,845 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,713 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156 Moderator

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans