Forum Discussion
Filter activity not working properly
Thanks, justinjbird . That sequential run solution is correct, i have already tested it but since there are very large tables to pull, it is not ideal solution. when we look at the time when set variable activities are evaluated it is 11:08:26. But for filter it is 11:08:35. it means whatever value last set variable activity set for the variable, filter will only evaluate for that variable and will always give same output for every for loop iteration (unless again set variable activity run after filter and change variable name). I had unified mapping file for all tables. i divided that into seperate files for each table and now instead of searching for specific table mapping in a large file, i am pulling table mapping directly from its mapping file using tablename and its working fine.
Hi ketan5050 ,
Thank you for sharing your findings and explaining the timestamp analysis it was an effective way to confirm the race condition caused by parallel execution.
You are correct- in parallel ForEach loops, pipeline variables can be overwritten before activities like Filter run, which explains the repeated translator output. I also appreciate your workaround of dividing the unified mapping file into separate files for each table and referencing them by table name. This approach helps prevent variable conflicts, simplifies the logic, and can improve performance by reducing concurrent lookups.
Thanks for your prompt response justinjbird .
Regards,
Yugandhar.