You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm happy to submit a PR for this, but in case anyone else wants to:
There is a requirement to use a custom Gender field for Relationships configuration, but Salesforce has a new standard GenderIdentity field that we'd prefer to use, as it's, well, standard.
Are there plans to update the package? Would a PR help? There are so many open PRs that I'm guessing nobody is responsible for this repo...
The text was updated successfully, but these errors were encountered:
Hi @dschach Hope you're doing well. :-) As you know, I'm an outside community member now, just like you.
The last time someone who worked for Salesforce responded on a Github issue was in December, and that person no longer works for Salesforce, so it's unlikely you'll hear back here. Salesforce is still responsible for NPSP/this repo, but also unlikely they'll take PRs. You might get better visibility opening an idea on the Idea Exchange.
My guess is that you'll have to continue to use the custom field, but can have its value reference the standard one in automation. I haven't tested yet, but I'm hopeful it works well with the new standard Salutation values.
Thanks @judisohn Yeah, that's the answer I was expecting, but not the one I was hoping for.
I'll set up all the flows for keeping gender and pronoun fields in sync. It's great that Salesforce made them standard; it just leaves some of us with extra things to manage and no documentation with a best-practice suggestion. Oh well.
I'm happy to submit a PR for this, but in case anyone else wants to:
There is a requirement to use a custom Gender field for Relationships configuration, but Salesforce has a new standard GenderIdentity field that we'd prefer to use, as it's, well, standard.
Are there plans to update the package? Would a PR help? There are so many open PRs that I'm guessing nobody is responsible for this repo...
The text was updated successfully, but these errors were encountered: