About the specification of GMU's "mapping action: ignore"

Document ID : KB000095172
Last Modified Date : 09/05/2018
Show Technical Document Details
If Include Policy Fragment is mapped by ignore, it will not migrate properly.

Reproduction step:
01. run migrateOut a service. (The service has "Include Policy Fragment".)
02. run manageMappings the source service to target service with mapping action update. 
03. run manageMappings the souce "Include Policy Fragment" to target"Include Policy Fragment" with mapping action ignore.
04. run migrateIn  the service to targer.

Include Policy Fragment does not migrate properly.
The following is shown.
"Include Policy Fragment: Deleted Policy #xxxx

The reason is that Include Policy Fragment's GUID is different on source and target.

In this case, we will replace the source service with the target service by mapping.
Therefore, the source GUID information is transferred as it is.
Since Include Policy Fragment is ignored as Ignore, Include Policy Fragment itself will not do anything.
However, since the service is updated, the information of the Include Policy Fragment to which the service is linked is the source GUID.
As a result, this problem occurs because the target GUID can not be found on the target.

If you use an existing entity on the target entity, the mapping action should specify Existing instead of Ignore.