Error opening a dashboard in embedded

[thsilva]

Hi,

I am getting this error below in console when opening a embedded dashboard . 

ERROR Error: Uncaught (in promise): [object Undefined]
at O (powerbiportal.dependencies.externals.bundle.min.122477f826d5ee943110.js:5)
at O (powerbiportal.dependencies.externals.bundle.min.122477f826d5ee943110.js:5)
at powerbiportal.dependencies.externals.bundle.min.122477f826d5ee943110.js:5
at t.invokeTask (powerbiportal.dependencies.externals.bundle.min.122477f826d5ee943110.js:5)
at Object.onInvokeTask (dashboardEmbed.min.1656a8ae4f9c487d78ca.js:1)
at t.invokeTask (powerbiportal.dependencies.externals.bundle.min.122477f826d5ee943110.js:5)
at e.runTask (powerbiportal.dependencies.externals.bundle.min.122477f826d5ee943110.js:5)
at m (powerbiportal.dependencies.externals.bundle.min.122477f826d5ee943110.js:5)
at e.invokeTask [as invoke] (powerbiportal.dependencies.externals.bundle.min.122477f826d5ee943110.js:5)
at g (powerbiportal.dependencies.externals.bundle.min.122477f826d5ee943110.js:5)
vi @ dashboardEmbed.min.1656a8ae4f9c487d78ca.js:1

I think that this error is preventing the tile click to open another report/link. Because when i open the same dashboard in the powerbi portal everthing works and there is no error in console

You can check the same error when opening the dashboard in the playground

https://microsoft.github.io/PowerBI-JavaScript/demo/v2-demo/index.html#

[v-chuncz-msft]

@thsilva 

The issue is reported internally and I will keep you posted with any updates.

CRI 244916198

[thsilva]

tks @v-chuncz-msft .

[v-chuncz-msft]

@thsilva 

When clicking on a tile in a dashboard the action will not occur by design. Instead a tile clicked event will be triggered and your app can listen to the event and open the report/embed the report.

Refer to the following doc for more info on click events (Focus on tileClicked event)

[thsilva]

@v-chuncz-msft ok. tks for the info. we will do that.

That exception not handled will be fixed ?

[v-chuncz-msft]

@thsilva 

We’ve identified the issue. As the fix involves lots of evaluation, coding and testing, there is no ETA at this time.