Hello Nintex-Community,
I have quite a simple issue that has kept bothering me for a while. I have been searching in google (and here) for a solution but never found one, and I believe I am not the only one. I would like to ask if there is a way to optimize this workflow. My idea is working but doesn't feel robust enough.
I have a Sharepoint-Site with various Budget-Lists from different user groups. Each user group has its seperate user rights (i.e. User Group 1 who is responsible for Budget 1 is not able to have a look at Budget 2 etc.). Nevertheless, the management wants to have an overview of all the Budgets. Thus, I have created a new list that consolidates all the various Budget-lists. This new list has also individual user rights for the management only. All the Lists have exactly the same data-structure.
I have created a workflow that runs when the element is created or edited (see Screenshot). The workflow has a parallel function with two "Run if-actions".
1. If field ID_Consolidated is empty (the item is new), the WF will copy the item created at one of the Budget-Lists to the consolidated list. Wait for changes pending, then query the ID of the copied item from the consolidated list based on values of the current item, and save it to ID_Consolidated.
2. If field ID_Consolidated is not empty (the item is not new), the WF will set varialbe vID_Consolidate to the value saved. Then the WF will delete the corresponding item from the Consolidated list, wait for changes pending, and follows with the logik of 1. again.
This works, but I think I will run to problems if the users are duplicating items in their budget lists (as the query criteria is based on the current item, a identical item would make the system confused). I have also tried using the "Copy to Sharepoint" funktion with the option to update a item if it already exists. This did not work, and simply created a new instance of the item.
I would apreciate the help.
Best wishes,
Paavo