Forum Discussion
Some embedded tiles doesn't load, others load fine
Hello guys,
Indeed, it turned out that my new reports that don't work were report tiles. Individual visuals from those report work fine. So now I need to redesign the way the tiles are embedded into my application, but at least I can make them work.
However I didn't find any sign of the limitation of the tile types mentioned anywhere. Can you please point me to the documentation of the supported tile types? It would be important to know wheter the remaining type of tiles are going to be supported in the future, or we have to stick to those available right now.
Thanks,
Tamás
Currently Report, Model tiles are not supported. In a process of adding this information to the documentation.
Sorry for the inconvenience, Irina
Hi Irina,
I wonder if you could share any insights on the roadmap of the various tiles currently not supported to embed. It would be great if we could have a hint by when are they going to be supported if ever. At least approximately, such as a quarter would be appreciated.
Cheers,
Tamás
Hi Tamás, we are usually not sharing the dates and just send anoncements when ready:)
I can say that very soon we will return empty embed URL for the tiles that we are not supporting, so you can skip them in your application.
Can you please explain your scenario? I would assume that you are not blocked by not embeding the model/dataset tiles (they are kind of useless), report tiles are also not so interesting in the embed scenario (IMHO) because you can embed the whole report using report embeding and get interactive experience.
Thank you,
Irina
Hi Irina,
Thanks for the info. Empty embed URLs for the not supported tiles is a great help, especially if they would be accompanied with a flag in the tile description indicating that it is not supported. If the URL is simply empty, then how would the developer know why? I will know it now, but the rest of the community might not have an idea and would assume it is a bug or something else.
The business scenario in our case is the following:
Interactive tiles are needed, but typically only one tab of a report. And the page/report level filters should not be available to the user running the report. We need to pre-set the filters (query string parameter at the end of the embed URL), and we don't want the users to be able to clear / modify them. The filters would be generated in the web app based on complex circumstances coming from the app. E.g. the organizational unit of the user combined with some other metadata - determined either based on the user context or criteria set in the web app - would end up in a number of filters for the report, which we would set for the user instead of asking him to set the same manually one by one in Power BI. We could define different reports for these presets too, but that would be impossible to maintain with large number of users.
This is primarily due to security reasons (kinda row level security), but also for eas of use.
Performance: embedding a tile is more lightweight than embedding a report. In our experience tiles load faster than reports.
Maintenance: we would have a few large reports with lots of tabs defining individual reports. We would maintain them centrally as single entities, then embed the necesary selected tabs of these reports into the web application based on the actual need. Some cases we would embed only one tab, some other case 3-4, some other cases a different set of tabs.
So at the end we would embed report type tiles instead of visual type tiles. This way we would have a clean and minimalistic user interface, where the users can focus only on the report itself, and the filters / other tabs of the report won't be displayed at all. That would be the ideal scenario.