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

no_valid_address not returned in List

Victor Heijke

The description of the Constituent on

https://developer.blackbaud.com/skyapi/renxt/constituent/entities#Constituent_01 sys that no_valid_address is one of the returned fields.

If we use this on Constituent Get we do indeed get that value

(https://api.sky.blackbaud.com/constituent/v1/constituents/196813)

However, when we use the Constituent List (https://api.sky.blackbaud.com/constituent/v1/constituents) then no_valid_address is not returned.

The document states that the list just returns a constituent entity but apparently it returns a lesser complete version of the constituent.

This is a vital field for our cleaning services and was hoping this small Boolean can be built in soon.

Regards Victor

Find more posts tagged with

Comments

Anthony Gallo

@Victor Heijke we are aware of gaps in our endpoints when we are talking single vs list. We are in the process of updating our lists backend and it will allow for us to fill these types of gaps more quickly. We are currently working on Gift and Action, and we will hopefully have the constituent list done in Q2.

Victor Heijke

@Anthony Gallo
Is there any news on this? We are almost in Q3 now .

Anthony Gallo

@Victor Heijke I fell victim to setting estimates on the last part of a 4 part project before we began part 1. We are currently in EAP for Action lists which will ship this summer and Gift list will be coming up right behind that. We shifted some other work in before we start on Opportunity and Constituent lists so my release timeline for those are now fuzzy. We should be able to give a better estimate as to completion there during our next product update briefing this fall.