Einstein Analytic Note: Data layer/ Dataflow vs Recipe

Dataflow should be build from the lowest grain data source. All lookup fields could be added in the dataflow.

Digest node:

filter is not recommended to add in digest node --> use filter node.
dimension field should have N/A as a default value for grouping.

Compute Relative: column based calculations (last/first day, latest opty by account, biggest opty by country, change from previous amount/stage/...)

Compute Expression:Row based calculations (margin, same row date calculations, saql case statement...)

Recipe: transform dataset.

Tips:

Combine datasets in data layer --> reduce dependency on saql

Add derived fields in data layer --> reduce dependency on Json binding

Add common lookup fields to datasets --> reduce dependency on Json binding

Resource:

Choosing Dataflow or Recipe (tbh, I dont think I could choose which one I should use if I watch this video solely)

Comments

The flow failed to access the value because it hasn't been set or assigned error

I'm sure that many Salesforce admin already encountered the this Process builder error when building automation referencing a field on a related record (aka lookup field): ' The flow failed to access the value because it hasn't been set or assigned ' and came across this Salesforce document . However, it does not help in case of referencing a User lookup field. ------------------------------- Use case: when a lead's ownership is transferred to another user, respective fields are updated based on their profile. Error element myDecision (FlowDecision). The flow failed to access the value for myVariable_current.Owner:User.ProfileId because it hasn't been set or assigned. --------------------------- Workaround: Have a condition to check if the record is assigned to a user or a queue before checking their profile id for respective actions. Records owned by user: BEGINS([Lead].OwnerId, "005") Records owned by queue: BEGINS([Lead].Owne...

Salesforce campaign model and tracking

Salesforce campaign tracking Check out the great article on Campaign tracking use case: https://www.salesforce.com/blog/track-salesforce-campaign-shadow-wolf-blog/ There are 2 ways to track Campaign ROI . Campaign Influence ( custom model ) Associate multiple Campaigns to multiple Opportunities (and multiple Opportunities to a Campaign) using the Contact Role . To get a broader view of opportunity pipeline, generate the standard report called Campaigns with Influenced Opportunities (Customizable Campaign Influence). This report provides opportunity data, such as amount, stage, and revenue share alongside helpful campaign details. For more control, build custom reports that show relationships such as these examples. • Campaigns with Influenced Opportunities • Contacts with Campaign Influence • Accounts with Campaign Influence If there is only one campaign associated with each opportunity ...

Renewable vs Evergreen Subscription type

Renewal: Renewable products transfer to renewal quotes. Standard renewable contracts have end dates, terms, and an option to renew. Evergreen: don't have any end dates and, therefore, don't need to be renewed. This supports an open-ended term of service that allows for customers or providers to cancel or terminate the subscription at any point. Evergreen and Renewable products can’t coexist in a bundle. Guidelines for Evergreen Subscriptions: https://help.salesforce.com/s/articleView?id=sf.cpq_evergreen_limitations.htm&type=5 Quote and Manage Evergreen Subscriptions: https://help.salesforce.com/s/articleView?id=sf.cpq_evergreen_use.htm&type=5

My Salesforce notes

Search This Blog