I have a requirement where normally an item column field on transactions would be completely hidden and not used, unless the user matches a specific criteria.
So I set up three column fields:
1. a list/record type and sourced to a list/record field on the item record.
2. the other two are date column types sourced to date fields on the item record.
I set all of these to 'hidden' by default. Then in a user event beforeload script, I check for the user criteria and if valid, I set these three columns to be visible. I know that you need to always first set these fields to 'normal' display when bringing a normally hidden field visible so I do this first. Then I set the three fields to disabled (so they are inline displayed).
The two date fields work correctly, with dates appearing as they are sourced in from the selected item. The list/record field however displays the VALUE rather than the text (the integer value of the selected record in the list rather than its display text). I even tried setting the text via script but still displays the VALUE.
If I change the column definition to default to 'disabled' and then go through the same process in the beforeload script, the list/record field works correctly (displaying the TEXT of the sourced list/record field).
Seems like a bug to me, but wanted to get some other developers input if they have seen this and know of a work-around. I want to keep these fields defaulted to 'hidden' to reduce the amount of scripting since they are only supposed to be visible under very specific conditions.
Thanks.