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

Primary Addressee / Primary Salutation

James Phillips

I've scoured the API documentation but can only find an endpoint for getting these important values on a constituent by constituent basis.

Am I missing something? Is there a way to include the fields in the GetConstituentList or GetConstituent endpoints?

If not it means a lot of extra API calls which is hard to manage with throttling an issue.

Find more posts tagged with

Comments

Anthony Gallo

Hi James,

The addressee and salutation data is calculated information and it is not stored in the database anywhere. For performance reasons we only provide this data on the single call. We would use our idea portal to see if the demand is there to make a change to this process before we would go down that road.

Anthony

Darrel Giesbrecht

Addressees and Saluations are technically calculated but I can adjust the calculation to anything desired, AND I can choose to disregard the calculations completely by making the field “Editable/Custom”. Is none of this available from NXT for use outside?

James Phillips

When accessing the API the only way you can get the primary addressee and salutation values are via this call, which is per constituent:

This approach is a nightmare for synchronisation.

We are having to pull a full list of constituents that have changed in any way, and for each one call this endpoint to get the values and see if they match the values previously stored in our system

James Phillips

Ok I'll add something to idea portal.

It seems strange to me though, the primary addressee and salutation are absolutely essential when communicating with a constituent, why is there no optimised way of accessing them in bulk via the API?

Jacob Dong

@Anthony Gallo
just following up the primary addressee and salutation API endpoint. They're important for us to conciliate the data quality coming across systems. So, it'll be helpful if there is a way to pull these data.

Anthony Gallo

We are doing a lot of backend plumbing work in our lists infrastructure to help with getting some of these much needed fields added later in the year.

James Phillips

@Jean Jackson ob d*** I created a ticket on idea portal some time ago:

Justin Beasley

@Anthony Gallo Did anything ever come of this?

I see some time has passed, but I don't see any ability to list Salutation or Addressee in bulk (same issue with things like Solicit Codes/Communication Preferences, Recurring Gift Schedules, and a host of others that are too request-prohibitive to pull for every constituent or gift)

Alex Wong

@Justin Beasley
You can get all of what you mention using Query API now.

Anthony Gallo

@Justin Beasley
We halted the lists project in favor of the expanded focus of getting items out of database view into web view. That pivot allowed us to bring query into the web. Although the query itself is not a replacement for lists, the query API would be the go forward solution like we had intended for the lists API. I agree with @Alex Wong and his suggestion here.

Justin Beasley

Thanks @Alex Wong and @Anthony Gallo — I didn't realize these were available via Query. I'll go this route for the time being. Appreciate it!