Easy import or Quick import in Domain separated tables.

[rohanhd]

Hello Peers,

Currently I am using quick or Easy import functionality within servicenow to upload data. It is on Fuji instance and the domain separation plugin is activated. When I create the template for a domain separated table eg sys_user it doesn't show the domain field hence I cannot assign the domain to the data loaded rather I have to upload the data for each domain separately or using a script assign the correct domain.

To overcome this I made change to the system property that tells easy import to ignore certain field types. Property is glide.import_template.field_types_to_ignore. From this property I removed the domain_id, hence easy import should not ignore domain_id type fields. But even then when servicenow creates the import template for insert the Domain (type domain_id) field is ignored.

My property value looks as below after removing domain_id:

table_name, order_index, collection, user_image, video, timer, translated_field, conditions, field_name, sys_class_name, journal, journal_input, due_date, user_input, image, workflow, template_value, documentation_field, user_roles, glide_list

Any ideas on what else might be blocking it? or is this an unreported bug.

Thanks

Rohan

[Michael Fry1]

Are you trying to be in global and import across multiple domains? Just use your domain picker to choose the domain to do the import.

[rohanhd]

Yes I am aware of that but we want to set a method where we can load multiple domains data at the same rather than make changes to domain picker every time. We could use transform maps but we have more than 50 different domains and 30 different tables hence maintaining those many maps in the system is not a good strategy. Would you be able to help why the domain_id fields are not visible in the template even when we tell servicenow not to ignore them.

[rohanhd]

When I try loading the data, the column label for sys_domain field on the table is Domain. But once easy import completes it gives me message that the column is ignored because it doesn't exist on destination table.

[Michael Fry1]

What table are you trying to import too?

Using transform map, you can create a script to put rows into appropriate domain, and different tables.