We have a multistep form with the first step based on Account table and the second step based on a custom table for storing event registrations for an account. The event registration table has a lookup column to Account table (acountid) and another lookup to the Event table (eventid). The primary key for this event registration table is Record Id.
The first step of the form retrieves the account associated to the signed in user -

The first step is in read-only mode -

The second step of the form is based on the event registration table and is in the insert mode. So the idea is that, every time a user reaches the second step, a new record is created in the Event Registration table. When we reach this screen for the first time, you will notice a new record has been created -

Now a user picks up new event record and submits the form.


You will notice that this record is created in the event registration table -

Now, we wish to create another entry for the same account but for a different event. But when we open the form for the second time, the second step instead of being in the insert mode, shows the record from the dataverse table (timestamp 3:32PM)-

So the issue here is that if we change the lookup and choose EVT-00002 and submit the form, it updates the existing record in dataverse rather than creating a new record with the same account id but different eventid.


You will notice the record ACEV-0022 was updated instead of creating ACEV-0023.
Our table permissions -




Please let me know what could be the issue.