Meaningful Error Messages

[lee_baldwin]

A feature that would be helpful to speed up troubleshooting for refresh errors is to provide meaningful error messages.

For instance, instead of the error message below:

Data source error: {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"We cannot convert the value null to type Logical."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"Expression.Error"}}],"exceptionCulprit":1}}} Table: Delivery Misses

It could provide something meaningful like:

Error: Cannot convert null to Logical

Table:

Column:

This small change could pay big dividends in time savings for report devs.