Forum Discussion
How create API with paging ?
There's a couple of things that immediately spring to mind:
1) Have you set up your paged call like this, using RelativePath?
Using this RelativePath structure for the Web.Contents is a key aspect of avoiding Dynamic Data Source errors.
You may need to adjust which parts of the URL sit within the core/RelativePath sections.
You may also need to use the same structure for your original ping call, but I've never had issues with this initial call being the basic Web.Contents structure.
2) Have you deleted all unused queries in the Dataflow that don't use the correct Web.Contents structure?
I've found that, even if incorrectly-structured calls are disabled from loading, they still cause the entire DF to fail on initial query validation. Not sure why, just something I've experienced.
Pete
Hi BA_Pete I managed to follow your instructions sucessfully, which is great!
However, when I want to save and close the dataflow, I get this error: One or more tables references a dynamic data source... is there any way to solve this?
Super User
There's a couple of things that immediately spring to mind:
1) Have you set up your paged call like this, using RelativePath?
Using this RelativePath structure for the Web.Contents is a key aspect of avoiding Dynamic Data Source errors.
You may need to adjust which parts of the URL sit within the core/RelativePath sections.
You may also need to use the same structure for your original ping call, but I've never had issues with this initial call being the basic Web.Contents structure.
2) Have you deleted all unused queries in the Dataflow that don't use the correct Web.Contents structure?
I've found that, even if incorrectly-structured calls are disabled from loading, they still cause the entire DF to fail on initial query validation. Not sure why, just something I've experienced.
Pete
Hi BA_Pete - your 1)-suggestion was indeed the issue. The original ping call needed a RelativePath, and that solved the problem. Thanks so much, you're a star! 😊 🌟