nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Create an Opportunity Attachment & Create an Action Attachment Bad Gateway Request

Adelle Mantle

Hello,

Recently, my Power Automate Flow, which creates a letter then saves the Sharepoint link of that letter as an Opportunity attachment & as an Action attachment, keeps failing with multiple BadGateway errors with the 502 status code. Because the Create an opportunity attachment fails, the Flow keeps trying to create the same letter, and we end up with multiple copies of the letter on our Sharepoint.

When I check the Sharepoint sharing link that's generated in the Create sharing link for file or folder step, it's a valid link. And the Create an Opportunity Attachment and Create an Action Attachment are pulling the same Sharepoint link that was previously generated.

I've also noticed that after the Flow fails and I go into the Opportunity record in RE NXT web view, I see the error “Sorry, something went wrong.” under the Attachment tile.

Does anyone know what might be causing these BadGateway Errors?

3ec352e47eb85cb28ed8cd40f5904493-huge-sc — Sharepoint Create sharing link to file or folder

1c3c42df4af6c59c073bdcb1e2e801c1-huge-sc — Create an opportunity attachment

1617fb1fc54cc06cab351f8e0131b91a-huge-sc — BadGateway 1

4b786eb6853e772fc624ab8601f37888-huge-sc — BadGateway2

8a3b658ad325b38fd3a608450af33962-huge-sc — Create an opportunity attachment inputs

21812f751facbac1ddd426ad714c98aa-huge-im

Find more posts tagged with

Microsoft Power Platform

Comments

Alex Wong

@Adelle Mantle
I have no problem using the Power Automate connector action to create a link type attachment on opportunity

644875c07667ae79310c5c781f7ded89-huge-im

So the question then becomes:

is the Opportunity ID correct? this has to be the opportunity system record id, not constituent id
https://host.nxt.blackbaud.com/opportunities/75
when you are on the opportunity page, take a look at the URL, the numbrer after opportunities/ is the system record id
the “Name” field has a 150 characters limit, make sure you not exceeding that.

Adelle Mantle

@Alex Wong
Hi Alex!

The Opportunity ID is correct as the Flow doesn't have any issues updating the Opportunity Status. I'll also say that this flow was created back in 2022 and has been running successfully since. However, as of Thurs 6/26, we started getting these BadGateway errors.

I double checked the File name field and confirmed that the character count is under 150. I've also tried deleting and recreating the Create an Opportunity Attachment as well as making a Copy of the Flow & using that instead, but we are still encountering these errors. To be honest, I'm at a bit of a loss.

212bda24778842e0ba7ec24095b0294b-huge-im

6d04a20d7f5ddf45cd51c947c85adcff-huge-im

e550e37419ba12336a66559ddd34de70-huge-im

Alex Wong

@Adelle Mantle
the icon for the connector looks to be the old connector that Blackbaud no longer update, please use the newer connectors instead

b62b9ca8c2a075e1fa33c5904b1fbee8-huge-im

582344233d1f26de78911af0de3be950-huge-im

Adelle Mantle

@Alex Wong

Thank you so much!! This did the trick! It took a minute to go through and replace everything, but it's run successfully since those changes were made. You're a life saver!