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
Allow us to rename fabric data agents published to m365
If we use deployment pipelines to promote fabric data agents between dev, test/UAT, and prod fabric workspaces, we need to keep the name of the fabric agent the same in each workspace. If we want to ...PeterDaniels30 minutes agoAdvocate IIINew176Views0likes2CommentsMake workspace and item session persistence optional
Description The new persistent session behavior in Microsoft Fabric should be optional rather than forced. Currently, Fabric remembers the workspaces and items that were open in my previous session...TeemuMultanen1 hour agoAdvocate INew292Views47likes2CommentsSupport Encrypted Sensitivity-Labeled Excel Files in Power Query
Description Currently, Power Query Online and Power Query in Excel are unable to access encrypted Excel files. Excel files with sensitivity types other than Public or Non-Business can be encrypted a...ewarstdhyjugkhi2 hours agoMicrosoft EmployeeNew16Views6likes0CommentsAuto-propagate Lakehouse (Direct Lake) permissions to users assigned to a Power BI App audience
Problem When a Power BI report uses a Live Connection to a Direct Lake Semantic Model, end users must have explicit ReadAll / ReadData permissions on the underlying Lakehouse (or its SQL analytics e...majofv4 hours agoNew MemberNew5Views1like0Comments