Forum Discussion
2 versions of Volunteer Management...
I discovered the hard way that there are two versions of Volunteer Management out there. They look very similar, but the way they denote Volunteers in Contacts is different: in one, the picklist column (field) Primary Constituent Type [msnfp_PrimaryConstituentType] is set to 'Volunteer'; in the other, the Y/N column Volunteer [msnfp_volunteer] is set to 'Y'. Both columns exist in the nfp version of Contacts. Forms and Views set up for one approach obviously won't work for the other.
The version of Volunteer Management that is currently (11/24) installed by Cloud Solution Manager uses the 'Y/N' method. The other is (I suspect) what got installed earlier in '24 when I first installed NonProfit Accelerator and asked to include the sample apps. Both showed up in my list of apps, including in mobile.
My initial reaction: D'oh! Doesn't a Unified Constituent approach suggest that the method should be the same across all apps, and not a one-off in this app? I can see advantages to both...but...
My rec: if you combine the latest VolMgmt with any other Dynamics/Dataverse-based app, either write a flow that also sets the Constituent type, or pay close attention to your filters when you view or report around your Contacts.
Sigh.
ps: if I'm right about the sample app, has it been updated more recently for consistency? thx
MattBurr, it looks like the Volunteer Management app is version 1.2.3.0, which uses the "equals Yes" approach, while the Volunteer app that was downloaded as part of the Nonprofit Hub sample apps is signed 3.1.3.0.
I created a clean developer environment, installed from Cloud Solution Manager but did not ask for CDM for Nonprofits Sample Apps or test data, but only the Volunteer Management solution, and that environment has ONLY the 1.2.3.0 version. My other environments have the 3.1.3.0 version, date-stamped 9 months ago. thx
Nicole_Bechard- wondering if you have any guidance on this topic? Is there a reason for two 'volunteer' identifiers?
