Basically I believe the API behaviour has changed, which in turn has broken our client-facing dashboards. Is there any way to force the embedding process to use a fixed API version? Much like the styles are pulled through a version:
The situation is that we have had untouched repot (2 weeks) and untouched code (4 weeks) that was running fine, and now the exportdata command used during initial filter conditions on a slicer throws "Export data is not supported for this visual". And this is happening across many reports in different areas of the site.
Now I think I know 'Why' - basically we have some filters that need to be controlled only be the web-side to make the interface user-friendly. These are 'hidden' by pushing them behind a white square so they are no longer visible but still operational (changing visibility to not-visible breaks slicer so you can no longer interact with it).
However I don't know 'Why now?' this behaviour was fine and now isn't, and from my end we've got untouched codebases that fail in an identical manner which is a pretty strong indicator it wasn't us.
Confirmed to have same behaviour with example app "App owns data".
If you paste the code below into EmbedReport.cshtml and alter the ID of the slicer to one on your first page you can reproduce the error. Slicer should be available on render but this throws an exception into the console, instead of the slicer selections.