Forum Discussion
Gen2 Dataflow Started Failing - Nullable Issue
Hi Mrizzo21,
it seems to me that a null value of the ID column has entered your input data and is giving the error when you refresh the data. The table in the destination is fixed with not null for the ID column. If there always need to be a value for the ID column (which makes sense for an ID column), you could remove the rows where the ID column is null. If you would like to allow null values, you should delete the destination table and recreate it.
Hi FabianSchut, the problem is that I've checked the output queries, line by line, and there are no NULL values being generated anywhere. I've tried looking though the JSON code as well.
This is happened to me as well for the first time today. I have no values that are null and have also filtered to remove empty just in case. It is the column that will be used as the primary key field in SQL.
I'm seeing the same issue.
Sounds like a bug introduced in the dataflows, that they check for nullable columns source<>destination instead of actually checking for the occurrence of null-values in the source.
Anyone had any luck resolving it? My destination table needs the column to be not null.
Also just started getting this issue when trying to re-publish an already functioning Dataflow Gen2. The source field (SQL Server accessed via recently upgraded Data Gateway) is a Primary Key and thus not null. So it's not clear what the system is checking.
