Is there an official Retirement Date for PMM yet? After it retires will the related objects and automations no longer work in our Org?
We are creating a 3-5 yr roadmap and evaluating changes that we need to be ready for. We are evaluating the need to migrate to Non Profit Cloud, and what happens to PMM will have a lot of influence on this.
I need to uninstall PMM from our org, put it appears that the admin who installed it did so via MetaDeploy? The app is not showing up under Installed Packages
Unfortunately the only installed packages are default or unrelated, I will reach out to support, thank you!
Hello! I'm tracking down info on the Last Service Date field. It's a roll up that's recalculated nightly with an Apex Job. There is a Last Service Date field on Contact, Program Engagement, Service and Service Session.
Our Last Service Dates are totally inconsistent. Sometimes the Program Engagement field will be correct, but missing on Contact. Sometimes missing on both.
I've gone through the steps on this Help Doc. (Except the fields aren't on a Page Layout). I've ensured the Scheduled Apex Job and the Feature Gate settings are correct.
I saw one post where someone thought it was tied to an Attendance Status = Present, but that doesn't seem to be the case, testing on two records.
What might be reasons for the the inconsistencies? Thanks!
I'm a few years late to this conversation, but this post kept coming up as I was trying to troubleshoot a very similar problem. I had a number of Program Enrollments that had Service Deliveries but no 'Last Service Date' even though most of the Program Enrollments in the org had a 'Last Service Date'. It turns out that you need to have a Quantity value entered on the Service Delivery for the 'Last Service Date' to calculate. Hope this answer helps someone else searching the same issue!
Allow Lookup Filter to be Disabled:
I understand the rationale behind the lookup filter on the Program Engagement field on Service Delivery - ensuring that both fields reference the same client. But this means that the user always has the extra step of selecting both. Being able to disable this would allow process automation to populate the Contact field.
Hi PMM Group,
We ran a summer camp and tracked attendance in PMM and unfortunately the staff who entered the data added the camper's names to the Program Engagement field that looks up to the parent's Contact record which generates this error code: Script-thrown exception: System. DmlException: Insert failed. First exception on row 0; first error: FIELD_FILTER _VALIDATION _EXCEPTION, Contact must match the Contact in the Program Engagement.: pmamProgramtngagement_c
At first I deactivated the Validation rules on Program Engagement and Service Delivery, which generated the error still. I found the Related Lookup Filter for Program Engagement to Service Delivery, but I am unable to edit it.
I started to create a permission set to bypass the PMM Validation rules, but learned I can't edit the Validation rules to allow the permission set into the formula.
Im hoping we don't have to reimport all the data because it is over 300 campers, but I am mentally preparing to scrap what they have done and data import to start over.
Any ideas on a workaround? Thank you !
I came up against this Validation Rule on Program Engagement as well. I don't suppose you figured out a workaround?
Hi,
I am new here and I've done the relevant modules for this app. Looking at the Service/Service Delivery objects specifically, I am wondering if service delivered is of currency type, I see no field about price. Which table in PMM Salesforce contains the cost of the service? or does it have to be custom created?
Thank you,
Ismaeel
In PMM there’s no out‑of‑the‑box “cost” field on Service or Service Delivery, it’s more about tracking what was delivered and to whom. If you need to store pricing or delivery cost, you’ll have to add a custom currency field or link it to another object (like Opportunity or a custom Cost record).
Hi. We are using PMM to track therapy-related service deliveries on cases. We won't be using the client field. I need a formula that removes anonymous from the naming convention. This is the default formula: IF(NOT(ISBLANK([pmdm__ServiceDelivery__c].pmdm__Contact__c)),IF(LEN([pmdm__ServiceDelivery__c].pmdm__Contact__c.FirstName + ' ' + [pmdm__ServiceDelivery__c].pmdm__Contact__c.LastName + ' ' + IF (NOT(ISBLANK([pmdm__ServiceDelivery__c].pmdm__DeliveryDate__c)), TEXT([pmdm__ServiceDelivery__c].pmdm__DeliveryDate__c) , LEFT(TEXT([pmdm__ServiceDelivery__c].CreatedDate),10 ))+ ': ' + [pmdm__ServiceDelivery__c].pmdm__Service__c.Name) > 77, LEFT([pmdm__ServiceDelivery__c].pmdm__Contact__c.FirstName + ' ' + [pmdm__ServiceDelivery__c].pmdm__Contact__c.LastName + ' ' + IF (NOT(ISBLANK([pmdm__ServiceDelivery__c].pmdm__DeliveryDate__c)), TEXT([pmdm__ServiceDelivery__c].pmdm__DeliveryDate__c) , LEFT(TEXT([pmdm__ServiceDelivery__c].CreatedDate),10 ))+ ': ' + [pmdm__ServiceDelivery__c].pmdm__Service__c.Name, 77) + '...', [pmdm__ServiceDelivery__c].pmdm__Contact__c.FirstName + ' ' + [pmdm__ServiceDelivery__c].pmdm__Contact__c.LastName + ' ' + IF (NOT(ISBLANK([pmdm__ServiceDelivery__c].pmdm__DeliveryDate__c)), TEXT([pmdm__ServiceDelivery__c].pmdm__DeliveryDate__c) , LEFT(TEXT([pmdm__ServiceDelivery__c].CreatedDate),10 ))+ ': ' + [pmdm__ServiceDelivery__c].pmdm__Service__c.Name) , IF(LEN($Label.pmdm__Anonymous + ' ' + IF (NOT(ISBLANK([pmdm__ServiceDelivery__c].pmdm__DeliveryDate__c)), TEXT([pmdm__ServiceDelivery__c].pmdm__DeliveryDate__c) , LEFT(TEXT([pmdm__ServiceDelivery__c].CreatedDate),10 ))+ ': ' + [pmdm__ServiceDelivery__c].pmdm__Service__c.Name) > 77, LEFT($Label.pmdm__Anonymous + ' ' + IF (NOT(ISBLANK([pmdm__ServiceDelivery__c].pmdm__DeliveryDate__c)), TEXT([pmdm__ServiceDelivery__c].pmdm__DeliveryDate__c) , LEFT(TEXT([pmdm__ServiceDelivery__c].CreatedDate),10 ))+ ': ' + [pmdm__ServiceDelivery__c].pmdm__Service__c.Name, 77) + '...', $Label.pmdm__Anonymous + ' ' + IF (NOT(ISBLANK([pmdm__ServiceDelivery__c].pmdm__DeliveryDate__c)), TEXT([pmdm__ServiceDelivery__c].pmdm__DeliveryDate__c) , LEFT(TEXT([pmdm__ServiceDelivery__c].CreatedDate),10 ))+ ': ' + [pmdm__ServiceDelivery__c].pmdm__Service__c.Name))
I'm trying to figure out if there is a way to view and pull numbers of the demographic composition within the household. Our main priority is to get the number of adults, children, number of children under the age of five, number of members that identify by what race, and whether they were served within the fiscal quarter on the household record. Has anyone done this before? Would flow be the way to go? Any advice? We are using NPSP and Program Management Module @Salesforce.org System Administrators @Nonprofit Success Pack @Program Management Module (PMM)
Not related to how you get the roll up, just a piece of advice on the time dependency feature of counting adults and children. I would encourage you to store the estimated birth year rather than H. That doesn’t mean you can’t make it easy on your users. They can enter eight and you can internally convert that to the estimate estimated Year they were born. Or perhaps you actually just collect birthdates. The rollup should be based on how many people were born before certain dates and after certain dates and not on age age changes every year and birthdate doesn’t.
--Terry
When creating a service schedule we are receiving a component error (image attached). We have been working with our consulting team and they can't seem to make heads or tails of it either.
This issue started occurring after our org was updated to Winter '24, prior to that it was working without issue.
We have come across an existing KB article but the work around doesn't resolve the issue (tried on multiple browsers, clearing cache, incognito mode after making suggested change)
Anyone else running into this and the above work around isn't working? Our consulting partner is looking at opening a case with Salesforce, but figured maybe someone in the community has run into and resolved it.
Thanks in advance!
Still having this issue in November 2025, and with a brand new PMM install --- any updates on a fix??
HI
We are implementing PMM to track additional therapy service deliveries on cases. My users will create the service delivery on the case record. I need the description of the service deliveries available prior to creating a new service delivery to ensure they select the correct service. I'm not sure of the best approach; do you have any suggestions for me? I'm currently considering a flow that includes a screen element, but I'd like to know if I am missing an easier solution.
Hi Stacy,
If you're looking to see the Description of the Service from the Service lookup field on Service Deliveries, one option is:
1. On the Service object, go to Search Layouts
2. Edit the Default Layout and add Description as the 2nd selected field after Service Name
When the user clicks in the lookup and starts typing, the search results will include the Service Name and the Description.
