Unanswered

Error Handling using Patch Function

(1) Share

Report

Posted on by ashokpershad

321

This error coming after i press the Patch submit button. Before pressing button this error is not showing in formula section.

Everything seems fine but still not resolved.

For details about this issue kindly follow this link:

Patch Dataverse Table with Lookup Columns from Collection

Thanks

Categories:

Error handling

I have the same question (0)

All responses (5)

Answers (0)

CarlosFigueira on at

Like (1)

Report
Assuming that you have the 'Formula-level error management' feature enabled in your app, you can wrap your Patch in an IfError expression as shown below, which will give you additional details about the failure. You can then use the Trace function to log the error, and use the Monitor to look at the trace and see more details on what is going wrong with the Patch.

IfError(Patch(Manhours, Defaults(Manhours), {WOrder:glrySWO_1.Text, ...}), Trace("Patch error", TraceSeverity.Warning, { errors: AllErrors }))

Hope this helps!

Was this reply helpful? Yes No
ashokpershad 321 on at

Like (1)

Report

@CarlosFigueira
I tried same as you suggested but still there are no extra details available. Please have a look at the screenshots.
Also, in 2nd screenshot error seems to be some expected types as "%" but I am not using that kind of field anywhere in my tables.

Was this reply helpful? Yes No
CarlosFigueira on at

Like (1)

Report
We currently have a bug in the Trace function where it is having some problems with serializing records that have enum properties (like the error). I'm fixing it now, but it should be a few weeks before it reaches production. Meanwhile, can you replace the expression with this (wrapping the AllErrors in the JSON function):

IfError(Patch(Manhours, Defaults(Manhours), {WOrder:glrySWO_1.Text, ...}), Trace("Patch error", TraceSeverity.Warning, { errors: JSON(AllErrors) }))

Thanks!

Was this reply helpful? Yes No
ashokpershad 321 on at

Like (0)

Report

@CarlosFigueira
I did that. How is it going to help?
Sametime please note that due to this error even the data is not patching in my data source.

Was this reply helpful? Yes No
CarlosFigueira on at

Like (1)

Report

Hi @ashokpershad that would show more details about the error in the "details" pane in the monitor (which may not be the case with the previous bug).

Was this reply helpful? Yes No