I’m using Data Lookup Matcher Rules to populate some Reference columns in my Import Set based on vendor key values in the source file. For example, vendor part id 12345 might get mapped to cmdb_model record “Routers”. The reference is what I want pushed into the target table.
The matcher rules work as expected when I open an Import Set row and populate the Part ID field.
However, I need these rules to run in the context of an import, right before my Transform Map runs. And I find that they are not running – at least, not by the time the transform runs.
My Data Source is polled by a Scheduled Data Import. The import reads data from my Data Source and populates an import set. Because my Data Source has a Transform Map associated with it, the transform runs immmediately. And here is where things go wrong. The transformRow event checks that those References have been populated, so as to filter out rows where these are empty. I find they have not been populated, and it skips inserting that row to the target.
if(!source.getValue("u_model")) {
ignore = true;
return;
}
But if I open the Import Set, the references are populated.
I think this is a race condition. It seems as if the matcher rules are running asynch (that is, upon an insert/update to my import set table), and the transform is not allowing time for this process to run. But the transform runs immediately, because it’s tied to my data source. Is my theory correct?
Assuming yes, the question is how can I restructure this to separate the creation of my import set from the running of the transform, and allow enough time between those two for the matcher rules to run?
All I can think of is to create my import set through a script and then schedule a run of GlideImportSetTransformer a few minutes later. Is there a better option or one with less scripting?
