Update SharePoint list daily with HTTP request going wrong.

[PaoloBM]

Hi, I'm getting an error after configuring my PA flow.

The flow is below, I'm trying to update the "Created" and "Client Birthday" so the 2 calculated columns based on these values can be updated daily ("Waiting time(calc)" & "Client Age(calc)").

The formula for "Waiting time(calc)" is =DATEDIF(Created,TODAY(),"d").

The formula for "Client Age(calc)" is =DATEDIF([Client Birthday],TODAY(),"Y").

The idea is, for each item send an http request updating the fields with the same value, just to trigger the update to all items/columns.

upper partbottom part

The result is below, and I don't understand the error details, since it should be a simple update task lol.

error

What are your suggestions to fix this or take another approach to this problem?

Thank you.

[v-chengfen-msft · Accepted solution]

Hi @PaoloBM ,

The reason why you met this problem is that:
1.Body's content format error

Here is format

Best Regards

Cheng Feng

[PaoloBM]

Thank you for the reply.

I've overcome this by removing the calculated formulas on the list and now I calculate them via Power Automate daily using the "SharePoint update item".

[PaoloBM]

Hi again @v-chengfen-msft, now I'm having the same issue with another HTTP request, could you please help?

It's a Yes/No choice

The field name in the URL shows: &Field=RiskLevel (I must have renamed it to add the space later.)

That's the flow:

{"odata.error":{"code":"-1, Microsoft.SharePoint.Client.ClientServiceException","message":{"lang":"en-US","value":"The request ETag value '' does not match the object's ETag value '\"79a52562-d0ad-4e21--bdfba772f99d,45\"'."}}}
clientRequestId: e650c21c-cfa7-4661--c246f4c5fa7b
serviceRequestId: 30536ea0-d06b-2000--cb25cf085f4d

I've tried with the values: Yes, "Yes", No, "No, "true", true, "false", false.

They all give me the same error.

Suggestions are appreciated.

Thank you.

[PaoloBM]

Solved the issue, the list name was first called something else and then renamed.

When calling the metadata, it couldn't find the model with the new name, only with the old name.

{
"__metadata": { "type": "SP.Data.<FirstEverName>ListItem"},
"RiskLevel": false
}