Yes, there are two main ways to handle it:
Example 1: There is a state field on Provider and a custom field called u_state on the consumer
1. Since there is a "close match" source and target, the easiest method is to map state > state when creating the definition on the provider. Next, when the consumer receives the definition, they can change the target to u_state before activating the definition.
Example 2: The consumer has a unique field we will call widget that is required but no match for the provider.
2. In this case, the provider can create a virtual outbound mapping called widget that requires no source and set the sync when to never, so it requires no target. Next, the provider makes a virtual outbound transform for widget and uses a script to set the output label and value. Finally the consumer adjusts the mapping to sync on insert or insert/update and then sets the target field to widget before activating the definition.
