Hi @cew657,
You’re actually pretty close. The parameters you send while executing/validating will override the ones you’ve set in the child pipeline. You cannot see those directly, but you can capture them like you already did in your setup. Those can be seen on the execution within the Dashboard.
Next, the only problem here I think is that you are passing the filename as a parameter, not the file path, which I believe it is produced from the Directory Browser as a $Path field.
After we confirm that this is the issue you’re having, I think you can try and simplify things significantly, because you don’t need to pass any parameters at all. After the Directory Browser lists the files and paths, the data will enter the child pipeline, and the $Path field can be directly passed into the File Reader, no need for parameters, no need for mapping.
Try these and let us know the result.
Regards,
Bojan