Forum Discussion
stever78
Jul 22, 2021Brass Contributor
datasource.error the web page function didnt finish within timeout of 100 seconds
Hi, appreciate if anyone can help with this i have a workbook with 110 queries on it. when i refresh all i get the above error being "datasource.error the web page function didnt finish within ti...
stever78
Jul 22, 2021Brass Contributor
ok sergei, thanks for reply
so are you saying that adding an index column after table.combine would help or speed up the refresh time of the query? or is there another reason for doing this.
i.e you mention fix table in memory?? could you please inform me what this means? to do with amount of memory it uses up?, thanks, steve
so are you saying that adding an index column after table.combine would help or speed up the refresh time of the query? or is there another reason for doing this.
i.e you mention fix table in memory?? could you please inform me what this means? to do with amount of memory it uses up?, thanks, steve
SergeiBaklan
Jul 22, 2021Diamond Contributor
Nope, that not necessary improves performance. The goal is to ensure your table will be sorted correctly. Due to so called lazy evaluation Table.Sort() may sort the table only partially by parts which are currently loaded in memory. The workaround is to push loading of the entire table into memory using Table.Buffer() as here Remove Duplicates and Keep the Last Record with Power Query - Excelerator BI or by adding/removing Index column which do exactly the same.
Above is not golden rule which warranty result on 100%, but in most cases it works.
Related topic is documented here Common Authoring Issues in Power Query | Microsoft Docs
- stever78Jul 22, 2021Brass ContributorThanks sergei, ill certainly look into this and read through the links you give.
PQ looked easy on the surface. but abit of a rabbit hole on information.
thanks for help- SergeiBaklanJul 23, 2021Diamond Contributor
stever78 , yes, more complex the task and larger the data more deep you need to dive into PQ.