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
Data Pipelines - Run only selected activities
For debugging and testing pipeline activities during development, allow us to select one or multiple activities and run only the selected pipeline activities. For example, I'm working on editing ...frithjof_v5 hours agoCommunity ChampionNew612Views11likes2CommentsSemantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connec...frithjof_v12 hours agoCommunity ChampionNew17Views1like0CommentsBulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change ...vishal14019716 hours agoFrequent VisitorNew6Views0likes0Comments