Unanswered

Update Content Approval Status- fails for "Rejected" in Sharepoint List. Automatically puts it as Approval

(0) Share

Report

Posted on by Sherlock Microsoft Employee

I have created an approval flow, with one level of approval. When the "Set content status" equals "Approve" the flow runs successfully. As soon as a user "Rejects" the flow fails with an error of Bad Gateway with four retries. It fails by automatically marking the SharePoint List as APPROVED instead of REJECTED in the Approval Status column of the list.

Categories:

General topics

I have the same question (0)

All responses (10)

Answers (0)

Pstork1 69,026 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Can we see the settings you are using for the set content approval status 2? Something seems to be off. Also, did you check to make sure that require content approval was enabled in the list settings?

Was this reply helpful? Yes No
v-bacao-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @Sherlock ,

Could you share a full screenshot of the Flow configuration? I did a test on my side and successfully set the approval status to Reject.

Besides Badgate way, is there any other error message that can be provided to us?

When configuring, you don't need to set ETag, because you only operate on the list item.

Best Regards,

Was this reply helpful? Yes No
Sherlock Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hey @Pstork1 attached below is the configuration for the Set Content Approval Status 2. Also, yes- content approval has been enabled in the list settings.

Was this reply helpful? Yes No
Sherlock Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @v-bacao-msft. I have attached the overall Flow in the picture below. The Switch statement is basically for populating the e-mail address to which the approval e-mail should be sent to. Let me know if there is any other information needed from my end. Yup I don't even touch the ETag section. Refer to my message above in response to @Pstork1 as well for additional configuration information on the "Set Content Approval Status 2"

Was this reply helpful? Yes No
Pstork1 69,026 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Sorry for the late reply. I've been out of town at a conference and haven't had time to catch up. The problem is that you are setting content approval on a file in a document library. That requires that you set the ETag property when applying the content approval. You won't have that property available from the regular trigger because its in the extended metadata. So you need to use a Get File metadata action to get the etag and then supply that when setting the content approval. see the screen shot below.

Was this reply helpful? Yes No
Sherlock Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

"The problem is that you are setting content approval on a file in a document library." - No, I am trying to set content approval on a list item in a Sharepoint list. I don't think I need an ETag for that. Let me know otherwise, @Pstork1

Was this reply helpful? Yes No
Pstork1 69,026 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

You are correct, an ETag is only required if Approving documents.

Was this reply helpful? Yes No
preetipatki 9 on at

Like (0)

Report
Copy link

Link copied!

I am still getting for Set content aaproval status when rejected even if ETAG is not used

Was this reply helpful? Yes No
Pstork1 69,026 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

This is an old thread. You should really post your question as a new request. You'll get a lot more responses that way.

Was this reply helpful? Yes No
mreed772 2 on at

Like (0)

Report
Copy link

Link copied!

I know this is an older thread but i had this issue yesterday. The issue is specific to the "set content approval status" function. The flow worked properly the first time but when i tested out the reject branch of my flow and then went back to try and approve it again I had this issue. What i found that worked for me is to add a check out and check in (publish) step just before the "set content approval status". When doing this you will have to pull the metadata again since the Etag will change.

Was this reply helpful? Yes No