--- schema_version: "1" id: ebabeaf77f6414f8d357369dfb43b499c2b89d79ecfafa6a5695338faf13597a title: Revenue Insights Post Installation Steps collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/revenue_insights_post_install.md canonical_url: https://help.salesforce.com/s/articleView?id=sales.revenue_insights_post_install.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 258c964b343f11ba1b615868e2a46f36e2cadee68783eb09f71af825a3632989 description: To see your data in the dashboards after you install Revenue Insights, you must schedule your app to refresh. You can add Revenue Insights to your navigation bar or edit your permission settings depending on configuration settings. Lastly, you can add additional filters to your panels. products: - Sales Cloud release: "264" --- # Revenue Insights Post Installation Steps To see your data in the dashboards after you install Revenue Insights, you must schedule your app to refresh. You can add Revenue Insights to your navigation bar or edit your permission settings depending on configuration settings. Lastly, you can add additional filters to your panels. ## Schedule the App You can set or change the app schedule or refresh the data as needed on the app management tab. For more information, see [Change Your Intelligent App Settings](https://help.salesforce.com/s/articleView?id=analytics.update_intell_apps.htm&type=5&language=en_US). Select a time outside normal work hours so the data refresh doesn’t interrupt business activities. The app now syncs and runs the recipes in the correct order every day at the time you set. ## Add Revenue Insights to your Navigation Bar To make it easy to view your insights, add the Revenue Insights App to your Navigation Bar. 1. From the Sales App, click the pencil icon. 2. From the **Edit Sales App Navigation Items** select **Add More Items**. 3. From the **Available Items** column, click **All**. 4. In the Search field, enter **Revenue Insights**. 5. Select Revenue Insights, and click **Add 1 Nav Item** and click **Save**. ## Verify Your Permission Settings When you turn on CRM Analytics for your org, a default Analytics Integration User is created. This "user" accesses the data within Salesforce when the recipe is used to bring data in as datasets to CRM Analytics. It's important that this user has the proper level of permissions to read the data you're trying to pull from the org to CRM Analytics. For example, the integration user must have object-level access to all the objects from which data you want to pull. And you need field level access to the fields within those objects. If you have trouble in creating your app or can’t view data, modify either object or field permissions. You must allow the integration user profile to have read access them. ## Add Additional Filters to Your Dashboards You can add additional filters to the Sales Performance dashboard. This dashboard has a **Compare by** selection as well as five global filters by default. You can add additional filters to the Overview dashboard. To add an additional global filter in the filter row of the Sales Performance dashboard: 1. From the Sales Performance dashboard, select **Edit** in the upper right-hand corner. 2. Click in the panel that displays the five global filters. 3. On the panel on the right, select **Manage Global Filters**. 4. Click **Add a Global Filter.** 5. From the menu, select the Opportunity RevInsights dataset. 6. Select the field you want to add. For example, you can select Industry. 7. Choose the field you want like to add and click **Create**. 8. By default, the filter panel shows five filters in one row. Edit the number of filters displayed to view your new filter in the row of default filters. 9. Click in the filters panel again to open the right side panel. You can see that the **Filters per Row** field is set to 5. 10. On the side panel change the **Filters Per Row** to 6. 11. To view the changes, click **Preview**. 12. Click **Save** if you’re satisfied with the changes. To add another option to the **Compare by** filter of the Sales Performance dashboard: 1. From the Sales Performance dashboard, select **Edit** in the upper right-hand corner. 2. Click in the **Compare by** field. 3. On the panel on the right, select **Advanced Editor**. The widget JSON code displays. 4. To show the query code, select **Query**. 5. Copy and paste the last code snippet that looks like the following: ``` { "Display": "Opportunity Owner", "Field": "'User.UniqueUserName'", "projection": ", closed['User.UniqueUserName'] as 'User.UniqueUserName'", "saqlField": ", 'User.UniqueUserName'" } ``` 6. To use the compare by field you want to add, edit the code snippet. For example ``` { "Display": "Industry", "Field": "'Account.Industry'", "projection": ", closed['Account.Industry'] as 'Account.Industry'", "saqlField": ", 'Account.Industry'" } ``` ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_pipe_visibility-264-0-0-production-enus/75640128-02d2-4752-84b3-eb077e12fb74/images/icon_note.png) Note Only fields from the Opportunity RevInsights dataset can be added as options. 7. Save your changes. To add a filter to the Overview dashboard: ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_pipe_visibility-264-0-0-production-enus/75640128-02d2-4752-84b3-eb077e12fb74/images/icon_note.png) Note The Overview page combines multiple datasets and live queries. The challenge of adding a filter here means that the field-selected needs to apply to all of the data sources. For example, you want to add a Region filter, such as Billing Country, to the dashboard. This field is in the Opportunity RevInsights dataset so most of the widgets on Overview will facet automatically by default. However, the SOQL queries look at the ForecastingItem object. This object doesn’t have a way to filter by country because the forecast is done at the individual person level. 1. Drag a list filter to the desired location on the dashboard. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_pipe_visibility-264-0-0-production-enus/75640128-02d2-4752-84b3-eb077e12fb74/images/icon_note.png) Note Don’t select global filters. 2. Select the dataset that includes your field. Salesforce recommends you use the Opportunity RevInsights dataset because most queries on the dashboard use this dataset. 3. Select a field and configure the design. 4. Open up the dataset connections and add a connection for your field, if applicable. Most queries on Overview, Team Performance, and Sales Performance tabs can facet based on these steps. The top section on the Overview dashboard, including the Team Quota Attainment, KPIs, as well as the forecasting chart may not facet. The faceting doesn’t happen because there are live queries based on Forecasting Item. The dashboard uses the following datasets: - Opportunity RevInsights - UserRole - OpptyProduct - Activity - OpportunityHistory - Forecasting Quota 5. Modify queries beginning with soql\_. If there’s a field that can be found in the ForecastingItem object and is pulled in for the Revenue Insights app, in addition to adding dataset connections, the soql queries require an additional binding. The following shows the default query for soql\_user\_closed\_won: ``` "query": "SELECT SUM(ForecastAmount) ForecastAmount FROM ForecastingItem {{toArray( toArray("Owner.UserRoleId", "IN", row(intermediate_step.result, [0], ["UserRoleId"])), toArray("ForecastingTypeId", "IN", row(forecasting_type.selection, [0], ["ForecastingTypeId"])), toArray("OwnerId", "IN", row(intermediate_step.result, [0], ["Id"])), toArray("Period.StartDate", "BETWEEN", row(CloseDate_1.selection, [0], ["min", "max"]))).asSQLWhere("sobject", true)}} AND ForecastingItemCategory = 'ClosedOnly'", ``` 6. If an additional field is added, use an additional binding: ``` "query": "SELECT SUM(ForecastAmount) ForecastAmount FROM ForecastingItem {{toArray( toArray("Owner.UserRoleId", "IN", row(intermediate_step.result, [0], ["UserRoleId"])), toArray("ForecastingTypeId", "IN", row(forecasting_type.selection, [0], ["ForecastingTypeId"])), toArray("OwnerId", "IN", row(intermediate_step.result, [0], ["Id"])), toArray("Period.StartDate", "BETWEEN", row(CloseDate_1.selection, [0], ["min", "max"]))).asSQLWhere("sobject", true), toArray("NewField", "IN", row(listfilter_name.selection, [0], ["FieldName_in_listfilter"]))}} AND ForecastingItemCategory = 'ClosedOnly'", ``` ## Create Other Versions of Revenue Insights After the initial instance of Revenue Insights is auto-created, you can create other versions via Analytics Studio so that your team members can use the version that meets their needs. You can create as many versions as you need. When your team members go to view the dashboard from the Revenue Insights tab, they can select the appropriate instance of Revenue Insights depending on their forecast type. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_pipe_visibility-264-0-0-production-enus/75640128-02d2-4752-84b3-eb077e12fb74/images/icon_note.png) Note While you can create as many Revenue Insights versions as you like, recipe and data sync limits apply. To create other versions of Revenue Insights: 1. From Setup, in the Quick Find box, enter Revenue Insights, and then select **Revenue Insights Setup**. 2. From Revenue Insights Setup, you can see details about your auto-installed app and a link to Analytics Studio. To create more versions of Revenue Insights, click the link to **Analytics Studio**. 3. In Analytics Studio, click **Create** in the upper right corner. 4. To open the template picker, select **App**, then **Create App from Template**. 5. Locate the **Revenue Insights** tile, select it, and click **Continue**. 6. Review the app preview page, and click **Continue** to open the configuration wizard. 7. If you’re offered a choice of basing your app on an existing app or creating a one, select **Create a brand new app** and click **Continue**. The app runs a compatibility check against your org to ensure it includes the data to successfully create the app’s datasets, recipes, and dashboards. If it doesn’t, follow the instructions in the error message to add the required data and start the app creation process again. 8. When the org compatibility check succeeds, click **Looks good, next**. 9. Name your app, and click **Create**.