My flow reads tables from an Excel file, including several bit or boolean fields, populated with TRUE, FALSE, and sometimes with the word NULL. The column type in Excel is general. The flow reads in the data using the Excel list rows action, then pushes each field into a corresponding column in SQL database tables. When it encounters a NULL coming in from Excel in a boolean field it produces an error stating that SQL expects type boolean, but "NULL" is not valid. I think the problem is that the word NULL is being interpreted as a string by Excel and Power Automate. As a workaround, I check the bit fields (and there are many) for the word NULL using the equals function, and if 'NULL' is found, then return NULL (with no quotes). This NULL with no quotes happily makes it to SQL.
Has anyone encountered this, and found a way to avoid the problem either in Excel or in SQL? This workaround is ok, but labor intensive, as every bit field must be checked individually with an If statement.
