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
Custom visuals: allow same-tab navigation & reduce confirm-navigation friction for trusted links
Description: Custom visuals (e.g. Deneb) that trigger navigation via href currently have two limitations that create friction for legitimate, author-controlled use cases: Links always open in a ne...AlexSenEON52 minutes agoNew MemberNew5Views0likes0CommentsSeparate Download and Publish Permissions for Power BI Workspaces
Idea / Feature Request Introduce more granular permissions in Power BI to independently control report download and report publishing permissions at the workspace level. Business Scenario We have ...ewarstdhyjugkhi2 hours agoMicrosoft EmployeeNew19Views8likes0CommentsSupport Fabric SQL Database with workspace-level inbound Private Link
Fabric SQL Database supports tenant-level Private Link but not workspace-level Private Link. Securing a small number of databases therefore requires enabling Private Link across the entire tenant, in...WorkFull223 hours agoAdvocate INew31Views1like1Comment