Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unclear what target Workspace info to specify ("unsupported data format : text/html; charset= utf-8") #58

Closed
fordmaxson opened this issue May 27, 2020 · 7 comments
Closed

Unclear what target Workspace info to specify ("unsupported data format : text/html; charset= utf-8") #58

fordmaxson opened this issue May 27, 2020 · 7 comments

Comments

@fordmaxson
Copy link

fordmaxson commented May 27, 2020 •
edited

I am a Power BI user attempting to implement incremental refresh and running into the issue defined at the bottom of https://docs.microsoft.com/en-us/power-bi/admin/service-premium-incremental-refresh.

I would like to use ALM Toolkit to update my BI report (charts, measures, etc.) while leaving the underlying dataset alone on the server (which has been incrementally accruing data).

When it asks for a target workspace and I enter something like "https://app.powerbi.com/groups/76288xxx-26xx-4cxx-a7xx-xxxxxxxxxx"
I get
"unsupported data format : text/html; charset= utf-8"

I am not clear on where to go to get the correct workspace string and what format you are looking for.

Thanks for the help.
@dylanjmorgan
Copy link

dylanjmorgan commented May 27, 2020 via email

@fordmaxson
Copy link
Author

fordmaxson commented May 27, 2020 •
edited

Thanks for response.
That got me a "ClaimsToken Authority Not Found"

Is there any supporting installs required? Where does my login and password come into play here? Also, my workspace name has a ":" in it. Is there a way to encapsulate special characters?

@christianwade
Copy link
Member

Is your workspace on a Premium capacity? (xmla only works on Premium). If yes, Dylan's format is correct, but you can confirm by copying from the workspace settings.
https://docs.microsoft.com/en-us/power-bi/admin/service-premium-connect-tools#connecting-to-a-premium-workspace

@fordmaxson
Copy link
Author

OK, I am not on Premium, but we have purchased Embedded via an A1 server on Azure.
I dug through more of your documentation and went and installed Visual Studio Community and installed the 2 extensions. At that point I just left it running. Have not pulled any code into Visual Studio.

So success! I am now able to get ALM Toolkit to run a comparison between my pbix on Desktop and what has been Published.

I inserted a simple text box into my pbix report view. Unfortunately, I see nothing in the comparison tool that caught this. My goal is to leave all the data alone and just send up the new page with the new text box.

Help?

image

@christianwade
Copy link
Member

Great. Glad you got past that hurdle.

If you're on Premium (including A skus) you shouldn't even need VS or the extensions if all you want to do is run ALM Toolkit.

It won't pick up (or deploy) report changes. It's only for datasets. You may want to copy the visuals into a separate live connect report to separate it from the dataset for ease of redeployment. Deploying the report alone normally doesn't have much overhead

@fordmaxson
Copy link
Author

Very frustrating, Microsoft keeps having us have to upgrade, change, switch to something else to get features working. The doc at https://docs.microsoft.com/en-us/power-bi/admin/service-premium-incremental-refresh should be updated to indicate ALM can't update just the report. It's misleading and the whole point should be how do you update the report without messing up the dataset that used incremental refresh.

Our datasets query mySQL. Not sure if I can do a live connect report as a result. Also not sure if live connect is available on our embedded A1, if there is a cost impact, performance impact. More research and hunting...sigh

Thank you for your help though.

@christianwade
Copy link
Member

That's a fair point about updating the documentation about this. I'll submit the request today.

There are technical reasons why XMLA write doesn't work on Pro. We could enable read only access, but currently focusing on getting it (& large models) to GA.

Not sure I understand the live connect over mySQL scenario, but there should be no feature loss on an A1 AFAIK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@christianwade @dylanjmorgan @fordmaxson