Fundraising

@Manjula Rajaram Our implementation partner cloned the OOB DPE and calculated the fields to use Fiscal Year instead of Calendar Year.  When it came time to generate end of year tax letters (United States), I needed Calendar Year calculations instead of FY.  Insted of undoing the partner's work, I made new fields and expanded the DPE to write CY data into fields I could use for total tax year giving.   Knowing what I know now, I would leave Salesforce's OOB for Calendar Year and make new fields on Donor Gift Summary for Fiscal Year, then reference Company Fiscal Year data points. 

Hey, 

Based on my understanding you are correct

The Actionable List does not refresh automatically. To update the dataset, you need to manually trigger it or set up a scheduled flow. 

Try this out (

Your individual fields array from the DataMapper are under the parent node "Products". For the fields to be available in FlexCard the resulting JSON must be a simple JSON array without child nodes. 

Essentially, your current JSON is this:

{
	Products:{
		ID:"1",
		Name:"Product1",
		Description:"Product1",
		UnitPrice:100
		},
		{
		ID:"2",
		Name:"Product2",
		Description:"Product2",
		UnitPrice:200
		}
	}
}

While it should be like this: 

{
	ID:"1",
	Name:"Product1",
	Description:"Product1",
	UnitPrice:100
	},
	{
	ID:"2",
	Name:"Product2",
	Description:"Product2",
	UnitPrice:200
	}
}

There are two fixes: 

1. Make sure the DataMapper output omits "Products:" prefix from all JSON output paths. OR 

2. On your Flex Card Data source setup select ["Products"] in Result JSON Path.

Hey Kim,  

Great question — this is something we think about a lot. 

Campaigns alone tend to hit a wall quickly: users without a full Salesforce license can't manage them, and campaign membership status ends up doing too much heavy lifting for something as layered as event engagement. 

What we've found works much better is a custom object model tied to a campaign — built around Events, Tickets & Options, Registrations, Sessions, and Check-ins. Each object handles its own slice of the engagement story, so you can see exactly where someone is in the lifecycle without trying to force it all through campaign membership. 

We actually built Bless Events (

) around this exact data model — designed specifically for nonprofits and faith-based organizations, with native Salesforce integration and giving built in so registrations and donations are all connected in one place. 

Happy to walk you through how it works if you're curious —