#Answers6 人正在讨论

For DAF gifts the cleanest model is hard credit to the DAF, soft credit to the individuals — and that also matches the legal picture: the donor's tax-deductible gift happened when they funded the DAF, so the grant to you legally comes from the sponsoring organization. 

On your two questions: 

1) Hard credit isn't multi-contact. In NPSP a gift's hard credit is tied to the Opportunity's Account (and its primary contact) — effectively one payer. So set the Opportunity's Account to the DAF sponsor (e.g., Fidelity Charitable), which hard-credits the DAF, and give each individual a Soft Credit. Hard-crediting the individuals would overstate their deductible giving and muddy audit reconciliation. 

2) Yes — add each individual as an Opportunity Contact Role with a soft-credit role, and NPSP creates a Partial Soft Credit for each. The soft-credit rollups then reflect the gift on every donor's record, so their giving history stays accurate without double-counting the hard credit. Which Contact Role values count as soft credit is configurable in NPSP Settings (Donations, Contact Roles). 

Tip: add an Affiliation between each advisor Contact and the DAF Account (role e.g. DAF Donor) so the relationship shows on both sides. 

if this helps, please mark it as the Best Answer so it helps the next person — thanks 🙂

Good - since it is CPQ, that actually settles the design. Keep the Commercial (operating) account as the transactional account CPQ points its Quotes, Contracts and Orders to, and use the Legal Entity as a bill-to / contract-party lookup rather than moving the transactions onto it. 

The reason: CPQ hangs Contracts, Subscriptions and Assets off the account, and renewals, amendments and asset combination ('Combine Asset Quantities' is an Account field) all key off that same account. So for existing customers, if you migrate them onto a new Legal Entity account you risk breaking the renewal and contracted-price lineage. Safest pattern: apply the two record types from day one for net-new, and for existing accounts keep CPQ pointed at the Commercial account and just add the Legal Entity link. 

If this helps, please mark it as the Best Answer - thanks :)

@Sourav P

Yes. The answer is: 

In Salesforce, Custom Metadata records are maintained under: 

Setup → Custom Metadata Types → [Your Custom Metadata Type] → Manage Records 

There are two different things: 

• Custom Metadata Type → Defines the structure/fields. 
• Custom Metadata Record → Stores the actual values. 

If you can see the field name but not the actual value, click Edit on the specific metadata record. The values should be displayed there. 

For example: 

Custom Metadata Type: Application Settings 

 → Manage Records 

 → Default Settings 

 → Edit 

 → Update the field values. 

If the value is still not visible or editable, it may be coming from another source, such as: 

•  A Custom Label
• Custom Setting
• Custom Metadata referenced by Apex/Flow
•  A Formula
•  A Named Credential
•  A value hard-coded in Apex/LWC 

You can also check the Apex/Flow code that references the metadata to identify exactly where the value is being used. 

Hi Oraz,

If you're comfortable with joins, you may want to prepare a Logical Table as follows:

1) UNION the questions and comments tables (right in Tableau)

2) 'ALIGN' the 'same entity' columns using the Tableau-generated [Table Name] as the anchor:

// aligned_question_id
CASE [Table Name]
WHEN 'questions' THEN [id]
WHEN 'comments'  THEN [question_id]
END

// aligned_user_id
CASE [Table Name]
WHEN 'questions' THEN [answered_user_id]
WHEN 'comments'  THEN [user_id]
END

// aligned_date
[date]

3) JOIN the users table with the Unioned one by the [aligned_user_id] Join Calculation on the left

Step 3 has to be prepend the step 2, I just show the calcs first to explain the Join to be made.

Yours,

Yuri

Hi @Chris Uttley,

You can do that by upgrading your highlight panel on Lightning record page to Dynamic and then set conditional visibility on the button based on the permission set.

Check the attached screenshots.

Please mark as the best answer if this resolves your issue.

Thanks,

Milos

Unfortunately, something like this would have to be introduced at a platform level to apply to all / any component. Otherwise it would have to be done at a component level (to take in a custom CSS Class name as a property input and apply it to the parent wrapper of the component). So it's unlikely that there's anything on the appexchange that would address this.

Maybe create an idea to extend similar functionality from LWR to Aura?

FYI @Alicia Teo

Yes, could use Email Service or if you are using Email-To-Case, you can do it in Trigger.

One Visual Solution could be use Custom Notification for Visual effect:

https://help.salesforce.com/s/articleView?id=sf.notif_builder_custom.htm&type=5

Additionaly, the check in the Case could be used, if you want this solution, but should work with List View and Filter for the Checkbox field. That way your agents could review this cases with incoming emails received.

Thanks a lot,

Regards