Skip to main content

Hi!  

While configuring the Funraising Intelligence, the last step, Install Fundraising Intelligence, fail in the middle. The app is not listed in the Apps after. 

Any tips? Salesforce support?  

 

Failed to create Semantic Model [NPC_Semantic_Model] from template [sfdc_internal__npc], error: [Failed to Create SDM [Invalid data object field: Creation of semantic entity NPC_Semantic_Model failed. caused by: The referenced Data Cloud fields ([ssot__LastStageChangeDate__c, ssot__LastActivityDate__c]) could not be found in the referenced DMO or CI (ssot__Opportunity__dlm). For DMOs, ensure that the referenced fields are properly mapped.]]
5 Antworten
  1. 10. Sept., 12:14

    Hi Deepak,

    Thank you for the information. I have already verified and completed the prerequisites you mentioned:

    • Data 360 is provisioned and enabled in the org. 
    • Fundraising Settings are enabled under Setup. 
    •  I have created the required Data Streams for the objects included in the Fundraising Bundle. 
    •  The Data Streams have been processed successfully, and I have also refreshed/processed the corresponding records. 
    • Tableau Next licenses are also provisioned in the org. 

    However, even after completing these configurations, I still cannot find “Fundraising Intelligence” anywhere in Setup / Quick Find.

    This is a Nonprofit Trail org on Enterprise Edition, so I’m wondering if there is another prerequisite that is not exposed through Setup—for example, a specific Nonprofit Cloud Fundraising license, feature entitlement, permission set/license, Tableau Next entitlement, or org-level provisioning that needs to be enabled by Salesforce.

    Could you please clarify whether Fundraising Intelligence is actually supported/provisioned in the Nonprofit Trail org (Enterprise Edition), or whether it requires a specific production/sandbox org type or additional Salesforce entitlement?

    If the feature should be available in this type of Trail org, is there any specific permission set, permission set license, package, feature toggle, or provisioning step that I should verify?

    I’d really appreciate any guidance on what I might be missing, as the standard prerequisites appear to be already configured in my org.

    Thank you!

0/9000