You also mentioned dynamic fields. As you design your process, keep in mind that dynamic fields don't store textual values in the form entry where it's being displayed. The field on the linked form stores the dynamic record's entry id. With an add new option, the dynamic field hasn't been created yet. It's not created until after the user form entry.
This means to keep the user entry in sync with the dynamic lookup, you have to write the new dynamic row entry id to the user form dropdown. Otherwise, it won't work correctly when viewing the entry.
Because of the bilateral transfer, this is a lot to test when writing custom code. If you need the help of an experienced developer, please visit https://formidable-masterminds.com/developers-directory/
Thanks Victor - I wasn't too sure what the difference was between Lookup and Dynamic fields. In my use case Lookups seems to be what I require. I will research a bit to see if I can figure out how to implement the "custom code" to insert new values to the lookup table.
This seems like functionality which should be available in a form tool like Formidable Forms without the need of custom coding, a bit disappointing 🙁
Maybe so, but it's not a common request. I've been answering questions in Formidable forums for over a decade and your question has been asked only a handful of time. I suggest you open a "feature request" ticket with Strategy 11.
Please login or Register to submit your answer
I could even do with using a dynamic field lookup of existing values for the Field in the capture form - If a NEW value is required, allow the user to capture it rather than forcing to select from the lookup list.