Our reciprocal relationships are not auto creating on Spouse. Where should I look to troubleshoot? Is there an apex class that manages this that might have been turned off? Here are my settings.
Update, I have checked and REL_Relationships_Con_TDTM apex is enabled.
Resolved, one of the other apex classes was disabled, go to trigger handlers and make sure all REL apex classes are enabled.
I'm trying to create a flow that will automatically add a start date when a relationship is created. It's not working, and I can't tell why. Any help would be appreciated:
Thanks! I'm new to working with flows so the Created Date issue hadn't occurred to me. I've tested what you did in the video and it seems to be working - will let you know if I have any questions.
I have a collection variable of Relationship records I am looping through to and assigning the Related Contact field to a variable. My objective is to then use the collection variable to pull the contact records. The problem is that when I try to assign the recent item in the loop (Relationship record), I can't get to the related contact Id field. I am only allowed to transverse down the chain without ability to actually pick an Id field. I'm not sure if I am doing this right or if the Relationship -> Related Contact lookup field is handled differently. Any suggestions?
Hi, I'm on the latest version of NPSP in my org. However, I have two Apex Classes that were created that are on API versions 26.0 and 28.0. I can't delete or edit these. How do I update them? #Admin Trailblazers #NPSP Relationships
"Deleting an app won't have any impact on Object, Field and Record as those are totally different entities. Your one object might be related to some other app and so on."
I got this answer ,but i am not satisfied .
if u get answer then u will tell me,
i am waiting for help .
I am testing out relationship autocreation in a Sandbox. I have a custom field on a contact called "Parent/Guardian" and an automatic relationship triggered from the field with type "Parent". I have the Parent and Child values both in the type on the relationship object and the reciprocal settings are set up. However, when I enter a contact lookup in the "Parent/Guardian" field, 3 relationship records are created: 1 on the child record and TWO for the parent. The 2 parent relationship records are both associated with the single child relationship record. This was also causing an issue with trying to delete duplicate records -- I had to go into the fields and delete out the reciprocal record ID on the duplicate parent relationship before I could delete the record.
The only thing I can think that might be related is that the org doesn't have a gender field. But I don't know how that would result in duplicate records (the reciprocal gender nuetral values are being correctly assigned.) Any thoughts? Is this a sandbox issue or a real problem? #NPSP Relationships
Oy. For those interested: check your triggers! I had duplicates of all my trigger handlers from a sandbox seeding job.
I am running into this issue in a Sandbox now, but I am not sure how to confirm it's just an environment issue: https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000IREGESA5
Has anyone else noticed this...? I added a relationship between two contact records and the relationship "type" changes on the connected record to a more general term. For example: between husband and wife relationship of Mr. John and Mrs. Jane Smith.
1) When entering the relationship from John Smith's contact record, I selected that Jane Smith is his Wife.
2) When I looked at Jane Smith's contact record, the relationship indicated that John Smith was Jane Smith's "spouse". I updated the relationship type from spouse to husband.
3) But, then on John Smith's contact record, the "wife" relationship type updated to "spouse". This happened a couple of more times; by updating the relationship type with "husband" or "wife" the connected relationship type would auto-update as "spouse".
Has anyone else experienced this? and is there a way to fix this?
Thank
@Tara Wenzel here is the overview from documentation for how relationship settings work and can be changed. https://powerofus.force.com/s/article/NPSP-Manage-Relationships-Settings
There's also a helpful Trailhead unit: https://trailhead.salesforce.com/en/content/learn/modules/contact-and-account-settings-in-nonprofit-success-pack/create-custom-relationships-npsp
Hi,
We have campers (contacts) who need to be connected to their divorced parents.
What do people normally do?
Is each parent a separate household account? If so, how is the camper, whose contact record is a part of one of the accounts, connected to the other parent's account?
Or, are the parents put into one household account and the marital status of the contacts is noted and the two parental contacts have distinct address and contact information?
Thanks for your insights,
Yaakov
@Yaakov Singer We have a similar situation. Our campers get pushed into Salesforce from our camper registration platform through an API. The other platform is camper-centric and Salesforce is Household-centric. We try to keep the camper contacts with the "primary" parent who is typically the one who registers them for camp. And then we use the relationship object to connect them. But it very confusing. And, bc of the API, often these families/ex-spouses are pushed together into 1 Account in Salesforce or the camper is pushed into the wrong parental account. If you come up with any better solution, please share! 🙂
Hi there! I am wondering if it possible to have two record types that act as households? Or if anyone has an idea on the best way to handle the following case:
We want to have US households and international households. Each user should only be able to see one or the other type of household (along with their contacts and opportunities) with the exception of system administers, who should see both. It would be great if I could create 2 household record types that both function as household (adding multiple contacts and having it update the name, ect).
Any thoughts or ideas are greatly appreciated!
@Emily Schwichtenberg , we use a custom field to segregate US records from International records, this custom field exists across all objects. Users have also this custom field with their respective value that pass on all records they create and child records as well. This was all put together by our implementation partner but I'll be happy to explain more why/how we use it in case you think it might be a solution for you.
Maida
