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

Constituent Lists using the List_id parameter - offset and duplicate id issues

Warren Sherliker

Ben Lambert‍

Has anyone noticed a few bugs on constituent list endpoint when you use the list_id parameter and the list has quite a few records?

- You have to specify the offset=0 on the first call otherwise the next_link is wrong (i.e. misses the offset so you just get the first set of results again...)

- You get duplicate for large lists. If you have for example 65000 records and use the next_link to iterate through them we are finding you get roughly 20000 duplicate ids back so not the full list..

Is this to do with the lack of a sort token? Is anyone not having these issues?

Find more posts tagged with

Comments

Ben Wong

Hey Warren Sherliker‍,

I haven't heard about this being an issue. If you suspect there is a bug, then the best path would be to contact Blackbaud Support so that they create a formal case, get it to the right team, and keep you updated. They have systems in place to track the progress.

We recently published this guide to show what the support options are:
https://developer.blackbaud.com/skyapi/support/options

We can continue the conversation in our email thread if you run into problems with Support.

Thanks!

Ben

Reed Wade

I haven't seen the need to set offset to zero.

I have seen (like a page full of) duplicate records in a response when paging through full sets. It's not common and I haven't looked closer at the issue -- I just expect that to happen and ignore the duplicates.