Mobile App - Drop Down/Typeahead fields not saving in Drafts or Submit

[ScottMo1]

We have a Request Queue with a custom form attached that the user must complete certain fields.   Of the fields there are 4 that are either a drop down selection or typeahead.   The web version works with no issue.   All fields function properly and the user can save his/her work as a draft or submit the request.

If the user chooses to use the mobile app to complete the request and either save or submit, the drop down fields and typeahead fields do not save and in some instances will not let the user submit because if thinks one of the fields is not complete (because all four of these fields are required).   

The user (and I was able to duplicate) will complete the request on the mobile devise, but when looking at the Draft Requests on the web version, all of the data is complete except these four fields that are either drop down or typeahead.

I went down the path that maybe these fields were not shared properly.   I opened up the sharing rights, but that did not fix the issue.

Any ideas on what is causing the Mobile App to behave differently on these types of fields (btw - the fields that are working are text fields and date fields)

Thank you

[monicacardoso]

Hi @ScottMo1, 

Thank you for your question! I know that External Lookup fields are not supported in the mobile app, but I haven't heard anything about Dropdown and Typeahead fields. If this is something that you can consistently replicated, I would suggest submitting a ticket to the Workfront Support team (if you haven't already) and including screen recordings and examples of the behavior. 

We will then be able to reach out to the Product/Engineering teams and confirm the intention behind this behavior. 

- Monica 

[ScottMo1]

Thank you - I also submitted a submitted a support ticket.   No response as of this morning.

[kautuk_sahni]

@ScottMo1 Just checking in. Were you able to resolve your issue? We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could benefit the community. Thanks again for being part of the conversation!

[ScottMo1 · Accepted solution]

Hi Kautuk - this was a programming bug with the mobile app.   It had to be resolved by the engineers.   Took them a few weeks to work through the issue - we are now fully functional in the mobile app.   

Thanks,

Scott