Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Vendor Approval Workflow issue
CarnivalBoy
Member Posts: 3
I have a created a Vendor Approval Workflow that is triggered on Event "A vendor record is changed". The condition is set to <Always>. I presume this workflow is triggered by the table's OnModify event.
The problem is, when a user edits a Vendor, there could be multiple record saves, and thus multiple Approval Requests are created.
This wouldn't be so bad, but when the Approver approves one of the Approval Request Entries, the record restriction is removed, but it doesn't remove the remaining Approval Request Entries. So you end up with redundant open Approval Request Entries.
Is this normal behaviour, or am I missing something in the way I have set it up? I could add a condition that it only triggers when a specified field is changed, but that only allows me to create a workflow against a single field change, not a more general record change.
The problem is, when a user edits a Vendor, there could be multiple record saves, and thus multiple Approval Requests are created.
This wouldn't be so bad, but when the Approver approves one of the Approval Request Entries, the record restriction is removed, but it doesn't remove the remaining Approval Request Entries. So you end up with redundant open Approval Request Entries.
Is this normal behaviour, or am I missing something in the way I have set it up? I could add a condition that it only triggers when a specified field is changed, but that only allows me to create a workflow against a single field change, not a more general record change.
0