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
Dedicated Fabric Message Center to communicate planned Fabric Changes
Summary Microsoft recently rolled out a change that automatically enabled the Item Recovery tenant setting in Microsoft Fabric for tenants where the setting had not been explicitly configured. Accor...Edgar_1 hour agoNew MemberNew4Views0likes0CommentsWorkspace-Level Control of Storage Modes (Import vs DirectQuery vs Direct Lake)
Organizations operating under strict governance and data residency requirements need the ability to control which storage modes are permitted within a workspace. Currently, report authors can choose...masoodaftab1 hour agoNew MemberNew2Views0likes0CommentsGranular Workspace Permissions Beyond Workspace Roles
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } The current workspace access model is limited to the predefined workspac...masooddevcorp1 hour agoNew MemberNew5Views1like0CommentsAccessibility issue in the Share dialog of embedded Power BI reports
Accessibility issue in the Share dialog of embedded Power BI reports I would like to share an accessibility finding identified while testing an embedded Power BI report published as part of the cont...ugartema5 hours agoNew MemberNew10Views1like0Comments