Skip to main content

Posts

Showing posts from October, 2020

Einstein Analytic Notes: Binding

Binding type: selection and result. Selection : a user need to click on somewhere in the dashboard. Selection interaction can be used to: Specify interactions between widgets which use queries from different datasets. In addition to filters, specify the measures, groupings, and other aspects of a query. Set widget display properties for some widget types (number and chart only Result : user does not need to click on dashboard or there is hidden step. A results interaction is typically used to: Define intermediate results for a complex calculation. For example, to calculate the total opportunity amount for the top-five products, use one query to calculate the top-five products. Then use those results to filter another query that calculates the total number of open cases for each product. Set an initial filter selection for a dashboard based on a characteristic of the logged-in user, like their country. Dynamically change the display of a widget based on the results of a query. For examp

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)

Passing record id in Lightning Flow lookup field for List button in Related List

 Use case: Create a list button from Account related list and pre-populate the Lookup field   Create an input variable Acctid to store Account id and get the Name of from that record id. Check "Manually assign variables (advances)" and put the Id and Name from the found record.  Debug: Create List Button in Competition Battle Card and add it to Account related list