Changing the Mode on Import Set
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-31-2019 08:35 AM
Hello,
It is about the import mode on Import Set and I have tried and tried as per what some folks have reported but none of it works. For instance I am told you are supposed to create an Import Set after you have created the Import Set Table but the Create Import Set gives me the following :-
The Import Set table is completely greyed out and I have delegated admin role. You can't set the mode through a script option either. The default Import Set for an Import Set Table always defaults to SYNCHRONOUS. I want to load first and then transform.
My load and transform process is currently running into a "Maximum execution time exceeded" because of the mode which is set at 3600 secs.
Could someone explain in layman steps as to how to go about changing the import mode?
Thanks
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-31-2019 10:10 AM
ok, it is what you could try
1) create manually importset record (mode=async), state="loaded" (fields are grayed out, thats ok)
2) get sysID for this record.
2) create staging table, that extends sys_import_set_row table, load data via script.
while you are loading staging table, two things:
setWorkflow(false), so business rules (there are two for sys_import_set_row table) are not triggered
, assign fields stagingtable.sys_import_set = your importset sys_id, populate row column in your staging table
3) run transform
let me know if it works
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-31-2019 11:16 AM
But I am not able to create an import set record manually for some reason using the sys_import_set.do command. Every field in the form is greyed out here.
I don't understand why there is a need to again create the staging table extending the import set record. Why is there a need to create the staging table thru a script? I can't use the existing table?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-31-2019 12:18 PM
does your staging table has field sys_import_set?
what it refers to? which importset? what is the mode value for this importset?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-31-2019 01:21 PM
Yes I do see an Import Set, Mode is Asynch, and the state as being PROCESSED. Seems like the import set I see only gets used if I execute the data source where it has the import set attached to it. But I still don't understand why my Flow does not look at the Import Set defined for my staging table. All it does is spawn a new import set and that is set to SYNCHRONOUS. How do I force it to use the import set that is already defined?
Isn't there some directive/property within a script that could force it to use a specific Import Set? With a clustered environment and multiple nodes it can't process 4800 rows. Instead it blows up with the error "Maximum execution time exceeded". Wish there was an easier way to Load first and then Transform. I have worked with so many different tools and this is the first time ever I am finding myself extremely handicapped.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-02-2020 07:44 AM
when you insert record in staging table (that extends sys_import_set_row), two business rules fired: one creates synchronous importset, second does transform
while you populating your staging table, you would need turn off business rules and grammatically assign you importsetsysid to the column