Skip to main content
A perfect store dashboard puts your most important retail execution metrics on one screen: coverage, call compliance, availability, and compliance with planograms and promotions. Use this page to lay out the dashboard from the recipe reports, build a weighted perfect store score, add filters by region and rep, and choose where your team sees it.

User Permissions Needed

Before You Begin

  • Build and save the source reports from the report recipes. Each dashboard component shows one report.
  • Save the reports in a folder that everyone who views the dashboard can access. See Share, Schedule, and Subscribe to Reports.
  • Agree on the weights for your perfect store score with your sales and trade marketing leads.

Build a Perfect Store Score

A perfect store score is a weighted index, such as availability 40%, planogram 30%, promotion 20%, and pricing 10%. Dashboards can’t combine numbers from different reports into one score, so build the weighting into a scored survey:
  1. Ask your admin to create a scored Perfect Store survey, with Calculate Score set to SUM. See Scoring.
  2. Give each section of questions points in proportion to its weight. For example, availability questions worth 40 points in total, planogram questions 30, promotion questions 20, and pricing questions 10.
  3. Add the survey as the Default Survey of a task type that’s on every visit, or in your visit templates.
  4. Ask your admin for a report type with Task Surveys as the primary object that includes Score Obtained, Out of Score, Score %, Survey, and the visit’s Account and Sales Representative.
  5. Build a report on it, filtered to the survey and Completion Date This Month. Group by Account, summarize Score Obtained and Out of Score with Sum, and add a summary formula with Percent formatting that divides the first by the second.
The result is each store’s perfect store score out of 100%. Ranging OSA isn’t part of the survey score. Show it next to the score, or ask your admin about combining it with automation. See Flow Recipes for Field Teams.

Lay Out the Dashboard

Put headline numbers at the top, then charts that show where the gaps are, and then tables reps can act on. To create the dashboard, click the Dashboards tab, click New Dashboard, and then add each component from its report. See Build a Dashboard in Salesforce Help.

Add Filters by Region and Rep

Dashboard filters let one dashboard serve every region and rep:
  1. In the dashboard builder, click + Filter.
  2. Select the field, such as the account’s Shipping State/Province or your company’s region field, and add the values your team uses.
  3. Add a second filter on the rep, such as Sales Representative or Account Owner.
A filter applies only to components whose report includes that field. Visit-based reports use Sales Representative, and account-based reports use Account Owner, so check each component after you add a filter. Ask your admin to add the same region field to every report type you use.

Choose the Running User

A dashboard shows data as one user sees it, called the running user. Choose the running user in the dashboard’s properties:
  • Run as me, or as a specified user: Everyone sees the same team data. Use this for a manager or leadership dashboard.
  • Run as the logged-in user: Each viewer sees only the data they can access, so reps see their own stores. This is a dynamic dashboard. Whether it’s available and how many you can have depend on your Salesforce edition.
When a dashboard runs as you, everyone who can open it sees what you can see, including other reps’ stores and orders. Save it in a folder shared only with people who should see that data.
For details, see Dashboard Running Users and Reporting Snapshots.

Where Your Team Sees It

  • Salesforce: On the Dashboards tab. Your admin can also add the dashboard to the home page of the FieldKo app. See Customize the FieldKo App and Home Page.
  • FieldKo Atlas app: Reps open dashboards from Dashboard in the side menu, if your admin turned it on. The app shows donut, pie, bar, column, line, gauge, metric, and table components. Other component types show “This component is currently not supported.” See View Dashboards.
If reps will use the dashboard in the app, use only the supported component types, and keep the filters to a few values so the buttons are easy to tap.

See Also

Last modified on October 20, 2026