Issue: Gifts Connector – Add gift to batch bypasses required field validation

Lee Grisham

Has anyone else seen this with the Gifts connector → Add gift to batch action?

We’re consistently able to reproduce a scenario where a gift is added to a batch even when required, system‑validated fields are invalid—for example:

• Constituent System ID
• Fund ID
• Potentially any required field that must already exist in the system

What happens

In Power Automate or any external connector:

1. Use Add gift to batch
2. Populate all required fields
3. Provide a value that does not exist (e.g., invalid Constituent System ID or Fund ID)

Result:

• The action returns an error (we’re seeing 50001 and 25004)
• BUT the gift is still created in the batch
• In the case of Constituent, the gift is added without a constituent attached

Previously, an error like this would prevent the gift from being created at all. Now, the connector appears to both error and write data, which makes flow error handling and retry logic very difficult and creates data integrity issues. While this is something that can be addressed in batch, it causes issues in PaperSave as the file doesn't get attached to the gift with the exception. It seemed to spike when the Grid View came online.

Are others seeing this with other required lookup fields?

We can reliably reproduce this and have raised it with Support, but wanted to check whether this is more widespread.

~Written with help from AI.

Alex Wong

my automation so far does not create gift in gift batch, but working on another automation that does for a client. Tagging the post, as I would like to know what to expect too.

Erik Leaver

@Lee Grisham Can you confirm the case number (I think it's 020747380).

Can you replicate the issue with the Try It console? Trying to determine if the problem is with the API or the Connector. I don't think you mentioned you were using the Connector in the case. Point of failure could be in the API, the connector, or potentially both.

Lee Grisham

@Erik Leaver yes, that is the case.

Not sure how to approach the Try It console to test it. Would need some help from that end.

I'm a PaperSave customer, which I think uses the API and verified this behavior in Power Automate using the Gifts connector. Both seem to be performing the same way.

Erik Leaver

@Lee Grisham I can't speak to PaperSave but if you have a process that is using the Gifts connector, you can use the SKY Developer "Try It" console and call the APIs to see if the response you get from the API is the same as the Connector. To use the Try It console, follow these directions: https://developer.blackbaud.com/skyapi/docs/getting-started/learn-api