I still struggle with parameters. I understand that they are immutable, but it’s the connection between a field that I have that contains data I want to pass into the file name and the parameter that contains the majority of the destination path except for the file name which would change each time the job runs.
For example, I have this derived table deduped down to the pay period name that needs to be in the file name
So the export file name needs to be a combination of the pay period name field and parameter based path.
I think that the answer is going to be something with moving the export part of the project to a new module then iterating that pay period column into a parameter in the new module. But concept really breaks my brain because while the pay period changes once every 2 weeks, it’s immutable for this run only.
The downside of this approach is that the output Excel file will have a column with the file path.
The "First column value" option sometimes helps avoid creating a separate module just for one iteration.
Also, you can use the "Iterate table" action in the 'PayPeriod Name" table. It will require creating a module with one "Input" action that will be used to pass the main table "Pay Period Data" into that module, which then can be immediately saved into a file in that module. So basically, iterating with just 1 iteration.
