Forum Discussion
Dataflow Timeout and "Query Contrains Errors"
- Anonymous6 years ago
Hi Anonymous ,
Thanks for the response. I was over thinking it.
I used Relative path to get past the dynamic URL issue and used startAt and maxResults for each entity. ie rows from 0-2000 and then a second entity of 2001-4000 and so forth.
Combining these tables into 1 made there no need for pagination.
Hope that helps someone that needs pagination in their dataflow.
HI Anonymous ,
It seems like you are using dynamic custom functions about iterator and pagination results that power bi dataflow does not support. I'd like to suggest you take a look at the following link to know more about the limits of using dataflow:
Creating and using dataflows in Power BI - Considerations and limitations
Regards,
Xiaoxin Sheng
- Anonymous6 years agoNot applicable
Hi Anonymous ,
Thanks for the response. I was over thinking it.
I used Relative path to get past the dynamic URL issue and used startAt and maxResults for each entity. ie rows from 0-2000 and then a second entity of 2001-4000 and so forth.
Combining these tables into 1 made there no need for pagination.
Hope that helps someone that needs pagination in their dataflow.- JoeRobert065 years ago
Helper II
This is a good post however what if pagination is required when you are dealing with many pages. Is there a work around this? I am doing something similiar by using a relative path with a dataflow but embedding a function in the query so that I can merge all the pages together. This works in desktop but I cann get this to execution as a dataflow. Each row value comes back as an [Error] instead of a [list]