Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I am try to setup dynamic settings to a file source with file type as Delimited Text. I want to setup column and row delimiter and header row properties. I see there is an option to set dynamic expresions to setup for each setting but the expression seems to be giving an error. I tried with using variables and even that is giving similar error.
Any idea how to add dynamic expressions?
Solved! Go to Solution.
Hi @g3kuser ,
In the file format setting of the Copy activity, the parameter information needs to meet the format similar to the following:
"source": {
"type": "DelimitedTextSource",
"storeSettings": {
"type": "AzureBlobStorageReadSettings",
"columnDelimiter": "@pipeline().parameters.columnDelimiter",
"rowDelimiter": "@pipeline().parameters.rowDelimiter",
"skipLineCount": "@pipeline().parameters.skipLineCount"
}
}
If the problem persists, providing specific error messages and configuration snippets facilitates my further diagnosis.
Best Regards,
Adamk Kong
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Looks to be some bug. When I added expression by double clicking on parameter name it ended up as @dataset.paramname resulting in validation errors. Instead that expression should be @pipeline().parameters.paramname. I explicitly copied the expression and it worked.
Explicitly Type or Paste: As you've discovered, this is the most reliable workaround. Don't rely on double-clicking. Either type the full expression @pipeline().parameters.paramname manually or copy and paste it from a known-good source.
Use the Expression Builder (Carefully): The expression builder should work correctly. However, you need to be very careful about where you're at in the UI when you open the builder. Make sure you're in the correct property of the activity where you want to use the parameter. Sometimes, the builder might default to a dataset or linked service context, which could lead to the wrong syntax.
Parameterize in the Pipeline (If Possible): If you have more control over the pipeline design, try to parameterize at the pipeline level whenever possible. This often simplifies things and reduces the chances of these context issues.
Check JSON Definition: For complex scenarios, you can sometimes edit the underlying JSON definition of the pipeline. This requires more technical knowledge but can give you fine-grained control. Be extremely careful when editing JSON directly, as any syntax errors can break your pipeline.
Workaround with a Variable (Less Ideal): As a last resort, you could use a pipeline variable. Set the variable's value to @pipeline().parameters.paramname, and then use the variable in your activity. This is less direct but might work if other methods fail.
Hi @g3kuser ,
In the file format setting of the Copy activity, the parameter information needs to meet the format similar to the following:
"source": {
"type": "DelimitedTextSource",
"storeSettings": {
"type": "AzureBlobStorageReadSettings",
"columnDelimiter": "@pipeline().parameters.columnDelimiter",
"rowDelimiter": "@pipeline().parameters.rowDelimiter",
"skipLineCount": "@pipeline().parameters.skipLineCount"
}
}
If the problem persists, providing specific error messages and configuration snippets facilitates my further diagnosis.
Best Regards,
Adamk Kong
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Fabric update to learn about new features.
User | Count |
---|---|
1 | |
1 | |
1 | |
1 | |
1 |