Gen2 Metrics App: Error processing data in dataset

[ScottDunk]

Hi,

We have just switched over to Premium Gen2 and have installed the latest version of the app.

Followed the steps to "connect" and then get red bar at top with "Error processing data in dataset" message.  Cant seem to get anymore detail than that.  Cant download report to check in PBI Desktop.

How do I find a more meaningful message?

[Anonymous]

Can a Microsoft representative confirm this is correct? You have to type the manually 36 random characters GUID. For the capacity metric app? Really? Please tell me this is a joke?

[Anonymous]

Any more info on this? We also recently upgraded our capacity to Premium Gen 2 and I was hoping to use this app but just can't get it to work. I have the same thing where I just can't get more detail on the error.

[Anonymous]

Hi @ScottDunk ,

Please follow the instructions provided by deanismael first to see if it helps.

The app is updated regularly with new features and functionality. Make sure you're running the latest version. 

Please check if the following limitations appear:
The app displays results for the last 14 or 28 days, depending on the visual.

The app only displays memory measurements and performance breakdown for datasets.

The Refresh page shown in the app doesn't work yet.

The Users column in the visuals displays how many distinct users have been using a Power BI item (such as a report or dashboard). When you expand the measure to display user breakdown for different types of operations for this item, counting can become faulty.

Hope it helps,

Community Support Team _ Caitlyn Yan

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.

[deanismael]

Same experience here. Our problem related to the capacity Id, which when re-entered, finally resolved the data set error. 

[Josh_Boj]

Apparently you have to type in the ID...no copy/paste.  Guess I'm an idiot for not trying that earlier, but thought I'd share just in case others were having the same issue.