Import Set API returning "Invalid table" when populating staging table mapped to RTE+IRE implementationIssue Import Set API returning "Invalid table" when populating staging table mapped to RTE+IRE implementationReleaseAnyCauseRTE works with insertMultiple but not single insert. single insert is synchronous by default, while insertMultiple is asynchronous by default. when populating a staging table linked to an RTE+IRE implementation there will be more than one target table mapped to it, we believe that the legacy import API "/api/now/import/{stagingTableName}" does not support a response format that provides information for all the target tables impacted.ResolutionImport Set API has two insert methods: POST /now/import/{stagingTableName} POST /now/import/{stagingTableName}/insertMultiple. Aligned with the documentation found in https://developer.servicenow.com/dev.do#!/reference/api/vancouver/rest/c_ImportSetAPI,POST /now/import/{stagingTableName} "inserts incoming data into a specified staging table and triggers transformation based on predefined transform maps in the import set table." while POST /now/import/{stagingTableName}/insertMultiple "Inserts multiple records into a specified staging table and triggers transformation based on predefined transform maps or Robust Transform Engine (RTE) configurations in a single request." - There's no workaround we could find now, but when using insert multiple "/api/now/import/{stagingTableName}/insertMultiple" this is not happening.