Solicit Code Count in Database View Doesn't Match API Response Count

Ashley Sanchez

Hello,


When I am in Rasier's Edge Database View and run a query on Constituents to pull their Solicit Code descriptions, I can see a large list of constituents and their many codes. However, when I am in the Sky API Console and run the Constituent Solicit Code List (Single Constituent) along with a Constituent ID that has multiple solicit codes and no other parameters, I receive a response that shows a '0 count' even though my query in the database shows 3 records.


Has anyone else experienced this or provide assistance?


Thanks,

Ashley

Val Kuppuswamy

Hi Ashley,


I couldn't duplicate this issue in SKY API Console. I ran the Constituent Solicit Code List (Single Constituent) with no other query parameters for a constituent with 3 codes and got all of them in the response. Please contact Support if you are still having the issue.

Thanks!

Harry Bailey

Hello,

Yes we're seeing exactly this issue currently. The database view returns a different list of solicit codes for the same constituent than the API list endpoint.

We've been via support and they pointed us here. They also questioned our use of constituent_id vs System Record ID. Apparently they are different even though the API documentation specifically states that the two are the same. We'd love to know more about this.

Creating a constituent returns an (System Record) ID attribute. All endpoints related to a constituent reference constituent_id and these are surely the same thing. They are both the immutable ID of the constituent database record.

So with that in mind, when we view a constituent in database view we see one list of solicit codes, and when we request the list via the API endpoints (either of these):
Communication preference list (Single constituent)
Constituent solicit code list (Single constituent)

The only difference between the two above endpoints is the use of `start` and `end` or `start_date` or `end_date`

I can confirm that adding / removing solicit codes from constituents also doesn't make that change to the database view. We've tried with existing constituents with solicit codes and with new constituents without codes.

How can we provide further information to get this replicated, or diagnose the reason for the inconsistency?

Thanks