Has anyone had any sucess in using the PowerBI connected system and components?
Whenever I try to use the reportField function, I only get "" (red brackets) on the interface. If I check the Developer Tools on the browser, the call to GenerateReportEmbedToken returns the folowing error:
Could this be something related to security/permissions on Azure/PowerBI? Any ideias?
Discussion posts and replies are publicly visible
Have you ensured that your api has delegated permissions to the Report.Read.All for the Power BI Service and that an admin has consented? See the example below:
Also note that it may take a minute or two to take effect if you make any changes
Thanks Domen, permissions for both of these have been set within the Power BI Service by an O365 admin, however, we're still seeing this error.
Is there anything else that could be interfering with this connection? Or anything else we can try?Also - originally just red square brackets on the interface, same error in the dev tools but error reads [type:INVOCATION_ERROR,error:[error:ACCESS_TOKEN_NOT_FOUND_CODE]]). Any thoughts?
Did the end user ever verify their connectivity setup: This can be done either via an authorization link paradigm https://docs.appian.com/suite/help/19.2/authorization_link_component.html or by having the user click authorize on the connected system.
Hi Domen Jemec
Yes, we already have done that step.
PowerBI Connected System config:
We now are experiencing a new error:
[type:INVOCATION_ERROR,error:[error:com.appiancorp.connectedsystems.templateframework.functions.pipeline.proxyDecoratorPipeline.TemplateInvocationException: Contact the developer of this template to resolve the following issue. com.fasterxml.jackson.databind.JsonMappingException: No content to map due to end-of-input at [Source: java.io.StringReader@1c7e61d9; line: 1, column: 1]]]
japc Did you ever get a resolution for this issue, I'm seeing the same error using the connected system
rodgraham no, we ended up following another approach. We never managed to put the PowerBI component to work...
I usually see this error when PowerBI Service permissions aren't granted. I usually try adding them all first to test.
Also there is a new Connected System included in the PowerBI Zip File that allows retrieval of access token with Password Grant type. It might help testing with that as well.
Just chiming in here that these permissions (on the Azure admin side, which I have no control over) were the trick to getting the component to successfully show data on-form. Prior to that, I was able to successfully query metadata about reports, groups, etc, via the connected system, but actually getting the component loading wasn't working. For me (in 20.4) it was just showing a plain blank box.
© 2021 Appian. All rights reserved.