Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Column 'ColumnName' cannot be null error: though schema set to accept

Hello,
I can't seem to get rid of NULLs appearing in my job (and stopping the mapping due to the above error)
At first I had "Nullable" unchecked, so I can understand the error...
Then I checked Nullable and also gave my fields default values as well (then removed the default values)
Still when I run the job I get the Column 'ColumnName' cannot be null
Ideally I'd like to actually make them not null, but place a default value in them as part of the ETL
Thank You 0683p000009MACn.png
Labels (2)
10 Replies
willm1
Creator
Creator

Probably best to check for both the absence of null and the existence of a value..
row1.FOERNAMN + " " + ((row1.EFTERNAMN != null && row1.EFTERNAMN.length() > 0) ? row1.EFTERNAMN : "")