Help! Network error when power automate is connected to the SharePoint list.

[Anonymous]

I am creating a simple form to input request, some columns are requestor name, request titles, description, dates. The form works but I want to create a custom ID for each new submission using the generated ID. Example, ID = 10, the Custom ID column should say Custom-10. This is created by power automate, and it works when I manually create a new item on the list. However, it permanently bricked my power app form. Even after turning power automate off, the app will produce the Network error prompt," the requested operation is invalid".

 Here is the formula used for my patching

Patch('Request', Defaults('Request'),
{Title:"", 'Requestor Name':DataCardValue2.Selected, 'Request Title':DataCardValue3.Text,
'Request Description':DataCardValue4.Text, 'Target completion date': DataCardValue9.SelectedDate}, Form3.Updates);

Notify( "Submission successful!", NotificationType.Success, 0 );

[VauBee]

Hi @Anonymous,

please check if there are any business required columns in your database that are not adressed in your patch. 

If so, either make the optional or include them in your patch.

------------------------------------------------------------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.

If you like my response, please give it a Thumbs Up.  

[SebS]

@Anonymous 

I will say it's more like Your patch fault. From the code you provided, it looks like You passing an empty string to Title and this field is required, so You can't create a record without Title having some data.

place something in Title and check if I'm right do Title:"Test" and run patch.

[poweractivate · Accepted solution]

@Anonymous 

Your Patch formula includes an additional Form3.Updates. Try to remove that to see if the error still persists.

Patch('Request', Defaults('Request'),
{Title:"", 'Requestor Name':DataCardValue2.Selected, 'Request Title':DataCardValue3.Text,
'Request Description':DataCardValue4.Text, 'Target completion date': DataCardValue9.SelectedDate});

Currently you specify Data Cards but Form3.Updates overwrites this anyway when you are using the 4th argument, as it is processing on the same new record Defaults('Request') which creates a single, new record. When using Defaults and you try to use a Table as 3rd argument, it should complain, as Patch bulk new records is not possible using Patch by itself.  So the 4th argument just overwrites the same new record. You already specify DataCards in the 3rd arg, which seems redundant, making the 4th argument overwrite these anyway.

Your Patch should then be just one of these two:

1. Individual Columns Specified

Patch('Request', Defaults('Request'),
{Title:"", 'Requestor Name':DataCardValue2.Selected, 'Request Title':DataCardValue3.Text,
'Request Description':DataCardValue4.Text, 'Target completion date': DataCardValue9.SelectedDate});

or 2. Using just Form3.Updates

Patch('Request', Defaults('Request'), Form3.Updates);

If you use both, you should probably only provide those records which are not on the form's datacards at all as the 3rd argument (such as the blank title, for example)

Patch(
    'Request', 
    Defaults('Request'), 
    {Title: ""}, 
    Form3.Updates
);

See if it helps @Anonymous 

[Anonymous]

The patch was working ok before the power automate was involved. I have used your recommendation and the same error still shows. All columns have been made optional on the sharepoint list.

[Anonymous]

I ve gotten rid of the form3.update, similar error popped up. I went to recreate the same list and app again, this time without power automate involvement and it was able to patch. Any idea how power automate could've caused this?

[poweractivate]

@Anonymous Hmm I see you marked mine already as solution, however, I think the problem could be this:

In Power Automate it depends if you have a Respond to a PowerApp or Flow block present somewhere in the Cloud Flow if your Power Apps Canvas App has multiple statements in the formula.

If present: The Canvas App waits for the YourFlowName.Run to complete before proceeding to the next statement(s) / line(s) of your formula, (whether you actually use the output or not, the Canvas app should actually wait on the Run statement, if this block is present in the Flow, before proceeding to the others).
If not present:  The Canvas App does not wait for the YourFlowName.Run to complete before proceeding to the next line(s) / statement(s) of your formula.

Besides having multiple lines or statements in one formula and the presence or absence of the above block, another problem could be as follows. Depending on how you structured the app, maybe another part of it doesn't have the output of the Flow yet and it may be expecting it to be there. This may also be causing the error. Then it may be some kind of timing issue.
You may want to restructure or rethink that part of the app if this may be the issue.
To better help with that part, I may need more info which parts of the app are expecting there to be a value from Power Automate and where these values are used, to see if maybe you are sending or using values that are supposed to be from the Flow but are actually not yet there in that part of the app, potentially causing your error.
See if it helps in case as well @Anonymous 

[poweractivate]

@Anonymous 
What is the Power Automate Flow and its purpose? Is it related at all to what the Canvas App is doing? Try just removing the Flow entirely and then in your Canvas App, remove any formula statements of the type YourFlowName.Run anywhere you are using such statements.

If that worked, then there's just something wrong with the Flow by itself and how it's being used from Canvas App, not so much with the Patch formula you provided in the original question.

So in that case, the  try recreating the Cloud Flow again and adding it to the Canvas App, and then add the YourFlowName.Run appropriately back in the Canvas App. If the issue persists in the recreated Flow, either you also may not be using the YourFlowName.Run part correctly as well wherever you are using it, or, it's an issue of identifying what you are trying to do with the Flow, what the Flow is doing and how it's being used in the Canvas App. There may be a problem with the Power Automate Cloud Flow and how it was made, or how it's being used from the Canvas App causing the network error.

If the Cloud Flow is erroring out itself fore example that may cause the error you saw in the Canvas app.

See if this additional info helps in case as well @Anonymous