Forms with steps : It create a record in the model-driven app when i click next after the first step

(0) Share

Report

Posted on by ALP2

242

Hi,

I don't know what's going on.

I have a multiple steps form and a model driven apps that i use to store the data from the form.

The form has 4 steps. When i click next, to go to the 2nd step, a record is created in the model driven apps while the input is not finished.

How to avoid this behaviour ?

I made a video to show you what's going on

https://1drv.ms/v/s!AoEBGFd4Hq6IyOg2rz0B71_fpcG5Hw?e=k17NrB

Categories:

General topics

I have the same question (0)

All responses (4)

Answers (1)

Fubar 8,338 Super User 2025 Season 2 on at

Like (1)

Report

This is how the Advanced/Multi-Step Form works, any Insert step will create a record in Dataverse. . If you are using the same form you can try setting generate steps from tabs option - believe this will save on the last step.

The general workaround, is to set a Status Reason during the create (usually via Metadata on a Basic form etc) e.g. set it to Draft, and on the Form being used for the last Step set it to another value e.g. Submitted.

Was this reply helpful? Yes No
ALP2 242 on at

Like (0)

Report

Argghh it's not working.

I tried also with load form in the field type..no change.

Do you have an article to share for the workaround ?

Was this reply helpful? Yes No
Verified answer

Fubar 8,338 Super User 2025 Season 2 on at

Like (1)

Report
Generate Steps definitely only creates the record on the Submit button (not the Next/Previous). Make sure that you cleared the portal cache (synch or _services/about with Adminstrators Web Role) - note, Generate Steps is the only one that gives a Next without a save to dataverse.

No article to share, steps would be
Edit Status Reason column on your table, add in whatever extra ones you want and can rename the existing one (take not of the Values of the items)
Publish the Table change
On the Advanced Form Step add a Metadata record (if not displayed as a Tab on the Step, look under the Related tab)
Type = Attribute
Attribute Logical Name = Status Reason (statuscode)
In the Set Value On Save section
Tick the checkbox
Type = Value
Value = the Value of the desired status reason (without thousands separators)
note: leave Form Attribute empty in this section (this is used for when you want to set the Attribute to a value currently stored on the Portal Users Contact record.
Save and close the Metadata
(create Metadata as above on the first and last Steps, or have the last step redirect to another Page and on the form of that page add Metadata to it)

Was this reply helpful? Yes No
ALP2 242 on at

Like (0)

Report

Wow.
For a strange reason it was not working with the reason column...the status was stuck on draft value.
So i tried with a new column statuscode2 with the same settings you explaines and finally it's working. i'm very happy and i learnt an another way to use metadata.

I would love to give you 2 kudos but it's not possible. thank you so much

Was this reply helpful? Yes No