I am integrating an Azure SQL Database into an app. I prefer NULLs in my database over pseudo-null values, so I selected the "Keep database NULLs" under Advanced Options in the integration. (See image 1 below)

When I add the integration as a dependency within Service Studio, I get the following message:

However, it does let me add the integration as a dependency. When I try to utilize the data in an auto-generated screen, I see the pseudo-null values in all the fields. (See image 2 below)

I could try to handle the pseudo-NULL values myself, but that seems to defeat the purpose of the feature. I'm assuming that the message above is intended to warn me about using this setting, but it doesn't explicitly say that it is the "Keep database NULLs" feature that is being worked on. The advised "Help" -> "What's New" just tells me about searching in keyboard shortcuts.

Am I jumping to the correct conclusion? "Keep database NULLs" is the feature in progress and shouldn't currently be used?

Thanks,

Stu

Image 1

Image 2