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
Blocker: Purview must scan Fabric Warehouse tables/columns or we will deprecate Purview
Purview + Fabric Warehouse ≠ enterprise‑ready governance. In our environment, the Fabric Warehouse is the system of record, but Purview can only catalog the warehouse container—not the tables or co...Joshua_Hernande8 hours agoNew MemberNew180Views1like1CommentPower Query Parameter create/use when connecting to a dataflow
In power query when you connect to a table in a dataflow there are no options to create or use a parameter for that dataflow. When connecting to SQL there is an option when setting up the connection ...ben_holmes17 hours agoNew MemberNeed Clarification198Views3likes1CommentParameterize Dataflow Gen2 data source connection
Allow the Dataflow Gen2 data source connection GUID to be parameterized and stored in a Variable Library. This would allow the same Dataflow to use different connections depending on the workspace/e...frithjof_v17 hours agoCommunity ChampionNeeds Votes37Views2likes1Comment