1. If you’re using Service Analytics (Classic) with previous dashboards built with the old dashboard designer, use this syntax to embed the dashboard in a Salesforce Classic page: filter="{'ServiceCase1': {'Id': ['{!case.Id}'], 'OwnerId' : ['{!case.OwnerId}'], 'Product__c' : ['{!case.Product__c}'], 'Reason' : ['{!case.Reason}']}}".Also do the following:Replace ‘Product__c’ with the name of thecustom field you use to track product family. See Step 4 to learn how to find thename of that field.Replace ‘Reason’ with the API name of thefield you use to track the case reason. This field is the answer you selected inthe configuration wizard, Page 2, Question 5. Find the API name of this field bygoing to Setup and typing Cases in the QuickFind box. Then click Fields and review your custom field names to find the fieldyou use for case reason. Look for the API name of the field, and use that in placeof ‘Reason’ in the query
2. Replace ‘Product__c’ with the name of thecustom field you use to track product family. See Step 4 to learn how to find thename of that field.
3. Replace ‘Reason’ with the API name of thefield you use to track the case reason. This field is the answer you selected inthe configuration wizard, Page 2, Question 5. Find the API name of this field bygoing to Setup and typing Cases in the QuickFind box. Then click Fields and review your custom field names to find the fieldyou use for case reason. Look for the API name of the field, and use that in placeof ‘Reason’ in the query
4. If you’re using the latest version of Service Analytics based on the new dashboard designer, use this syntax to embed the dashboard in a Salesforce Classic page: filter="{'datasets' : {'ServiceCase1': [ {'fields':['Id'], 'filter': { 'operator':'in', 'values': '{!case.Id}'} }]}}".
5. If you’re embedding a dashboard from the latest version of Service Analytics in a Lightning Experience page, use this syntax: filter=”{'datasets' : {'ServiceCase1': [ {'fields':['Id'], 'filter': { 'operator':'in', 'values': ['$Id']} }]}}”.