Anonymous
1 year agoNot applicable
Status:
New
Better Error Messaging for Refresh Failure
Recently I had a data type cause a failure when refreshing data. I recieved the error message:
"DIM_INSURANCE_PLAN
OLE DB or ODBC error: Type mismatch. (Exception from HRESULT: 0x80020005 (DISP_E_TYPEMISMATCH))".
If it is able to tell me there was a type mismatch error on a field, why can it not tell me what field the error is occuring on? I spent a considerable amount of time researching/comparing the data types manually. If the error is already known, why can the error message not be specific to where the error is occuring? It would be much more user friendly and save time.
No Comments
Recent ideas
Option to set custom width for gridlines OR fixed outer padding
When designing reports, using the align and distribute evenly options in the format pane are useful, however when designing report pages with fixed bleeds between visuals I have to follow these steps...IolaWhiteley9 hours agoAdvocate IINew2Views0likes0CommentsDefault Scrollable Time-Series Charts to Most Recent Data
Currently, Power BI time-series charts always open scrolled to the earliest (leftmost) date by default, which is inconvenient for reports where users are interested in the most recent (rightmost) dat...CStillwell9 hours agoNew MemberNew21Views2likes1CommentOption to Stop Fabric Planning Billing Session After Plan Item Deletion
Currently, a Fabric Planning session remains active for 30 days once triggered. If a user creates a Plan item only for testing and deletes it the next day, the billing session still continues and c...v-dugumarrir111 hours agoMicrosoft EmployeeNew47Views11likes1Comment