Forum Discussion
Please explain "DynamicDataSource"
Hi Netrelemo
Thank you very much KNP for your prompt reply.
To clarify your points:
Dynamic Data Source as the URL: You're right. The URL is just a string. It’s the endpoint you’re calling, but it doesn’t encapsulate the dynamic nature of the data.
Relative Path: This makes sense as a dynamic reference since it can change based on the context of the API call.
Root System: The root system providing the API can indeed be dynamic, especially if the data is frequently updated or if there are multiple sources feeding into it.
Real world: It is because the real world is constantly changing that the data is also changing.
Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks, although I'm not sure it answers my question.
Here's the thing: I have a particular API endpoint that I want to call repeatsedly, with different "RelativePaths". One would think that I could create a PowerQuery function, with one parameter - the RelativePath as text.
But it does not work.
Because the function parameter is an input, even though it is used as a relative path, I get this dynamicDataSource error.
The minute I take out the paramater and hardwire it, it works fine.