Our BI team has recently started trialling the ArcGIS for PowerBI to provide a geospatial view and context around their data. There are some feedbacks from them I would like to pass on to our community. It would be much appreciated if the experts could guide us thru the start of the journey.
Unlike app credentials that we can automatically generate and refresh tokens from a server component, for Power BI, we used a named user to run the ArcGIS for Power BI component. It logs out after 10 hours and needs to log back in manually. The GIS team won't change the security policy to make any data publicly available. What is the best practice around the authentication pattern for this use case?
"Can create a join, and it worked initially but now doesn't seem to be connecting (when I click in the table, it doesn't update the map selection and vice-versa)".
"Keep getting the spinning circle once I create a join (it doesn't seem to stop me doing other tasks but not sure why it continues spinning)."
Above are the issues reported by our BI team. It would be great to get some input from experts here.
Issue 1 could potentially also be resolved by switching to SAML based authentication with your ArcGIS Enterprise.
Issue 2 this might be a bug that we have resolved in the next release, that we are handing off to Microsoft today. I'll double check and confirm.
Issue 3 this is a bug and will have to test for a fix and confirm.
I'd love to know more about your workflows, to see if there's something else we might be able to do in place of joins or to see if we need to expand our functionality on the join feature. Please let me know if you have time to talk or direct message about this.
Thanks, Andrew. I will be in touch when I can sit with our BI team to go thru their workflow in more detail. Currently, the product gives them issues that hold them back from trialling it further. Appreciate your response.