Constituent Code Behaviors

Dan Bonville

I submitted this as a support request as it feels like a bug to me, but I was directed here (which, to be honest, I kind of resent).

In brief, when querying the constituent list endpoint, and filtering by constituent code, it appears that users will be returned even when their inclusion in that constituent code is expired. That seems to not be an intuitive thing and feels like a bug to me since that endpoint specifically is supposed to exclude “inactive” users by default.

This is documented more thoroughly in the open case 018424953, if a Blackbaud staff member happens to see this post.

Anthony Gallo

Hey Dan,

The support folks did file a bug for this and we have it on the engineering side now. We will look at the bug and respond back thru support to you. I agree that sending you to the community should not have been needed here.

Dan Bonville

Thanks @Anthony Gallo I appreciate the follow up. I'll keep my eyes on my support case for further updates.

Dan Bonville

Hi Anthony,

Thanks for getting back to me. Ultimately, it was deemed that this is not a bug, but expected behavior and the documentation of the endpoint was updated to reflect this.

I think I found a workaround that will work for the client which involves creating a list in RE that filters for unexpired users with that constituent code. We can then use that list as the target for our feed into Finalsite…just thought I would mention in case someone can confirm/deny that that filtering is possible, or if someone needed a workaround.