Robust transform failing with the error "Could not find value for one or more symbols used in query condition. Transform rule order for symbol used in query condition should be less than the order for this transformer rule" - Support and Troubleshooting

Robust transform failing with the error "Could not find value for one or more symbols used in query condition. Transform rule order for symbol used in query condition should be less than the order for this transformer rule" Summary If you have configured Robust Import Set Transformers, the integration could be getting the error below on the importset records.

Transfomation failed: Could not find value for one or more symbols used in query condition. Transform rule order for symbol used in query condition should be less than the order for this transformer rule The import log will be having a stacktrace similar to the one below.

java.lang.RuntimeException: Could not find value for one or more symbols used in query condition. Transform rule order for symbol used in query condition should be less than the order for this transformer rule at com.glide.transform.adapter.GlideLookupBatchAdapterRule.initializeCachedResult(GlideLookupBatchAdapterRule.java:333) at com.glide.transform.adapter.GlideLookupBatchAdapterRule.lookup(GlideLookupBatchAdapterRule.java:155) at com.glide.transform.adapter.GlideLookupBatchAdapterRule.evaluatePerBatch(GlideLookupBatchAdapterRule.java:150) at com.glide.transform.adapter.AdapterRule.evaluate0(AdapterRule.java:173) at com.glide.transform.adapter.AdapterRule.evaluate(AdapterRule.java:216) at com.glide.transform.transformer.Transformer.applyAdapterRules(Transformer.java:833) at com.glide.transform.transformer.Transformer.transformInBatch(Transformer.java:640) at com.glide.robust_transform_engine.TransformerWrapper.transform(TransformerWrapper.java:53) at com.glide.robust_transform_engine.RobustTransformEngine.transformRteInputs(RobustTransformEngine.java:309) at com.glide.db.impex.transformer.service.RobustImportSetProcessor.sendToRobustTransformEngine(RobustImportSetProcessor.java:125) at com.glide.db.impex.transformer.service.RobustImportSetProcessor.processBatch(RobustImportSetProcessor.java:106) at com.glide.db.impex.transformer.service.RobustImportSetProcessor.transform(RobustImportSetProcessor.java:81) at com.glide.system_import_set.ImportSetTransformerImpl.doRobustImportSetTransform(ImportSetTransformerImpl.java:142) at com.glide.system_import_set.ImportSetTransformerImpl.transformAllMaps(ImportSetTransformerImpl.java:106) at com.glide.system_import_set.ImportSetTransformerWorker.startWork(ImportSetTransformerWorker.java:40) at com.glide.worker.AbstractProgressWorker.startAndWait(AbstractProgressWorker.java:126) at com.glide.worker.ProgressWorker.startAndWait(ProgressWorker.java:52) at com.glide.worker.BackgroundProgressJob.execute(BackgroundProgressJob.java:59) at com.glide.schedule.JobExecutor.lambda$executeJob$0(JobExecutor.java:113) at com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:116) at com.glide.schedule.JobExecutor.execute(JobExecutor.java:100) at com.glide.schedule_v2.SchedulerWorkerThread.executeJob(SchedulerWorkerThread.java:300) at com.glide.schedule_v2.SchedulerWorkerThread.lambda$process$0(SchedulerWorkerThread.java:188) at com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35) at com.glide.schedule_v2.SchedulerWorkerThread.process(SchedulerWorkerThread.java:188) at com.glide.schedule_v2.SchedulerWorkerThread.run(SchedulerWorkerThread.java:102)

Instructions Below are the possible causes of this exceptions

a) If you have configured GlideLookup operation operation, then the source field in GlideLookup operation is not mapped in Entity Mapping.

Normally you create multiple ETL entities (sys_rte_eb_etl_entity) e.g Import, Temp.

Assuming the following scenario:

You have the following fields for the on your ETL entities (sys_rte_eb_etl_entity) configurations: The Import sys_rte_eb_etl_entity record contains 2 fields IuserID and Ititle. The Temp sys_rte_eb_etl_entity record contains 2 fields TuserID and Ttitle. An RTE Entity Mapping(sys_rte_eb_entity_mapping) exists for Import to temp. In this mapping you have only set up a single mapping from Import.Ititle to Temp.Ttitle fields. You have an "RTE Entity Operations" in the Temp entity that uses a GlideLookup using the field that is not mapped in the sys_rte_eb_entity_mapping in the step above. In this case you have a GlideLookup using TuserID to lookup a sys_user record. Then you will get this exception. Therefore ensure that the field used in GlideLookup operation is mapped in Entity Mapping.

b) The order of Entity Mappings is not correct.

The entity mapping which populates the field used in GlideLookup operation should run before the mapping which uses the operation.

Assume the following scenario:

You have 3 ETL entities (sys_rte_eb_etl_entity) configurations which are Import, Temp and Incident. In addition to the configurations described above you have an RTE Entity Mapping(sys_rte_eb_entity_mapping) from Temp.TuserID to Incident.Caller You have configured following RTE Entity Mappings (sys_rte_eb_entity_mapping) Import to Temp, order: 100 Temp to Incident, order: 100 If the Incident entity has GlideLookup operation, second mapping should have a higher e.g. order = 200 otherwise the exception will be generated