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
Fix links generated in multi tenant setups
When I log into Fabric, and I have access to multiple tenants, the links generated for things like monitoring URLs in pipeline runs do not include "ctid=<tenantguid>" query string value, which appear...jwisemanfs2 hours agoNew MemberNew3Views0likes0CommentsDedicated 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_11 hours agoNew MemberNew33Views5likes0CommentsWorkspace-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...masoodaftab11 hours agoNew MemberNew6Views0likes0Comments