A Groovy Script can be implemented by the Development Team to be sure certain values are copied to Custom Fields when the record is downloaded from the Master Instance to the Customer Instance.

The following example shows expected behavior:

The Master record has license_status__v populated.

Groovy Script is set to copy the value from license_status__v to a Custom Field in the Customer Instance.

The Master record is downloaded to the Customer Instance and the Groovy Script is triggered and the Custom Field gets populated.

The value is not copied in the Customer Instance.

Root Cause:

The field is not populated in the Master Instance for the record(s).

The corresponding Custom Field is not enabled or available in the Customer Instance.

Conditions are not valid for the record(s) in question.

Solution:

Do the following:

Download the Groovy Script file.

Double-check which Fields are involved (e.g. license_status__v).

Be sure that the field is populated in the Master Instance for the record in question. If not, it is expected that the corresponding custom field does not get populated in the customer instance.

Be sure that in the Customer Instance, the corresponding Custom Field is enabled and available for the country in question. This can be verified in the Data Model.

If all is properly set up, check what the conditions are for the Groovy Script to be applied (example: license_status__v must be Active and best_state_license__v must be Yes or True.

Be sure the conditions are valid for the record in question. If not, it is expected that the Groovy Script does not copy the value.

Related Documentation:

N/A

Send us your feedback: We're always looking for advice to help improve our Knowledge Base! Please let us know if this article was helpful or provide feedback on how we can improve your experience here.