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; } } }

Another SP26 Issue

Kelli Crispin

We have found during testing that the Relation Only constituency displays on ALL records at the top of the constituent page.

We have submitted a support ticket, but have not heard when this will be fixed.

To avoid confusion for our users, we are inactivating the Relation Only constituency, so it does not display on any records or in the Constituencies query node. It continues to display on the Personal/Org Info tab > Constituencies subtab. We also populate it in our data warehouse, so users can query it there.

Find more posts tagged with

Comments

Rick Root

Adding to this.... making the constituency inactive causes it to NOT get put into the CONSTITUENCYDATERANGE table - however we don't rely on that for our data warehouse custom table that we store "primary constituency" in so we are still able to do queries including or excluding relation only records based on that.

Stephanie Boyce

This seems like a pretty big oopsie for them to miss! Let's hope they come out with a hot fix soon!

Rick Root

Stephanie Boyce:

This seems like a pretty big oopsie for them to miss! Let's hope they come out with a hot fix soon!

I've just been informed by Blackbaud support that this won't be fixed until SP28!!!

Erika Layfield

I just received the following response from support on this issue: "We have a fix for this issue coming soon, and it is currently in QA. I will reach out with an update as soon as I have further details from our Development Team on if this will be able to be hotfixed for SP26 or if it will require a higher version."