Currently my flow:
I am able to get the site page based on the Uri but cannot figure out how to update the properties.
Solved! Go to Solution.
Hi @scscott,
You are getting this error because your Headers are different. You are using odata=verbose. In my example I was using the odata=nometadata value.
Can you try and use these headers:
{
"Accept": "application/json;odata=nometadata",
"Content-Type": "application/json;odata=nometadata",
"X-HTTP-Method": "MERGE",
"If-Match": "*"
}
Hi @scscott,
Can you try and use the id of the page in the URI field instead of your filter to update the page title. Below is an example of that approach.
Thank you for the quick reply. I tried getbytitle already and that is how i ended up with the filter solution since i was unable to find the file. I did 2 tries based on your image above. The first I used "Site Pages" (as you showed) and the second I did "SitePages" and I received the same error that the flow was not able to find the file. I have attached what the input, output and file information in hopes that you can help resolve this issue.
Hi @scscott,
That folder part is not needed since we are referring to the id. Can you try this URI instead?
_api/web/lists/getByTitle('Site Pages')/items(70)
It appears that we are on a different error.
Hi @scscott,
You are getting this error because your Headers are different. You are using odata=verbose. In my example I was using the odata=nometadata value.
Can you try and use these headers:
{
"Accept": "application/json;odata=nometadata",
"Content-Type": "application/json;odata=nometadata",
"X-HTTP-Method": "MERGE",
"If-Match": "*"
}
User | Count |
---|---|
92 | |
44 | |
21 | |
18 | |
16 |
User | Count |
---|---|
137 | |
49 | |
42 | |
37 | |
29 |