Retrieve Tribute information

Padman DeSilva

can anyone suggest a way to get tribute information to power automate flow. if there is no direct way please let me know the steps in other way to do?

Nicole Holt

We've gone a bit backwards for this and have set up gift attributes to get tribute info (for acknowledgees) and a condititional statement that looks at the reference field for “in honor of….”

It does result in a little extra coding when entering gifts, but not a ton (and we were already using the reference field for the memory/honor info for quick reference).

Stacy Cope

Another way would be to export the information from RE and retrieve it to Power Automate from your SFTP site. With this version, you would need to manually run the export OR use RE:Queue to fully automate the entire process. This template would give you the steps needed to get data from an export into Power Automate:

Maya Rosman

@Stacy Cope has the capabilities to retrieve Tribute information changed since this was posted? My IT person working on a PowerAutomate flow for us is being prevented from adding Tribute information. She gets an error telling her "403 Forbidden" for the "List Gift Tributes" action. There is nothing in her RE permissions that prevents her from interacting with Tributes so we're a bit stumped. Is this just something that isn't possible to do? We just wanted to see if anyone else had cracked this before we look into adding a gift attribute.

Glen Hutson

@Maya Rosman:

@Stacy Cope has the capabilities to retrieve Tribute information changed since this was posted? My IT person working on a PowerAutomate flow for us is being prevented from adding Tribute information. She gets an error telling her "403 Forbidden" for the "List Gift Tributes" action. There is nothing in her RE permissions that prevents her from interacting with Tributes so we're a bit stumped. Is this just something that isn't possible to do? We just wanted to see if anyone else had cracked this before we look into adding a gift attribute.

What you may be running into is that for areas listed under the “NXT-Integrations” APIs (including Tributes), is that one has to be what is currently called an “Environment Admin” to access those, regardless if you're already someone even with Supervisor Rights in RENXT.

Prenger Solutions

@Glen Hutson, thanks for this update! This looks like a great change. Do you know what level of Marketplace permissions will be required for @Maya Rosman 's user, once the change is applied to their environment?

Maya Rosman

@Glen Hutson
Thanks for that! I'm not as familiar with Environment Admin - I know it's not a security setting within RE webview, but I'm less clear on what being an Environment Admin means for the users that are designated that way. I want to make sure we're not granting it to someone who could accidently use it to cause an issue.

Glen Hutson

@Maya Rosman
Here's a KB article that talks about the various levels of Admins. Basically, an Environment Admin is a “Super Supervisor”.

Maya Rosman

@Glen Hutson, thanks! I did look that up. So, just to confirm, Environment admin has supervisor rights + right? Sadly, this won't work for our situation. The person handling the PowerAutomate build should not have that level of permissions. Do you know if there are any plans to change how the tribute information can be accessed for flows? This seems like a really weird restriction case.

Glen Hutson

@Maya Rosman:

@Glen Hutson
Thanks for that! I'm not as familiar with Environment Admin - I know it's not a security setting within RE webview, but I'm less clear on what being an Environment Admin means for the users that are designated that way. I want to make sure we're not granting it to someone who could accidently use it to cause an issue.

Here's an update to new permissions for using those Endpoints and not needing to be an Environment Admin. Hot off the press.

Glen Hutson

@Glen Hutson:

@Maya Rosman:

@Glen Hutson
Thanks for that! I'm not as familiar with Environment Admin - I know it's not a security setting within RE webview, but I'm less clear on what being an Environment Admin means for the users that are designated that way. I want to make sure we're not granting it to someone who could accidently use it to cause an issue.

Here's an update to new permissions for using those Endpoints and not needing to be an Environment Admin. Hot off the press.

It would help if I actually put in a link:

https://community.blackbaud.com/blogs/13/9472