MCAE: Open Prospect user interface with Prospect ID

If you have the Prospect ID, you can open the Prospect detail with the following URL with parameters:

With the Pardot user interface:
https://pi.pardot.com/prospect/read/id/179597888
https://pi.pardot.com/prospect/read?id=179597888

With the Account Engagement user interface:

https://mydomain.lightning.force.com/lightning/page/pardot/prospect?pardot__path=%2Fprospect%2Fread%2Fid%2F179597888

B2B Marketing Analytics app: sfdc_internal__B2BMA

B2B Marketing Analytics, a CRM Analytics app within Salesforce designed to analyze marketing and sales data. It leverages datasets from Account Engagement (formerly Pardot) and Salesforce to provide insights into campaign performance, prospect behavior, and overall marketing effectiveness. 

You can create the B2B Marketing Analytics app from Analytics Studio, select B2B Marketing Analytics, and follow the wizard.

You need to enter your Pardot Account ID, then select optional features, such as Account-Based Marketing, Multi-Touch Attribution, Prospect and Activity dataset, etc. If you stopped with the following error:

Unable to create app based on template: [sfdc_internal__B2BMA].

* Your org does not currently meet minimum data requirements to proceed. Please fix the following issues before creating a 'B2B Marketing Analytics' Application:

In the 'sfdcDigest_Contact_CWA' node, the 'pi__grade__c' field doesn't exist, is deprecated, or isn't accessible to the Integration User. In the 'sfdcDigest_Contact_CWA' node, the 'pi__score__c' field doesn't exist, is deprecated, or isn't accessible to the Integration User.

You need to adjust the fields in both Lead and Contact, the Account Engagement Score (pi__score__c) and the Account Engagement Grade (pi__grade__c) fields, to make them visible (as read-only is sufficient) to the Analytics Cloud Integration User profile. 

From the object manager, open each field and update the field-level security settings to grant visibility to the Analytics Cloud Integration User profile. 

Re-create the B2B Marketing Analytics app from Analytics Studio, and you should be able to pass the error.

Once the app is created, it can also be seen in the "Auto-Installed Apps" in the setup menu.

Salesforce Field history tracking on Record creation

In Salesforce, field history tracking can be setup for both standard and custom fields. 

On Record Creation
No, field history tracking does not log the initial values when a record is created.

On Record Update

Yes, it tracks changes to the specified fields when they are updated. It logs the old value, new value, user who made the change, and timestamp.

As noted in the last screenshot, the Mailing Country should ideally be auto-updated (from Flow, Trigger, etc.) after the record is created; however, the order can be misleading, as they have the same timestamp. If we use SOQL, will we see the difference? No, they may have the same exact milliseconds

Reference:

• Field History Tracking on Record Creation

Salesforce: Sales Territories (I)

Sales Territory

As per the Summer '24 release, Enterprise Territory Management is now called Sales Territories. 

Out-of-the-box sharing mechanism to share record access to users based on the territory setup:

• Account (View OR View and edit OR View, edit, transfer, and delete) 
• Contact (No access OR View all OR View and edit all contacts associated with accounts)
• Opportunity (No access OR View all OR View and edit all opportunities associated with accounts)
• Case (No access OR View all OR View and edit all cases associated with accounts)
• Leads (View, edit, and transfer OR View, edit, transfer, and delete)

* You can set access for the Contact and Lead if you use Private as the default internal access for contacts or cases.

Default access levels determine the default selection when creating new territory.

Territory Model

• Defines the structure and assignment of sales territories and their associated accounts and users.
• It's a hierarchical structure that organizes sales teams and their responsibilities.
• Allow for flexible assignment of accounts and users to territories based on various criteria.
• You can create and preview multiple models (2 for EE, 4 for UE/PE), but only one can be active at a time.
• Once a model has been created, you can open it to Clone, Activate/Archive, or view more info, such as the activation date, etc.

Territory Type

• It can help you group territories based on geography (e.g., North America, Europe), industry (e.g., Financial Services, Retail), or other factors.
• To categorize territories at a more abstract level, not within the hierarchy itself.
• Can be used in reports to analyze sales performance by type (e.g., compare sales across geographical regions). 
• Every territory you create must have a territory type.
• Territory types are used for organizing and creating territories only: they do not appear on territory model hierarchies.
• Each territory type has a priority (it must be a number). For example, "1" indicates the highest or lowest priority.

Create New Territory

Once the Territory Type and Territory Model are created (Territory Model does not need to be activated), you can add the Territory from the "View Hierarchy" in a Territory Model. When creating a new territory, you need to select:

• Territory Type 
• Parent Territory, this is populated by default
• Description (optional)
• Access level for: Account, Contact, Opportunity, and Case

After a territory is created, you can:

• Edit the Territory to set the Forecast Manager (for forecasting purposes)
• Assign users
• Manually add accounts
• Create assignment rules

- An assignment rule can be assigned to multiple territories
  - You need to run the rule when the account or assignment criteria are changed

• Create a child territory

- Inherited Assignment Rules from the parent territory

• Click the 'View Accounts' button to see all Accounts that fit into the rule. 

Account

Add the Assigned Territories related list to the Account page layout, and you will see all Territories related to the Account

Reference:

• Enterprise Territory Management Is Now Sales Territories
• Salesforce Sharing Using Enterprise Territory Management
• What's new in Enterprise Territory Management
• Managing Users and Roles Within Territories

Salesforce: Inactive User

When a Salesforce user has been deactivated, can we still assign the user as the record owner, or populate the user into a lookup field? 

1. Lookup Fields

From the Page Layout (UI): In the standard Salesforce user interface, you typically cannot select or populate a lookup field with an inactive user. The UI filters out inactive users from lookup fields to prevent confusion and ensure that only active users are selectable. Therefore, if you are trying to populate a lookup field from the page layout, you will not see inactive users listed.

From the Backend: You can populate lookup fields with inactive users through backend processes. This includes using data import tools, APIs, or automated processes (like Apex code, workflows, or triggers).

2. Record Ownership

From Setup > User Interface > User Interface, look for "Set Audit Fields upon Record Creation" and "Update Records with Inactive Owners" and enable it. Then, create a permission set with "Update Records with Inactive Owners" permission or enable the permission in the profile.

From the Page Layout (UI): In the standard Salesforce user interface, you typically cannot find or populate the record owner with an inactive user, even if you already have the above permission granted.

From the Backend: If you have "Update Records with Inactive Owners" permission enabled, you can populate record ownership with an inactive user through backend processes. This includes using data import tools, APIs, or automated processes (like Apex code, workflows, or triggers).

Without the permission enabled, you will receive the error message INACTIVE_OWNER_OR_USER:

CRM Analytics: Unsupported Salesforce Data

CRM Analytics (CRMA) is an analytics tool by Salesforce and is hosted in Salesforce's core platform; however, not all of Salesforce's objects and fields are supported by CRM Analytics data sync, including external objects, so you can't build a CRMA dashboard that uses those fields or objects. Check out the following article.

A supported object is one for which you can grant field-level access in Setup. If you're unable to assign field access to a Profile in Setup, that object is considered unsupported in CRMA, e.g. LoginHistory object.

The following statement from the above help article explains this: "To extract fields, the object must be visible to the Integration User. If you can’t manage a field’s visibility in Setup, you can’t grant the Integration User access to it."

Reference:

• Unsupported Salesforce Objects and Fields in CRM Analytics