View form button not displaying SharePoint form and Patched collection data together - struggling to work

[sudosaurus]

I appreciate I've posted something similar on another thread, however that's had no traction, hence why I'm posting again.

As you will see from the below, I have a SharePoint Edit Form control (No item to display) and a gallery at the bottom-right of the screen of which the data source is a collection.

The Edit Form displays correctly when it's a new form and I can also add topics to the collection. Then on the 'Save to SharePoint' button, the SharePoint form is submitted to it's list - I also have a patch function applied to the Edit Form OnSuccess property - which is correctly writing the required data to a secondary list.

On my home screen - I have a list of items in a gallery that are part of the vanilla submit to SharePoint - when I select one of these items, I see the above screen - the Topics are listed but the original SharePoint form information is not displaying.

It's also worth noting that regardless of which item I select on the home screen, all the items in the Topic collection/gallery are always the same - it's not displaying the one associated with the main SharePoint record.

SharePoint Edit Form items are saved to the list: DocData
Collection items are saved to the list: colTopicClaimSP

The OnSuccess property of the Edit Form has the following added to patch the collection to SharePoint:

ForAll(colTopicClaim, Patch(colTopicClaimSP, Defaults(colTopicClaimSP), {spTopic: With({wTopic: LookUp(Topics As Inner, Inner.Topic = Topic)}, {Id: wTopic.ID, Value: wTopic.Topic}), spClaim: Claim, spTopicRAGStatus: TopicRAGStatus, DocDataID: BuildingForm.LastSubmit.ID}));

// THIS WILL CHECK FOR ERRORS
If( IsEmpty(Errors(DocData)),
    // ON SUCCESS
    UpdateContext({locFormDisplayMode: "View"}); // 
    Notify( "Success: Building Safety Case Report - Saved", NotificationType.Success),
    // ON FAILURE
    Notify( "Errors: Unable to Save Building Safety Case Report", NotificationType.Error)
);

// THE FOLLOWING TWO SECTIONS WILL RESET ALL FIELDS WHEN THE FORM HAS BEEN SUBMITTED

// THIS WILL CLEAR FORM VARIABLES
Set(varCurrentRecord, Blank());
UpdateContext({locFormDisplayMode: Blank()});


// THIS WILL RESET CONTROLS
Set(varResetthemAll, true);
Set(varResetthemAll, false);


// THIS WILL NAVIGATE THE USER TO THE SUCCESS SCREEN
Navigate(HomeScreen, ScreenTransition.Fade)

As you can see, DocDataID = BuildingForm.LastSubmit.ID - this is the link between the two lists.

This is the code that I'm using for the OnSelect code for the gallery on my home screen which allows me to view a previously submitted item (not currently working properly):

// Get the record from DocData list
Set(
    varCurrentRecord,
    LookUp(
        DocData,
        ID = ThisItem.ID
    )
);

// Get the related record from colTopicClaimSP list using the ID from DocData
Set(
    varLinkedRecord,
    LookUp(
        colTopicClaimSP,
        DocDataID = ThisItem.ID
    )
);

// Go to TopicScreen
Navigate(
    TopicScreen,ScreenTransition.Cover
)

For the record, this is the code I'm using for creating a new item from the home screen:

// Sets item as new and sets colTopicClaim collection
NewForm(BuildingForm);
ClearCollect(
    colTopicClaim,
    {
        Topic: "",
        Claim: "",
        TopicRAGStatus: ""
    }
);
// Sets item as new
Set(
    varNewItem,
    true
);
//go to new item screen
Navigate(
    TopicScreen,
    ScreenTransition.Cover
)

I've been struggling with this issue for 2 days and have got no further with my app 😞

[MarkBandR]

For your TopicScreen, what are you setting the "EditForm" Item value to? It should be set to varLinkedRecord. You should check that variable to see that it has a value.

Also, it appears that you have a one to many relationship between the DocData List and colTopicClaimSP. This means that your Lookup is only going to return the first record it ever finds where:

DocDataID = ThisItem.ID

I keep reading over your post and it seems that you would want to load the items from colRopicClaimSP 

where DocDataID = ThisItem.ID into a collection instead of a variable.

[sudosaurus]

@MarkBandR I just tried that and I get this:

I don't know why this is so difficult to display a submitted form and a collection together on another screen based on the select item from previous screen?

[MarkBandR]

Is your form laid out as a top section that shows the Item from DocData and a bottom section that is a Gallery linked to colTopicClaimSP? Or is it just a form for a specific Topic from colTopicClaimSP?

If it is the first one, it is tricky sometime to get a Gallery to add correctly into an EditForm. When you are able to get the gallery added inside the EditForm, then you can set the Gallery Items to be something like:

Filter(colTopicClaimSP, DocDataID = ThisItem.ID) where ThisItem is the item selected for the EditForm.

The screenshot you showed above, is that for a Gallery? The Gallery control has an Items property which expects a collection. From the screen shot, Power Apps knows that varLinkedRecord is a "Record". To get a collection, you would need to do something like:

ClearCollect(
    colLinkedRecords,
    Filter(
        colTopicClaimSP,
        DocDataID = ThisItem.ID
    )
);

And then set the Items property of the Gallery to colLinkedRecords.

[sudosaurus]

@MarkBandR - Yes the top section is the SharePoint edit form and the bottom is a gallery which items property is colTopicClaim. The bit on the left with the two drop-downs and Claim text field are standalone controls (not part of a form or gallery) - these Collect data into the colTopicClaim Collection:

Collect(
    colTopicClaim,
    {
     Topic: Topic_dd.Selected.Value,
     TopicRAGStatus: TopicRAGStatus_dd.Selected.Result,
     Claim: Claim_TextInput.Text
    }
);

Ideally Id like saved values to be loaded into the colTopicClaim Collection gallery when the item is selected from the previous screen and I'm not sure what you mean about having the gallery inside the EditForm - do you mean as a child object of the EditForm control or do you just mean on the same page/screen?

[sudosaurus]

@MarkBandR - also, what/where would I be adding this to?

ClearCollect(
    colLinkedRecords,
    Filter(
        colTopicClaimSP,
        DocDataID = ThisItem.ID
    )
);

[MarkBandR]

Is the top part of your form that is linked to DocData coming up correctly? Hopefully it is and you can focus on the lower part.

The OnSelect code from the Home Screen should possible change to:

// Get the record from DocData list
Set(
    varCurrentRecord,
    LookUp(
        DocData,
        ID = ThisItem.ID
    )
);

// Get the related records from colTopicClaimSP list using the ID from DocData
ClearCollect(
    colLinkedRecords,
    Filter(
        colTopicClaimSP,
        DocDataID = ThisItem.ID
    )
);

// Go to TopicScreen
Navigate(
    TopicScreen,ScreenTransition.Cover
)

The gallery on you form should have the Items property set to colLinkedRecords. It should populate if the top part of your form is populating. Also, I don't know how many items (> 5000) you expect in your colTopicClaimSP list as it grows, but you should add DocDataID as an Index.

Once you get the Topic Gallery populating, then you can work on the "Stand Alone" Topic section. That is going to be a little tougher if that Section needs to allow editing of the selected Topic.

[sudosaurus]

@MarkBandR - that seems to work in terms of displaying the correct linked record in the collection/gallery.

How would you suggest what to do next as when adding the Topic, Topic RAG Status and Claim information in the standalone form section on the left (before any of the form is saved to SharePoint) - I could previously see these items appearing in the collection/gallery on the right - whereas now, I don't see that due to the items property being set to colLinkedRecords.

Another thing I've noticed is that when creating a new item from the home screen, whilst all the fields are blank, the collection/gallery on the right shows the last Topic added regardless of it not being relevant to the new item that is being filled out.

[MarkBandR]

Your problem looked interesting so I was building a sample app so I could make sure to tell you the right thing.

Having a one to many relationship between DocData and Topics is an issue in the same form. I saw your other post where you are having a separate form for creating or editing Topics. That is probably a better way to go but you should link the Topics to DocData. The easiest way to do this is to uses the DocData Item ID and a DocDataID field in the Topics List. This would require you to save the DocData item to get theID before you can add Topics for a DocData item.

I am going to look at your other Post now.

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.