If you use TextField instead of Numaric you have option for ZIP to select in patterns....
Of couse if you want to stick to your Numaric field I would say use num{99999zzzz}...key: You would use 9 when you would expect to see 0-9 no matter what you passed...you would use "z" where you expect nothing prints when there is no data available.
If you use TextField instead of Numaric you have option for ZIP to select in patterns....
Of couse if you want to stick to your Numaric field I would say use num{99999zzzz}...key: You would use 9 when you would expect to see 0-9 no matter what you passed...you would use "z" where you expect nothing prints when there is no data available.
Thank you, it worked. I used the TextField and set up the Display Pattern of all z's.
This way I'm able to enter the hyphen and the last 4 digits of the zip and if there is no extra 4 digits then the 5 zip code will appear without zeros.
The following has evaluated to null or missing:
==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41]
----
Tip: It's the step after the last dot that caused this error, not those before it.
----
Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing#if>. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)??
----
----
FTL stack trace ("~" means nesting-related):
- Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5]
----