As mentioned in my previous comment, I would say that if we have to use workarounds, it means that the product can be improved with more user-friendly, intuitive and default solution. The idea behind Qlik Sense is the self-service analytics and this kind of behaviour makes it complicated.
The NullAsValue solution cannot be used with QVD optimized load. If I break the QVD optimized load, my load goes from 8 minutes to an hour (I have several dozens of millions lines.. and resident load is freaking slow). Obviously, I cannot use that..
Thank you for your feedback on ways to improve our product. While this is something we understand would be useful, it's not on the short-term roadmap. Please continue to show your support for this idea.
Here's another workaround that I found recently to remove nulls (as opposed to missing)
I just put this at the end of the script as required. So the region code is held in a data table. And some region codes are missing in the REGION table
NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.