Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option List Exports Display Text NOT Field Value #15

Open
ghost opened this issue Apr 24, 2018 · 3 comments
Open

Option List Exports Display Text NOT Field Value #15

ghost opened this issue Apr 24, 2018 · 3 comments

Comments

@ghost
Copy link

ghost commented Apr 24, 2018

FT 3.01 / Windows Localhost install

  1. Create Option List & Assign Field Values and Display Text
    olist01

  2. Link Option List to to Field1/Col_1 in DB - displays as expected
    olist02

  3. Add record

  4. Display record using HTML /Printer Friendly Format - Display Text is shown NOT value
    olist03

  5. Export as XML - <col_1> shows Display text
    olist04

  6. Check database in phpMyAdmin - displays correct field value from Option List
    olist05

  7. 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...

  1. Lies down

Thanks. Apologies if I have completely lost it

T

@benkeen
Copy link
Member

benkeen commented May 2, 2018

Hey @tidalfire - sorry for not responding sooner. Will get back to this tomorrow.

@benkeen
Copy link
Member

benkeen commented 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. :(

@ghost
Copy link
Author

ghost commented May 4, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant