The sequencer replaces the original metadata file with a new one on every iteration. An update on the original metadata file never worked (at least in my PP lifetime). I always had to save an intermediary file, reload it, interpret it and so on…
I already solved my problem with passing a separated string as a variable from the workflow to the data mapper and splitting it. But loading text and JSON.parse() is also a way. Have to test it.
But now I have another problem. Is there any way to skip a record in the data mapper?
Let’s say, I have a list of statements to skip, an I don’t want them to be generated as records?
I know, I can do it also in the workflow, but it would be much easier in the data mapper. I already did the definition work and the input data is pretty weird… It doesn’t make sense to replicate the logic in the workflow.