URL for Hyperlink Opportunities is Not Working

Austen Brown

I have a opportunity notification summary flow that includes hyperlinks to the opportunity and constituent records. The “https://host.nxt.blackbaud.com/opportunities/[Opportunity System ID]" is no longer working as a hyperlink.

I've included some screenshots of my flow below, and what happens when clicking on the hyperlink within the notification table.

Hyperlink Set-up

Resulting Table

Result When Clicking on Hyperlink in Table

Ben Regier

What about “https://host.nxt.blackbaud.com/constituent/records/[Constituent ID]” for the constituent, and “https://renxt.blackbaud.com/opportunities/[Opportunity ID]?svcid=renxt” for the opportunity? Does that work for you?

Austen Brown

@Ben Regier - The Constituent Record hyperlink within the table works, it is only the opportunity link that is having issues. Unfortunately, your suggestion for the Opportunity link is returning the same result - “Can't reach that page”.

It was working at one point. Could this have something to do with our move to Azure?

Austen Brown

@Ben Regier - Got it to work with “https://host.nxt.blackbaud.com/opportunities/[Opportunity System ID]?svcid=renxt” - Thanks for for your help!

Ben Regier

Yes, I believe moving to Azure could impact this, though I am surprised that the constituent link is still working if the opportunities link does not.

Try this one for the opportunity:

https://host.nxt.blackbaud.com/opportunities/[Opportunity ID]?svcid=renxt

Do you have multiple environments?

Ben Lambert

Hey Austen and Ben,

I can provide a little background on what's happening here...

Many areas of the Blackbaud user interface (across all products) are being updated/modernized/refactored to leverage newer patterns for how we (Blackbaud) build user interfaces. For example, we're shifting from monolithic front-ends (like RENXT and FENXT) to more factored single-page-applications (SPAs) using the latest SKY UX tools and the SKY UX "SPA host" service (runs at https://host.nxt.blackbaud.com).

As part of this effort (which we're doing incrementally), the "location" (i.e., the URL) of the page being updated will change. Some areas of the product may still live at the older, not-yet-updated location while updated areas will all be accessed through the SKY UX host base URL.

For example, the "home page" of RENXT used to be accessed at renxt.blackbaud.com. That page now has a redirect to the "new" home page located at https://host.nxt.blackbaud.com/renxt-homepage. Similarly, the old "constituent page" in RENXT was located at https://renxt.blackbaud.com/constituents/CONSTITUENTID. The new SPA version of the constituent page is located at https://host.nxt.blackbaud.com/constituent/records/CONSTITUENTID. In most (maybe all?) cases, we've implemented browser redirects so that if you have existing bookmarks to the "old" location, the browser will redirect to the "new" location.

So this has nothing to do with "hosted in Azure vs Boston", but more a function of our internal evolution of the product UX.

Now we admittedly haven't formalized any special logic/documentation for how to build links to various areas within the product (and I'd say this problem extends beyond Power Platform, it's an issue in general).

So when you see renxt.blackbaud.com, just know that is an older-style URL for which there's probably a newer-style URL that should be used instead. And when you see host.nxt.blackbaud.com, know that is the SKY UX "Host" service (which handles hosting all SPAs that we create). The first segment in the URL after the SKY UX host base URL is the "SPA name" (for example, /renxt-homepage, /workcenter, /constituent/records/CONSTITUENTID, etc.). Subsequent segments in the URL refer to individual routes within the SPA itself.

Accessing a SPA (via the SKY UX Host) may include/require some additional query params. For example, you may have seen the envid query parameter - this value indicates the customer environment being accessed, and in most cases if omitted (and you have access to multiple environments) the SPA will provide you with an intermediate page for selecting the environment (and of course you have to be logged in and actually able access that particular environment in order to see the page). Similarly, you may have noticed a svcid query parameter (with typical values like `renxt`, `fenxt`, etc.). This parameter indicates which of the "omnibar navigation menus" should be shown. In some cases this parameter is inferred if not provided, but in some cases the SPA will require it (and show the zebra/dinosaur if omitted).

Since we haven't issued any formal guidance (or implemented any helper methods for building links to our pages), my recommendation for now would be to explicitly include both envid and svcid query parameters. Otherwise, when someone clicks your link they may have access to different environments and thus may not see what you are expecting them to see. Unfortunately, it's not easy to get the environment ID from your Power Platform "connection" (we include it, but I don't think there's a way to reference it from within a flow). So until we have a better overall solution, it's best to hard-code your environment ID when building the link. And, make sure you use the SKY UX host URL pattern (unless the page hasn't been updated, in which case you can still use the renxt.blackbaud.com host pattern).

I hope this (long-winded <g>) explanation helps provide some clarity behind what you're seeing and some transparency in our overall direction.

Happy to comment further if you have additional questions, just let us know!
Thanks

Bob Rickards

I have also been trying to get this to work….was a solution found? As the above link does not work.

Austen Brown

Hi Bob - replacing the beginning of the hyperlink for opportunities worked for me. I changed it to “https://host.nxt.blackbaud.com/opportunities/[opportunity system ID]?svcid=renxt”.

Updated Append Array Variable

Bob Rickards

Austen...yeah it worked...it takes me to my RE NXT selection page....we have production and test...once I select production it works. I assume a user with only one choice will be taken to that record. Thanks so much for the help.

Ben Lambert

Hi Bob,

In case it helps - if you append &envid=YOURENVIRONMENTID to the link you're building, you'll be able to skip the environment selection page:

https://host.nxt.blackbaud.com/opportunities/OPPORTUNITYSYSTEMRECORDID?svcid=renxt&envid=YOURENVIRONMENTID

Note that your production and test environments are independent “databases” - any similarity with the system record IDs between those two environments is coincidental. In other words, opportunity 12345 in your production environment may (or may not) be the same opportunity 12345 in your test environment. So our recommendation would be to include the environment ID when building the link to remove any ambiguity (and also to ensure the user lands on the actual record you intend them to land on).

Hope this helps!

Bob Rickards

I now have both of those working…so next question….how do you get to Actions? I assumed the same way…but I was wrong. Any thoughts?

Ben Lambert

Bob,

The "list of actions for a constituent" page is located at:
https://host.nxt.blackbaud.com/constituent-actions/lists/CONSTITUENTID?svcid=renxt&envid=ENVIRONMENTID

The “specific action record” page is located at:
https://host.nxt.blackbaud.com/constituent-actions/records/ACTIONID?svcid=renxt&envid=ENVIRONMENTID