Conditional mapping and issues updating work items #1349
Replies: 1 comment
-
Re-Migration of a Work ItemIn the You can a) delete the work item in the target to re-migrate, or b) make a change on the source to force a revision. There is a completely undocumented Field MappingsThere is not a lot of documentation on the FieldMapps, but the We do take pull requests, and this is a good suggestion. |
Beta Was this translation helpful? Give feedback.
-
I'm trying to get some kind of conditional mapping going on with the following setup:
I tried using the MultiValueConditionalMapConfig settings to do this, with no luck. The documentation doesn't show any examples on how to use it and i don't see anyone online attempting to do so.
I then tried using the WorkItemMigration processor to first move the work items to Target and then running it again with a different mapping config to map Field DEF on Source to Field ABC on Target, for the work items that have Field A empty on Source.
However, the processor seems to ignore the work item since it exists already on the Target and no revisions are detected:
Is there a way to do this? Can i make the processor not skip any items? I do have FilterWorkItemsThatAlreadyExistInTarget set to false but it seems to make no difference in this case, which is why i'm not sure if this is an issue or just a design choice. And what about the MultiValueConditionalMapConfig? Is there any documentation on how it works exactly and how to use it?
Beta Was this translation helpful? Give feedback.
All reactions