Forum Discussion
Dataflow Gen2 refresh issue
Hi pws_flick,
Thank you for reaching out to the Microsoft Fabric Community Forum.
We sincerely apologize for the inconvenience. After reviewing the issue of Dataflow Gen2 refresh issue, here are a few steps that may help resolve the issue.
- Ensure the schema from Dynamics 365 matches the dataflow structure. Even small discrepancies like field names or types can cause issues. Review both schemas for alignment.
- Specifically, check if the Data Source Type column exists in the source and is correctly mapped. Ensure the partitioning column e.g., date or ID is correctly set up and recognized for the incremental refresh. Properly configure metadata like data source type to avoid errors.
- Remove any custom steps or transformations in the dataflow temporarily and rerun it. This can help identify if a specific step in the M code is causing the error.
- If the error continues, try creating a new dataflow from scratch using the defaults without adjusting the M code. This can help determine if there is a deeper configuration issue.
Also, please go through the below following link for better understanding:
Dataflow Gen2 refresh - Microsoft Fabric | Microsoft Learn
Incremental refresh in Dataflow Gen2 - Microsoft Fabric | Microsoft Learn
If this post helps, please give us Kudos and consider accepting it as a solution to help other members find it more quickly. Also, if you have any further queries, please feel free to reach out to us, and we will guide you accordingly.
Thank you.Hi pws_flick,
Thank you for contacting the Microsoft Fabric Community.
We apologize for the delayed response. After reviewing the details you provided, here are a few workarounds that might help resolve the issue. Please follow the steps below:
- Please consider using Dataflows Gen1 instead of Gen2. Gen1 operates under a different execution model and may not enforce schema validation as strictly as Gen2, which could help resolve the problem.
- If the incremental refresh is failing due to metadata issues, try switching to Direct Query mode for Dynamics 365. This method dynamically retrieves the schema, reducing the chances of mismatches and ensuring more reliable data retrieval.
- Use API pagination and field selection in Dynamics 365. API responses may impose row limits or exclude certain fields by default. Ensuring that all necessary fields are accessible and using a custom FetchXML query for data retrieval can help address issues related to missing data.
- Instead of manually adjusting the partitioning column or data source type, consider reconfiguring the incremental refresh from scratch in Power BI. Refreshing the setup and allowing Power BI to reconfigure the data can sometimes identify and resolve hidden issues related to partitioning and schema mapping.
- The issue might also be due to missing or incorrect references and relationships. Please check the relationships between the "account" entity and other entities in Dynamics 365, such as primarycontactid and ownerid, to ensure they are correctly configured.
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.
Hi v-kpoloju-msft ,
Going through each of these:
Ensure the schema from Dynamics 365 matches the dataflow structure. Even small discrepancies like field names or types can cause issues. Review both schemas for alignment.
Per lists above, the column names and order in source match those in the destination table. Likewise with data types.
Specifically, check if the Data Source Type column exists in the source and is correctly mapped. Ensure the partitioning column e.g., date or ID is correctly set up and recognized for the incremental refresh. Properly configure metadata like data source type to avoid errors.
There is 100% definitely no column with this name in either source (dynamics 365 account entity) or the desination table.
Remove any custom steps or transformations in the dataflow temporarily and rerun it. This can help identify if a specific step in the M code is causing the error.
There are literally no transformation steps in this dataflow. It is basically just what you see in the M-Code above.
If the error continues, try creating a new dataflow from scratch using the defaults without adjusting the M code. This can help determine if there is a deeper configuration issue.
I am going to try creating a new dataflow and manually delete all the unnecessary columns from source, rather than selecting them in M-Code.
Given Dynamics entities contain hundreds of columns of 'dynamics boilerplate' - this will be a frustratingly slow process 😂 Nonetheless, I think it's my only option at this point.
If this doesn't work, I think I will just abandon Dataflow Gen 2 and try an alternative approach haha
Hi pws_flick,
Thank you for contacting the Microsoft Fabric Community.
We apologize for the delayed response. After reviewing the details you provided, here are a few workarounds that might help resolve the issue. Please follow the steps below:
- Please consider using Dataflows Gen1 instead of Gen2. Gen1 operates under a different execution model and may not enforce schema validation as strictly as Gen2, which could help resolve the problem.
- If the incremental refresh is failing due to metadata issues, try switching to Direct Query mode for Dynamics 365. This method dynamically retrieves the schema, reducing the chances of mismatches and ensuring more reliable data retrieval.
- Use API pagination and field selection in Dynamics 365. API responses may impose row limits or exclude certain fields by default. Ensuring that all necessary fields are accessible and using a custom FetchXML query for data retrieval can help address issues related to missing data.
- Instead of manually adjusting the partitioning column or data source type, consider reconfiguring the incremental refresh from scratch in Power BI. Refreshing the setup and allowing Power BI to reconfigure the data can sometimes identify and resolve hidden issues related to partitioning and schema mapping.
- The issue might also be due to missing or incorrect references and relationships. Please check the relationships between the "account" entity and other entities in Dynamics 365, such as primarycontactid and ownerid, to ensure they are correctly configured.
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.
Hi pws_flick,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi pws_flick,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.Hi pws_flick,
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If my answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
Thank you.