How to display an editable form in the last page with all their answers

[inanoffice23]

I am trying to get to grips with the whole 'insert data from different forms into different tables', not too sure if it's possible the way I am building it below

If I do 1st form insert, and the rest as 'edit', the forms from other tables will not open

If I do the below, the last form will not open

Form 1 - Insert (main table)

Form 2 - Edit (main table)

Form 3 - Edit (main table) 

Form 4 - Insert (Table 2)

Form 5 - Insert (Table 3)

Form 6 - Edit (main table)

How can I get hold of all the parameters I need to remember from the different forms and tables, and display all of the forms in one page as 'editable' so they can amend the data if necessary? 

I read about local storage, but the samples aren't great, so unsure how to go about it

I hear a lot about workflow, but I didn't see any in action just yet

I believe I read you can create an 'Edit' version of a form, is this true? Do I just name it 'Edit Form 1' and that would work? 

The insert/thing issue confuses me

Thank you!

[OliverRodrigues]

Hi, you have a multistep form that you are pointing to multiple tables, is that it?

If yes, you can't have a single form where you can edit all the information, because there are coming from different tables, users should navigate on previous/next to see the information.

If you want a single form with read-only access showing all the information, you might be able to use embed Quick View Forms to help you with this, but it will depend on the table relationships.

Technically speaking you can always do a custom page using either Liquid or Web API to retrieve the data, but this starts going to a custom approach and not leveraging OOB capabilities.

[inanoffice23]

Thank you @OliverRodrigues yes it will be a multi step form (if I manage not to make it crash)

I will give it a go with the Quick View Forms, there is one main parent table and everyone else will be a child

Is there a way to remember the variables in the final form though? I have to display a list in the end to say 'upload these documents' based on their answers that I am tracking, the issue is that the data is in different tables

[OliverRodrigues]

I will give it a go with the Quick View Forms, there is one main parent table and everyone else will be a child

In this scenario, you should have the parent table and then subgrid to the child tables.. you don't need to navigate to the child table itself, does this make sense?

[inanoffice23]

The form will end up being pretty big, so I can't make all of the children as subgrid, but thank you, I'll see how I get on

At the moment I have to re-do the whole site as we were told Microsoft released an 'enhanced' data model on 12th Dec and better to do it now than later

[Fubar]

What's not 100% clear is your table relationships (2 & 3), are they child tables to Table 1, in which case use Subgrids and insert the records from the Subgrid during the Steps.

The other issue is that you want 1 page with all the details to be editable at the end.  If it is readonly, you could create the page using liquid fetchxml, similarly you could present the readonly page and add links to edit forms, or  alternatively present the page using liquid fetchxml and hook up the Portals Web API to facilitate editing.

The key to all of this is what the Table relationships are, so you can get the appropriate data and GUIDS.

[inanoffice23]

The business wants users to fill one form with 5 different scenarios

To minimise risks and slowing down a database with potentially empty columns, they want to split certain data into different tables

It will all be one record, however some of the tables could have 3 children, some of them could have 1 or 0, and some tables might even be empty, but need to ensure that the one form the user is filling, belongs to the same record

Based on the above, I did

Main table: one to many relationship

From the other side, every child table has a many to one relationship with a look up column to the main table

Thank you for the fetchxml suggestion, I gathered I might have to use that, not too sure how I would add a link to edit the form, I presume I would also have to do 'Edit' forms for them

[Fubar]

If your insert for tables 2&3 could be multiples not just 1 record, then I would put a subgrid on the form for them, you can configure your steps etc to just use a specific Tab (e.g. so you have 1 Tab with a Subgrid for Table 1, another Tab with a Subgrid for Table 2 - and then use  those tabs up as Steps).

If creating manual edits, you would configure basic forms for edit, and then a Web Page for that form, and then in Liquid create a html anchor with the url of the Web Page with the guid as a parameter (default is 'id').  If you use the Web API you could get a bit more fancy and do things like inline editing or popups.

[OliverRodrigues]

The business wants users to fill one form with 5 different scenarios

To minimise risks and slowing down a database with potentially empty columns, they want to split certain data into different tables

I don't think this should be a business user decision, it should be coming from the IT department of your organisation. If you are only going to have 1 record in the "child" tables, ideally you should have the fields in the parent table.

Dataverse is a lot more than a regular Database, creating a table means capabilities for Audit history / a lot of metadata against the data / Permission controls / etc.

my point here is that creating a table won't necessarily be lighter from a database perspective

[inanoffice23]

Thank you @Fubar if there were any samples online I would appreciate it, I will take time to investigate this, at the moment still fighting to link all the tables