Varan Haiku : glide.import_set_row.dynamically_add_fields

[VaranAwesomenow]

System Property : glide.import_set_row.dynamically_add_fields

When implementing integrations it may not always be needed to dynamically create fields that are available in source payload for following reasons

1. Source system payload may contain attributes which are not relevant from ServiceNow dataload.

2. Source system may provide data to lot of targets along with ServiceNow, hence may change the output attributes more frequently that needed for ServiceNow.

3. Number of columns in import set table are already a lot (more than allowed custom column limit) and adding more fields may break the integration.

Type : True / False

Controls dynamic creation of fields in import sets when loading data via import sets.

Good practice : Set value to False(Production) : If you don’t want ServiceNow to create fields dynamically in staging table.

True(Non-production) : To test and configure required data transformation.

This property need to be added to instance to system properties, I have attached an export of xml record you can import it to your instance and access it via this link

https://<instanceName>.service-now.com/nav_to.do?uri=sys_properties.do?sys_id=9f0db27647b1511021eaf2e7536d4365

Note : This is a global property hence turn on and off with caution.

Now Support articles on what happens if you turn it off : https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0868619

[Christoph Lang]

Hey, thanks for sharing this valuable information.

I did not know about this setting yet.

[VaranAwesomenow]

Thanks for taking time and sharing your feedback !

[Chitradevi G1]

What will be the impact if we turn it off in an existing system.

[VaranAwesomenow]

When you turn this off it doesnt dynamically create columns in import set. Pros: Import set configuration is correctly deployed via updatesets. 

If you load a bad file in prod by mistake it wont accidently create bad columns in import set table.

Cons: Requires all updates to import set tables done via updatesets which is a good practice.

This setting can be let on in dev instance, in higher instances it can be turned off so that all dataload configuration is managed in a controlled manner via updatesets.

[Chitradevi G1]

Thank you for the suggestion. I couldnt get your point "Import set configuration is correctly deployed via updatesets. " what does it mean?