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

Error when posting gift custom fields

Charles Boshell

When posting gifts assigned to a batch through SkyAPI, the gift posts properly and the Id is returned. However, when posting a custom field to the previously posted gift, I receive a 404 error stating, “Returned when the specified opportunity is not found.” Researching the gift in RENXT, I see the gift with a status of “Pending approval”. Is that what is preventing the custom field to be posted, and if so, is there a work around? Any help would be greatly appreciated.

Find more posts tagged with

Comments

Kevin Hathorn

Those gifts sitting the batch and waiting on approval should not prevent custom fields from posting, we do the same and have no trouble with them posting. Do the custom fields you are posting exist in your RE setup (ie: “custom field category”)? Those have to be created in RE before you post them and the category name you post must match the category name in RE (case sensitive)

Charles Boshell

Kevin, thanks for the reply. Yes, those custom fields exist and we are matching the category name. We have implemented this pattern in other locations, except non-batched gifts, which led me to ask about it.

Kevin Hathorn

Gotcha. Is this happening in production, or dev account “sandbox”?

Charles Boshell

Sandbox

Kevin Hathorn

ah, that's the problem. Sandbox does not return valid gift ids, which will cause dependent subsequent calls to fail. I addressed this a few weeks ago in a post, no responses.

https://community.blackbaud.com/forums/viewtopic/494/56291

Kevin Hathorn

the only way I could successfully test it was by doing a one-off api call after getting the valid gift id from the webview ?

Kevin Hathorn

That said, I may have had to approve the batch first to get that valid ID as I recall, so there may be more than one issue here. But the docs say that the batch gift api returns the “gift_id”, so I wouldn't understand why it would be anything but the valid gift_id that could be used for additional calls.

Charles Boshell

Kevin, thanks for all the information. I think I finally realized that using this process is creating gift records that are not quite accessible (the batch gift post returns the system record ID, not gift ID) until the batch is approved, therefore you can't post additional attached records (like custom fields) until the batch is approved. Now I am running into an issue where I can see the posted batch in Web View, but not Database View, which doesn't make a lot of sense since that is where the records are contained.