First Submission of Modern Form never updates Choice/Dropdown Fields

[DanielPfaff]

Hi Community,

I have built an App for our CR Management and I only encounter the issue on one of the screens and am unable to figure out the root cause of the issue. I have a form that populates based on a table selection and then allows the user to update the CR, change, status etc.. I have attached a screenshot showing the layout of the screen. 

Now the issue is, that when I update the first request after the launch of the app (e.g. status from Development to UAT), the submit form wipes out some of my choice fields, e.g. Request Type, Implementer and some of the people fields. What worries me, is that the fields impacts vary each time so I cannot narrow down what the issue is. The second submission then works like a charme and it updates perfectly. When running the Monitor while in Play Mode to test this, it shows the current value correctly but has the new value as blanks somehow. I have also attached the version history of the related SP item. The highlighted fields were filled but are updated with blanks. The "Update" property looks correct and also works on all other occassions. 

I should add that it's a modern form with modern choice/dropdown/combo fields. I have added the "Value" parameter to all the controls as I first thought that might be the issue (s. screenshot). The table that you see at the top of the screen is a classic table control (the modern control had some issues). I can also confirm that the submit button only has the "SubmitForm" function. 

There is also an option to Copy a CR using the "Duplicate CR" button that you see on the screenshot. This button opens a popup with another form on the same screen referencing the same table item. However, it's a separate form with separate fields so I don't see a reason the two forms should interfer. 

Based on all the behavior I experienced so far it feels like the form is not caching the values from the selected item properly. 

As we are planning to launch the app next week, I'd greatly appreciate any support/tips/hint the community has to offer as the inconsistent behavior is not really an option. 

Thanks in advance! 

Daniel

[v-jefferni · Accepted solution]

Hi @DanielPfaff ,

For the modern form control, when the data card value control (modern Combo box) is referring a Choices or LookUp column that allows multiple selections, the DefaultSelectedItems property is default to [Parent.Default] and it will case issues. Please remove the brackets, make it to be Parent.Default:

There is no need to add a Value field for the control.

Best regards,

[DanielPfaff]

You are an absolute life saver! Thanks for this - the issue seems to be resolved. 

However, wondering why it would by default be [Parent.Default] if it's known to cause issues? I would expect that by adding the modern form control, it would respect this when it's a choice field. 

[v-jefferni]

Hi @DanielPfaff ,

Modern controls are in preview, so, it will be fixed later when the feature goes into public. 

Best regards,

[DanielPfaff]

Hi @v-jefferni 

Thanks for the clarification. Unfortunately, it happened again despite making the suggested changes. Please see below the changes I have made as well as the result of my recent test:

Property of my Choice Field (Implementer) and associated Default / Update of my DataCard: 

What I notice is, that the below appears when hovering over the Default:

Here's the version history from SP (the other blank fields here have the same issue and are also choice fields):

Any ideas?

Thanks!

Daniel