Table.NestedJoin and cache problem

[intrasight]

I have a query with a Table.NestedJoin() call which joins two tables which were obtained via Web.Contents() calls.

Each of two tables has 8 rows and final table has 8 rows. The query works. However, I observe in Fiddler that 8 identical HTTP requests are being made for one of the tables. I can understand that the NestedJoin call would need to get the data 8 times from the table being joined. What I don't understand is why the cache isn't being used. Imagine if my table had 100 rows. Now there would be 100 identical calls to my backend web service. This makes no sense.

[mllopis · Accepted solution]

Hi intrasight,

This is a known issue in the M engine. Currently, caching is not always working for Web.Contents function. We don't have an exact timeline for the fix, but it will be in the November update or later (i.e. not in the October update).

Thanks,
M.