Who would benefit? |
Syndicate user |
What impact would it make? |
More customer friendly, less unneeded CVL's |
How should it work? |
Add an option for the CVL-based input parameter option to choose for either Key or Display Value usage in the custom function |
Why is it needed? |
In my use case, the input parameter CVL key does not exist in the CVL against which I'm comparing. With that CTX function you pull the CVL value, hence the check doesn't work out. Two options left to solve this:
If in the input parameter option I could choose to use display value instead of the key, this workaround is not needed... |
Additional feedback, background or context:
Could you remove the CVL from the input and let the mapper just input any Country Code instead of choosing from the CVL?