I have a requirement involving a catalog item in the portal, which is already implemented for bulk upload. When we select the CI class variable from the portal, the respective transform map should run. However, currently, if we have 12 rows in the template, every transform map runs 12 times, resulting in a total of 17 TMs * 12 (number of rows in the template). This means if we have 1000 records, each TM runs 1000 times. It is not necessary for all transform maps to run; only the one related to the selected class should run when we import data from the bulk import catalog.
How can I achieve this? In the flow, the script will run the data source in the background. The respective CI class transform map should trigger, while the rest should remain idle.
#Data foundation.
