You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Option List Exports Display Text NOT Field Value #15
Create Option List & Assign Field Values and Display Text
Link Option List to to Field1/Col_1 in DB - displays as expected
Add record
Display record using HTML /Printer Friendly Format - Display Text is shown NOT value
Export as XML - <col_1> shows Display text
Check database in phpMyAdmin - displays correct field value from Option List
Scratch head - I am missing something obvious - Option list export value should be exported?
Option List display text should only appear in For Tools UI (internal form page)?
Trying this with external form - data saved OK in db but when exported as XML for round trip to another system incorrect option list value is exported.
Can workaround by making display and value exactly the same but...
Hey @tidalfire, so it turns out this is working as designed. :) In all cases - even export - it'll favour the display text over the actual value in the database. It was a judgement call on my behalf, but to be honest, now I can see both sides.
I originally include the display value for option lists just so you could minimize the amount of data actually stored in the database: a single char could represent a massive long string displayed to the user.
But I'll put this down as a feature request, since I gotta say, it's pretty reasonable to need the display value during export - just like with the DB. I took a look through the code to see if I could come up with a recommendation of a workaround, but there's really nothing that easy I'm afraid. :(
Activity
benkeen commentedon May 2, 2018
Hey @tidalfire - sorry for not responding sooner. Will get back to this tomorrow.
benkeen commentedon May 4, 2018
Hey @tidalfire, so it turns out this is working as designed. :) In all cases - even export - it'll favour the display text over the actual value in the database. It was a judgement call on my behalf, but to be honest, now I can see both sides.
I originally include the display value for option lists just so you could minimize the amount of data actually stored in the database: a single char could represent a massive long string displayed to the user.
But I'll put this down as a feature request, since I gotta say, it's pretty reasonable to need the display value during export - just like with the DB. I took a look through the code to see if I could come up with a recommendation of a workaround, but there's really nothing that easy I'm afraid. :(