When the write workflow is run, and is outside of the match/stage workflow, it sets the attributes used by the template multiple times, and can cause issues with unwanted overwriting of attributes.
When a match/stage workflow is run, and the write workflow is not part of the same workflow as the match/stage, the match/stage creates the changeset for the write workflow to use the next time it's run. If the match/stage workflow is run once, and then run AGAIN before the write is run, it creates a second changeset.
In this scenario, when the write workflow is run, it will first perform the changes created on the first changeset, then perform the changes again on the second changeset. If the first changeset was created to overwrite attributes that you did NOT want overwritten, and then you changed the template to exclude those attribute mappings and ran the match/stage again, the attributes would STILL be overwritten during the first write pass using the initial changeset that was created.
In order to clear any changesets that were created with a match/stage workflow before you run the write, first run your read workflow. This will clear any stored changes waiting for a write. Once that is run, you can now run your match/stage again with the updated template, which will create only one changeset (which should be the correct one at this point). You can now safely run your write workflow.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad