Forum Discussion
DM_GWPipeline_Gateway_MashupDataAccessError
I was able to resolve the issue by explicitly naming the columns in the table when accessing the schema.
Please see below the step that was added to the query.
pv_jobcosts_Table = Table.SelectColumns(dtl_radius_10_1_Schema{[Name="pv_jobcosts",Kind="Table"]}[Data],{"compnum","plantcode","jobcode","stepnum","costcatnum","costcatsubnum","costcattype"})
The dataset is refreshing without any error after this was added.
Hi connectprince,
Thank you for reaching out to the Microsoft fabric community forum. Thank you GilbertQ, for your inputs on this issue.
After reviewing the details you provided, I have identified few workarounds that may help resolve the issue. Please follow these steps:
The error DM_GWPipeline_Gateway_MashupDataAccessError, with the message ODBC: ERROR [01S07] Fractional data truncated while performing conversion, occurs during the cloud refresh of your Power BI dataset due to data type conversion issues, specifically with fractional data truncation. This issue is specific to certain tables like pv_jobcosts and does not happen during desktop refreshes.
Ensure the privacy levels in Power BI Desktop align with those in the Power BI Service, as inconsistencies can cause refresh issues.
Navigate to the data source settings in the Power BI Service and set the privacy level to "Organizational". This method has resolved similar issues for other users. Check the data types of columns in the problematic tables within your Enterprise Data Lake and ensure they match the expected types in Power BI, especially date or decimal types to avoid truncation errors.
If using external tables, ensure the data types in Power BI match those in your source. For example, using DATETIME2 instead of DATE has resolved similar issues in SQL Server environments. Refreshing the connection credentials in the Power BI Service can resolve authentication or connection issues. If using an on-premises data gateway, consider restarting it or ensuring it's updated to the latest version, as resetting the gateway has resolved refresh issues for some users.
In Power BI Desktop, go to "Transform Data" and review each step in the Applied Steps pane for the affected tables. Look for any transformations causing data type issues or truncation, and simplify or modify them to ensure compatibility with the Power BI Service.
You might want to check out these solved threads they cover similar errors related to gateway configuration, credentials, and privacy level mismatches:
Solved: Re: DM_GWPipeline_Gateway_MashupDataAccessError - Microsoft Fabric Community
Solved: DM_GWPipeline_Gateway_MashupDataAccessError - Microsoft Fabric Community
Solved: DM_GWPipeline_Gateway_MashupDataAccessError - Microsoft Fabric Community
Make sure all your data sources are mapped in the gateway, credentials are updated, and privacy levels are consistent.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you for using Microsoft Community Forum.