linked service parameterization rest type with d=offset & limit [Product issue]

Shreyash Choudhary 126

hi,

i am not able to parameterize linked service when my api link have offset and limit , when tried and used in zure mapping dataflows it fails, i know it works in copy, but my solution required dataflow. i don't know why ?

discussed with a person from microsoft , he told the same approach but in dataflow its fails.

api link with changing offset and limit , i am pasing offset and limit part from parameter

https://abcd.com/vc/limit=9999&offset=1

parameter 1 url:https://abcd.com/vc/

param2 : /limit=9999&offset=1

and concatenating in final link these param.

ShaikMaheer-MSFT 37,896 Reputation points Microsoft Employee

2023-03-14T10:32:12.2+00:00

Hi Shreyash Choudhary,

Thank you for posting query in Microsoft Q&A Platform.

Could you please share your linked service configuration details along with screenshots and also API details if possible? So that I can try same and let you know.

Between, could you please check below video of mine, where I used linked service for API with paramters in copy activity and see if that anyway helps you.

Copy activity - Pagination rules - Variables in QueryParameters in Azure Data Factory

Please let me know how it goes. If not helps, as requested please share your linked service screenshots to understand how you created it and also how you are using it in dataflows. Screenshots and more details helps.
Shreyash Choudhary 126 Reputation points

2023-03-14T11:07:35.91+00:00

Hi,

API format is like this can't share : https://abcd.com/v3/Getdata?dataoffset=1&limit=9999

in linked service created thre parameters

param1 value: https://abcd

param2 value : /v3/Getdata?

param3 value: dataoffset=1&limit=9999

and in base url i am concatinating all this three : @concat(param1,param2,param3)

connection successfull at linkedservice level and datset level when tested

when checked same inside dataflow it gives error like : attached image

asked a person from microsoft he told me the same approach ,when tried its didn't worked out.

cant give exact api details but when hardcoded it works , but when things need to move to prod everything we are parameterizing & this is creating problem.

also tried with relative URL approach that too didn't worked out, in that approach passed

part of url passed as parameter in dataset relative url : Getdata?dataoffset=1&limit=9999

in base url passed just https://abcd.com/v3/