Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
I am trying to pass a query with a pipeline parameter from a json. And passing the parameter while running the pipeline and the pipeline fails. below query:
Also, tried the below expression the copy activity query editor and still no luck. Any ideas appreciated.
-----------------------------------------------------------------
Solved! Go to Solution.
Hi @IAZ ,
Looks like you're trying to dynamically pass a pipeline parameter into your query string using a JSON config, but the expression isn't resolving as expected during runtime.
The issue is likely because you're trying to use @{pipeline().parameters.par1} inside a string that's already being evaluated by the @concat() function. When you nest expressions like that, especially inside JSON-driven queries, it can get tricky.
Instead of embedding the parameter directly in the JSON like this:
"query": "select * from CUSTOMER where OBJ > @{pipeline().parameters.par1}"
Try keeping the query in the JSON more generic, like:
"query": "select * from CUSTOMER where OBJ >"
Then in your copy activity, use something like:
@concat(item().source.query, ' ', pipeline().parameters.par1)
This way, you're appending the parameter value at runtime without trying to resolve nested expressions inside the JSON.
Let me know if you're still hitting issues, happy to help further.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
Brilliant...many thanks and really appreciate you help and guidance. It works ! And saved me loads of time. Thanks again.
Hi @IAZ ,
Looks like you're trying to dynamically pass a pipeline parameter into your query string using a JSON config, but the expression isn't resolving as expected during runtime.
The issue is likely because you're trying to use @{pipeline().parameters.par1} inside a string that's already being evaluated by the @concat() function. When you nest expressions like that, especially inside JSON-driven queries, it can get tricky.
Instead of embedding the parameter directly in the JSON like this:
"query": "select * from CUSTOMER where OBJ > @{pipeline().parameters.par1}"
Try keeping the query in the JSON more generic, like:
"query": "select * from CUSTOMER where OBJ >"
Then in your copy activity, use something like:
@concat(item().source.query, ' ', pipeline().parameters.par1)
This way, you're appending the parameter value at runtime without trying to resolve nested expressions inside the JSON.
Let me know if you're still hitting issues, happy to help further.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
User | Count |
---|---|
75 | |
45 | |
15 | |
11 | |
7 |
User | Count |
---|---|
90 | |
88 | |
27 | |
8 | |
8 |