Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
Hi everyone,
I am new to Appian and facing challenges in using customFieldPicker, we need to implement:
Do we have any Field where user can search for exiting list of values from database, and if value(text column in our case) is not there in the list then whatever value user has typed in can be written to DB on the form submission. Later the value will become part of the list.
We implemented it like this:
We have one table having 2 fields- id and text only. The ER we created is attached below:
We are unable to save the value. Please let me know what I am doing wrong.
Thank you!
Discussion posts and replies are publicly visible
appiant0003 said:facing challenges in using customFieldPicker
TBH it's not an easy component to use, at least if (as in my case) you don't use it frequently.
appiant0003 said:whatever value user has typed in can be written to DB on the form submission
Frankly you'd be better off (in terms of sanity in general, as well as later maintainability) just separating this out to a whole separate field.
For instance you could have the user check a checkbox saying "i need to enter my own new value", and after that, show a text box where they can freely type in the new value. This could be designed as an "alternate field" where it shows up below the original custom picker selection box, or where it replaces the custom picker box altogether in the same spot, such that it appears to have just changed functionality (whereas really in the back-end you've swapped in a completely different component).
Thanks Mike Schmitt