Need urgent help - After Solution deployment Issue - getting error: "Network error when using Patch function: The requested operation is invalid." - In UAT managed solution.

(0) Share

Report

Posted on by SueA

559

Hi:

DEV - Unmanaged Solution with SharePoint as Data Source.

UAT - Managed solution with different set of site and lists as Data Source.

PROD - Managed solution with yet again totally different set of site and lists as Data Source.

After migrating my solution from DEV (unmanaged) to UAT (managed), when I try to create a Task to do the testing in UAT using my Canvas Power App, I get the following error:

Network error when using Patch function: The requested operation is invalid.

Googling the error, I found the below article:

https://stackoverflow.com/questions/77388158/how-to-solve-the-network-error-when-using-a-patch-function

And verified and updated all the fields for all the SharePoint lists and libraries for this project and still the error is occurring.

What else can I do?

Any suggestion is appreciated.

SueA.

P.S.: I have migrated my solution to the PROD (Managed) environment as well and no error is in PROD!! FYI.

Categories:

Building Power Apps

All responses (4)

Answers (1)

Sort by

Ami K 15,689 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@SueA - are you using Environment Variables? Are you patching to your data source using the Submit Form function or via a Patch?
SueA 559 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Amik:
Yes, I am using Environmental Variables for each API Step in all of my 7 FLOWS. I am using Submit Form Function. I am able to see my data in Canvas App accurately. I am able to create an ITEM successfully. However, for any given ITEM, I am unable to create a TASK for some reason. I matched up all of fields in UAT with DEV and PROD SP Lists' fields in both naming conventions and data types. The DEV and PROD work without any issue. The process of Migration from DEV to PROD and DEV to UAT are identical except pointing to the respective SP Site and SP lists.
Thanks,
SueA.
Verified answer

Ami K 15,689 Super User 2024 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!
@SueA I do not think Flows have any relevance to the problem. I assume you're also using Environment Variables as your data sources.

I have no idea what an "ITEM" is or what a "TASK" is (I do not know your app).

Some classic checks:

Check if you have any required fields in your data source and whether your Form is populating those fields with data

Remove a DataCard from your Form and then execute the SubmitForm function, keep repeating this until the Form successfully saves. You can then pinpoint which field is causing the error.

Check if you are patching text values to a number column (and vice versa)

For SharePoint, check if any of those fields have "enforce unique values" enabled and you're not patching to a field which already has the same value

If any of your fields are of Choice field type, check if the choice from the combo box/dropdown in your app exists as an the available choice in the SharePoint list. If not, you will need set the SharePoint choice column to allow “fill in” choices (or select 'can add values manually' in modern SharePoint).

Check the number of people columns in your list. The threshold in a single list is 12 Lookup columns. You start out with 2 out of the box people columns (created by and modified by), so you actually then only have 10 LookUp columns left to work with (people columns are also classified as LookUp columns).
SueA 559 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi, @Amik
You are right on the target in the above response.
I had a few later added columns in UAT SP List did not quite conform to DEV SP List. For an example the column name in DEV was CompletionDt as compared to in UAT it was CompletionDate and such similar irregularities once corrected, the issue now has been resolved.
Many thanks for your timely response.
I appreciation,
SueA.