Skip to main content
All CollectionsCompare and deploy metadataGuides on comparing and deploying specific metadata
How to deploy Fundraising standard objects, such as "GiftTransaction" and "GiftCommitment"
How to deploy Fundraising standard objects, such as "GiftTransaction" and "GiftCommitment"

Guidance on retrieval of Fundraising Standard Objects (via Custom object metadata), which are a part of Salesforce Nonprofit Cloud

Mateusz Kochanowicz avatar
Written by Mateusz Kochanowicz
Updated over a week ago

If you're using Salesforce Nonprofit Cloud, and you're looking to retrieve either GiftTransaction or GiftCommitment objects and their sub-components - you can do it in Gearset.

As per our documentation, Nonprofit Cloud is one of the Clouds our app supports.

Important to note: Both GitfCommitment and GiftTransaction objects have special access rules in Salesforce - they're only available for retrieval if the Fundraising Access license is enabled, and the Fundraising User system permission is assigned to users.

Permissions should be assigned both in the source and target org if you're comparing two Salesforce orgs.


What metadata type to select in the filter?

If you have the correct license and permissions, to retrieve these objects you'd need to do the following:


1. Add Custom object to your metadata filter (or you can use our Basic comparison default filter which already includes Custom object).
2. Set the API version to be 59 or higher (these objects are not available in API versions lower than v59).

Note: As long as you're using a source & target with API version 59 or higher, you can select Default (highest common version)
3. You may need to select "All" under Include managed packages if the objects you're looking for are a part of a managed package (if you select "All" make sure that Installed package type is excluded from your metadata filter).

This guidance also applies to other Salesforce Fundraising Standard Objects, some of which are supported only in API version 60 and above - such as GiftCmtChangeAttrLog and PaymentInstrument.

How do these objects look in the comparison results?

Once objects are retrieved, they'd look as below in your comparison results:

Did this answer your question?