The API to get refresh history does not include the error message for failed refreshes. If you look in the service and view the history you'll see something like this: Underlying error message: AnalysisServices: The connection either timed out or was lost. or this: Underlying error message: AnalysisServices: Server: The operation was cancelled because of locking conflicts. (both very helpful) However if you pull the refresh history from the API you only see this (the exact same message) for both failures: 'serviceExceptionJson': '{"errorCode":"DM_GWPipeline_Gateway_MashupDataAccessError","errorDescription":"-2147467259."} (not very helpful) We need the 'Underlying error message' to surface in the API.
1 Comment
- fbcideas_migusrNew MemberStatus added:Needs Votes
Recent ideas
notebookutils.runtime.context['userName'] doesn't work for Workspace Identity or Service Principal
Please make notebookutils.runtime.context return the name of the Workspace Identity or Service Principal when running a notebook under such identities. userId is populated with the object id of the ...frithjof_v1 hour agoCommunity ChampionNew11Views0likes0CommentsAzure Key Vault Support for On-Prem SQL Connections
Enable Azure Key Vault integration for on-premises SQL Server connections configured through an On-Premises Data Gateway, allowing customers to: Store SQL Server usernames and passwords in Azure Ke...RohiniUppu5 hours agoMicrosoft EmployeeNew5Views0likes0CommentsChange the behavior of Fabric View (design experience) for clicking on Workspace in Navigation
Microsoft added or revamped the "design experience" down to two options only: Power BI and Fabric. Fine. Suggestion #1: Get it to REMEMBER the state I left it in when I closed the browser. I'm star...ToddChitt2 days agoSuper UserNew150Views2likes1Comment