Fundraiser Assignment Missing Important Columns on Return

To Preface:
I know that there are two ways to pull down fundraiser assignments down, either form the constituent to see who is assigned to them or from the fundraiser to see who they are assigned to. I know that “required” is false, but the data I want is present on the assignments for both web view and database view.

My Issue:
I tested with both, and I have come to the conclusion that neither can return the “end” parameter. Or many other expected parameters either.

36ffe95a6fd92d5e3f7b2f2b8f8419d0-huge-im
API projected output

No matter which API endpoint I choose - even though both are supposed to return those columns - I can only get six columns: id, amount, constituent_id, fundraiser_id, start, type. I have checked both RE NXT and RE database view to see that all information I am wanting should be present (e.g., end, fund_id, appeal_id) but I get nothing but those six aforementioned columns from the API.

Questions:

  • Is this a known issue? (I saw some posts showing only the truncated fields in results, but I want to know I am not crazy)
  • Is this only happening for me? (again, saw a few posts but it went unacknowledged)
    • If it is, how do I fix this?
    • If not, is a fix planned to release, or should this be reported as a bug instead of just a discussion post?

Comments

  • Alex Wong
    Alex Wong Community All-Star
    Ninth Anniversary Kudos 5 Facilitator 3 Raiser's Edge NXT Fall 2025 Product Update Briefing Badge

    @Wyatt Mosteller
    your screenshot looks like this endpoint:

    https://developer.sky.blackbaud.com/api#api=56b76470069a0509c8f1c5b3&operation=ListConstituentFundraiserAssignmentsSingleConstituent

    4b3ed84a8316730a6816443629f6a49e-huge-im

    so using that endpoint I am able to get “end” property. but you can see that JSON returned does not show the property if the property is blank.

  • @Alex Wong

    Attached are screenshots from multiple steps in my journey for this. First is the raw JSON output for this specific constituent system record id. Second is the Pandas DataFrame having the JSON normalized (hence the amount.value showing up). Finally, the last photo is the RE database view of the constituent record having assigned fundraisers with to and from, but it was not present in the DataFrame.

    c40d9b559b9d5a180e7438e32fde5b26-huge-im
    using Find tool on raw JSON (no ends)
    f56674575516abde3890292cae55e89b-huge-im
    Python Pandas DataFrame created from raw JSON output
    77a57f46a3c37e919cfe3a34588143bd-huge-im
    Database View of record

    After diving deeper to grab screenshots for this, you can see that I only showed the assignment with id of 46944 from the JSON because the assignment with an end didn't show up in the request response. All of the assignments with an end didn't show up. It seems you can only pull active assignments with no option to include inactive like normally possible. Regardless though… why?

    Edit: changed “report” to “record” in third caption.

  • Alex Wong
    Alex Wong Community All-Star
    Ninth Anniversary Kudos 5 Facilitator 3 Raiser's Edge NXT Fall 2025 Product Update Briefing Badge

    @Wyatt Mosteller
    https://developer.sky.blackbaud.com/api#api=56b76470069a0509c8f1c5b3&operation=ListConstituentFundraiserAssignmentsSingleConstituent

    this API endpoint does have a include_inactive paramter that can be specified. When not specified, it is default to false (would have been better if they told you inactive is excluded by default, but that is generally the case). So explicitly setting the include_inactive=true will give you those that are inactive (inactive are those that has start/end date range outside of current).

    f2b1038a9eddeb8eb88bba120b5820a9-huge-im
  • @Alex Wong So there is. That is another difference between thew two similar but different calls then. I was looking from the fundraisers side (so I could get more data in less calls), and that one only has limit and offset. I just assumed the constituent perspective would've been the same.

    Thank you.