Forum Discussion
Can't save dataflow due to cdsaModelvalidationfailed error message
Hi there,
I'm trying to add a new table to a dataflow by inserting data (blank table/copy and paste method) but when I try to save the dataflow it triggers cdsaModelvalidationfailed despite of the fact that no warning message is showed at Power Query.
Error message
I checked here and there is another thread dealing with the same error, but no solution has been posted: https://community.fabric.microsoft.com/t5/Service/Cannot-save-dataflow-due-to-CdsaModelValidationFailed/m-p/4250301
Thank you for reaching out to the Microsoft Fabric Community Forum.
The answer provided by GilbertQ was indeed correct. In addition to that, I am including some more points that might help.
The error CdsaModelValidationFailed occurs due to issues with the validation of the dataflow model, often caused by incompatible data types, missing required fields, or schema inconsistencies.
To troubleshoot and resolve this issue, please follow these steps:
1. Check Data Consistency:
- Ensure that the column names in the new table do not have unsupported characters or duplicate names.
2. Metadata Inconsistencies:
- Custom tables might have schema conflicts or metadata misalignments. Ensure that metadata, such as table relationships or column properties, aligns with Power BI's expectations.
3. Model Validation:
- Ensure that your data model is valid and free of hidden issues. Even if Power Query shows no warnings, there might be underlying issues with the data model that need to be addressed.
4. Refresh and Retry:
- Refreshing the workspace or reloading the dataflow after making changes can often resolve temporary issues related to caching or syncing.
- Additionally, custom tables might encounter issues if the dataflow has advanced features like linked entities or DirectQuery storage.
If the issue persists after these steps, please share the detailed logs or configuration for further debugging.
If my response has resolved your query, please mark it as the Accepted Solution to help others. Additionally, I would appreciate a 'Kudos' if you found my response helpful.
Thank you!
3 Replies
If it is possible to save your data flow without the new table, then there must be something in the copy paste method of the table you are putting in that is causing the issue. The only thing I can recommend is to comment out steps to see what time will eventually resolve your issue for your copy paste table.
Thank you for reaching out to the Microsoft Fabric Community Forum.
The answer provided by GilbertQ was indeed correct. In addition to that, I am including some more points that might help.
The error CdsaModelValidationFailed occurs due to issues with the validation of the dataflow model, often caused by incompatible data types, missing required fields, or schema inconsistencies.
To troubleshoot and resolve this issue, please follow these steps:
1. Check Data Consistency:
- Ensure that the column names in the new table do not have unsupported characters or duplicate names.
2. Metadata Inconsistencies:
- Custom tables might have schema conflicts or metadata misalignments. Ensure that metadata, such as table relationships or column properties, aligns with Power BI's expectations.
3. Model Validation:
- Ensure that your data model is valid and free of hidden issues. Even if Power Query shows no warnings, there might be underlying issues with the data model that need to be addressed.
4. Refresh and Retry:
- Refreshing the workspace or reloading the dataflow after making changes can often resolve temporary issues related to caching or syncing.
- Additionally, custom tables might encounter issues if the dataflow has advanced features like linked entities or DirectQuery storage.
If the issue persists after these steps, please share the detailed logs or configuration for further debugging.
If my response has resolved your query, please mark it as the Accepted Solution to help others. Additionally, I would appreciate a 'Kudos' if you found my response helpful.
Thank you!
Hello v-karpurapud ,
Thanks for your reply. In my case, the problem was a column name with 353 characters. After trimming its text to less then 256 characters everything worked fine.Thanks for your tips.
