I've posted this problem before but didn't get a resolution. Going to try and explain myself a little better.
I have an App with a form screen that draws the majority of its data cards from a main Sharepoint list.
When using the basic fields that are generated upon linking the data source, the default behaviour of those fields is to preserve the choice that was selected by the user upon submitting the form.
So when a user edits that form, the choice they made previously is preserved.
This is great, and exactly what I need.
However, a couple of the fields I have use custom controls in order to draw data from different sharepoint lists. These are configured as dropdowns also, but they are generating their 'choices' from a list of 'single line text entries' in the secondary Sharepoint list (in other words, they are not a choice column in the Sharepoint list).
My app is set up this way so I can filter these datacards based on the choice made in other datacards on the form.
These custom dropdowns revert back to the first available entry (after filtering) after the form is submitted. It stores the correct choice in the main Sharepoint list upon submission, but upon editing the form, the choice has reverted back.
Eg: User selects 'Week 13' in the 'Week Number' custom control dropdown.
App stores 'Week 13' in the main Sharepoint list upon user hitting submit button
App then reverts to 'Week 01' in the 'Week Number' custom control dropdown.
Because this is a custom datacard, it does not possess the DefaultSelectedItem property.
Has anyone come across this behaviour? Is there a way to preserve/store the choice made in a custom control datacard when the user comes back to edit the form?