Return
-
Title
During the workflow why are some attributes pre-mapped and others are not when configuration the -
Description
During the workflow why are some attributes per mapped and others are not when configuration the initial Mapping within Quick Connect?
-
Cause
This is by design in the product.
-
Resolution
The reason why are some attributes pre-mapped and others are not during the initial mapping is Quick Connect looks for similar names against the target. If the source is using a virtual attribute, it likely won't find it in the destination, however if you use something like "Description", the Quick Connect easily finds it.
,