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
01-02-2020 11:55 AM
I am a little confused. Which Column in what table gets the sys id? Is it the Staging Table that needs to be updated with the Sys Id of the Import Set that I want it to use after turning off Business Rules on it?
The integration uses an Import Set which is set to Synchronous mode.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-02-2020 01:14 PM
Nataliya,
I don't have any business rules on the staging table.
There is another thing I am noticing. If I turn ON the Active flag on the underlying transforms and run the process I end up getting twice the number of rows in the staging table (import set table) and if I turn OFF the Active flag on the underlying transforms I get the exact number and not double the number, Why is it so? I am not loading the import twice.
Vish
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2020 06:45 AM
hi Jazz
please see below solution we have and maybe it could help you with yours or give you some hints
1) we create importset with mode=async programmatically
2) then we load data into staging table (this table extends Import Set Row), programmatically assigning values to fields that map staging table to importset for each record
rec.sys_import_set=importset sys id from step1;
rec.sys_import_state="pending";
rec.sys_class_name=staging table name;
rec.sys_import_row=i;
3) update state to "loaded" in importset
3) run transform via code
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2020 08:17 AM
Hi Nataliya,
I did change the Mode on the import set and also the data source mapping on it. When I ran the Flow, the staging table populated instantly but the underlying transforms did not kick off. Is that how Asynchronous loading works? I always thought Async would load the staging table and then kickoff the transforms soon thereafter.
Seems like I will have to manually kick it off in a script using GlideImportSetTransformerWorker. Am I right? If so, I would have to explicitly state the Sys_id of the Transform Map I am trying to run and I don't think that should be the way. Kicking off a Scheduled import will force the re-loading of the staging table.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2020 11:10 AM
to kick off transform, you could use a scheduled job Asynchronous Import Set Transformer (activate if it is not active) and make sure that your importset has values that are checked in the job's code