FieldKo captures rich field data – such as visit records, task completions, and survey responses – all within Salesforce. This means you can use Salesforce Lightning reports and dashboards to analyse and visualise FieldKo data.
In this article, we’ll walk through building custom reports and dashboards based on FieldKo data, using standard Salesforce functionality. You’ll learn how to create reports (filtering by field rep, date, account, etc.), leverage FieldKo’s report types, and add components like tables, charts, and KPI metrics to a dashboard. We’ll also share tips for common dashboard use cases (field team productivity, call cycle adherence, visit outcomes) to help you get the most out of your FieldKo data.
Building Reports with FieldKo Data
The first step in creating a dashboard is building the underlying reports. FieldKo’s data is stored in Salesforce objects (e.g. Visits, Tasks, Surveys), so you can create reports on these objects just like any Salesforce data. FieldKo provides custom report types that join its objects, making it easier to report on related data (for example, a report type combining Visits with related Task or Survey information).
To create a FieldKo report in Salesforce Lightning:
Navigate to the Reports tab: In Salesforce, click on the Reports tab (in Lightning Experience). Then click New Report to launch the report builder.
Select a FieldKo report type: In the Choose Report Type dialog, find FieldKo’s report types or objects. For example, select Visits (or a specific FieldKo report type like “Visits with Tasks” if available). This defines which data will be in your report.
Choose fields and format: Add the columns you need by selecting fields (such as Visit Date, Field Rep, Account Name, Task Status, Survey Score, etc.). Decide on a report format:
Use a Tabular report for a simple list of records.
Use a Summary report to group data (e.g. group visits by rep or by account).
Use a Matrix report for a grid comparison (e.g. visits per rep by month).
FieldKo supports all standard Salesforce report formats, including joined reports and custom report types.
Apply filters: Refine the report by adding filters for the desired data scope:
Date filters: e.g. Visit Date during the current month, last week, or a custom range.
Field Rep filter: e.g. Field Rep equals a specific user (or use “My Visits” to show the current user’s data).
Account filter: e.g. Account Name equals Acme Stores (or use a contains filter for a region or segment).
You can stack multiple filters. For example, you might filter Visit Date = “This Month” AND Field Rep = Alice Nguyen to see Alice’s visits this month. Use the filter logic as needed to combine criteria.
Group and summarise (if needed): If you chose a summary or matrix report, define groupings. For instance, group rows by Field Rep to see per-rep totals, or by Account to see visits per account. The report builder will then allow you to add summary fields (e.g. record count, average, sum) for those groups. For example, you could show the count of visits per rep and the average survey score per rep.
Run and save the report: Click Run to preview the results. Adjust filters or columns if needed. Once satisfied, click Save. Give the report a name (e.g. “Visits by Rep – Current Month”) and choose a folder that your dashboard will have access to (folders control who can see the report). Now you have a report based on FieldKo data that can be used in a dashboard.
Tip: FieldKo’s custom report types make it easy to include related data. For example, using a “Visits with Tasks” report type would let you report on visit outcomes alongside task completion in one report. Similarly, a “Visit Survey Responses” report type could show survey answers linked to each visit. Leverage these where possible to avoid having to create separate reports for closely related data. Custom report types are essentially templates that pre-define the relationships between objects in FieldKo. If a suitable report type doesn’t exist, an admin can create one to combine FieldKo objects as needed.
Creating a Dashboard in Salesforce Lightning
Once you have one or more reports on FieldKo data, you can assemble them into a dashboard for at-a-glance insight. Salesforce Lightning dashboards allow you to display multiple report visuals on one page (for example, a chart of visits by rep, a table of recent tasks, and a KPI number of completed surveys). All of this uses standard Salesforce dashboard functionality, so no code is required.
To build a FieldKo dashboard:
Navigate to the Dashboards tab: In Salesforce, click Dashboards, then New Dashboard. This opens the Lightning Dashboard Builder.
Set dashboard properties: Give your dashboard a name (e.g. “Field Team Performance Dashboard”) and description. Choose the appropriate folder (same as or accessible to where your reports are saved). You can also set the dashboard’s viewing options (such as running user – for most cases, “Run as logged-in user” so each person sees their data, or a specific user for a company-wide view).
Add a component: Click + Component to add your first dashboard component. A dialog will appear to select a source report and the type of visualization. Choose one of your FieldKo reports as the data source. Then select a display type:
Chart: Salesforce offers bar charts, line charts, pie/donut charts, etc. Choose a chart that suits your data. For example, select a bar chart for “Visits by Rep” to compare field reps, or a donut chart to show the breakdown of visit outcomes (completed vs missed).
Table: To show a list of records or a detailed view, use a table. You can display top or bottom records by a metric (e.g. list the top 10 accounts by number of visits).
Metric (KPI): A single number component that highlights a key metric. For example, you might use a metric component to show the total number of visits this week or the % of tasks completed.
Gauge: A dial graphic useful for showing progress against a target. You could use a gauge to display, say, “Call Cycle Adherence” – the percentage of planned visits completed, against a 100% goal. (In the source report, you’d need a percentage or ratio value to use a gauge effectively.)
Lightning Table or Chart: (All charts and tables in Lightning are added through this same interface – you just choose the format in this step.)
After selecting the type, click Add to place it on the dashboard canvas.
Configure the component: Once added, you can configure component details in the right-hand panel. Give it a meaningful title (the default is the report name, but you can label it like “Visits by Representative – This Month”). If it’s a chart, you can adjust things like the display units, legend, and hovering info. For tables, choose how many rows to display (e.g. show 10 rows). For metrics or gauges, set the appropriate values (e.g. for a gauge, set the max or target value if needed). Salesforce will automatically aggregate the data based on the report (e.g. if your report is summarized by rep, a bar chart will have one bar per rep).
Repeat to add more components: Continue adding components for each report or metric you want on the dashboard. You can mix and match charts and tables. For example, your dashboard might contain:
A bar chart of Visits by Region (from a summary report grouping visits by region).
A pie chart of Visit Outcomes (e.g. percentage of visits that met all compliance criteria vs those that failed any, drawn from survey data).
A table of Open Tasks from Visits this Week (to highlight any pending tasks).
A KPI metric showing Total Visits This Month.
A gauge showing Task Completion Rate.
Arrange the components on the grid by dragging and resizing them to make the dashboard easy to read.
Apply dashboard filters (optional): Lightning dashboards allow up to 3 filters that can apply to all components. For instance, you could add a dashboard filter on Region or Team. This lets viewers toggle the dashboard to only see data for a particular region or team. If you add filters, you’ll map the filter to relevant fields on each component’s source report. This is optional but can make a single dashboard more flexible for different audiences.
Save and view the dashboard: Click Save when you’re done editing. Then Done (or View Dashboard) to exit the builder. Now you can see your live dashboard. All the components will display the latest data from their reports. Users can refresh the dashboard to retrieve up-to-date data (or you can set it to refresh automatically each day). The dashboard can be shared with others who have access to the folder.
Tips for Common Dashboard Use Cases
Different teams will have different metrics they care about. Here are a few common FieldKo dashboard use cases and tips on how to build them:
Field Team Productivity: This dashboard focuses on the efficiency and output of your field reps. Use reports that track the number of visits completed per rep, tasks completed, and hours worked. For example, create a summary report grouped by rep with a count of visits and completed tasks in the past week or month. A bar chart can compare Visits per Rep, and a separate bar or line chart can show Tasks Completed per Rep. Include a metric for the Average Visit Duration if that data is captured (you might calculate this via a formula field or in the report). This helps managers quickly see who is handling the most visits or if anyone is falling behind. You might also include a table of Top Performers (reps with the most visits or highest survey scores) to encourage friendly competition.
Call Cycle Adherence: FieldKo’s call cycle feature plans recurring visits for reps. A call cycle adherence dashboard shows how well the team sticks to the schedule. You can report on planned vs. completed visits. One approach is to use a custom formula field or a report that flags whether a visit was completed on time. For example, create a report with filters like Planned Date = This Week and group by rep, showing two summarized fields: # of Planned Visits and # of Completed Visits. Then on the dashboard, use a gauge or metric to display the % of Visits Completed (completed vs planned). A donut chart could show Completed vs Missed Visits for the team. Also consider a table listing Missed Visits (visits not completed by their due date) so the team can follow up. This dashboard helps ensure your field team covers their route as expected.
Visit Outcomes and Compliance: This type of dashboard highlights the results of field visits. If FieldKo surveys are used for compliance checks or scoring visits (e.g. store audit scores, safety inspection results), include charts for those outcomes. For instance, use a summary report of survey results grouped by outcome (Pass/Fail or score ranges) to create a donut or bar chart of Visit Compliance Rate. A line chart can show Trend of Average Audit Score over time (e.g. by month) to see improvement or decline in visit quality. If you track follow-up actions or tasks resulting from visits, include a component for those – e.g., a table of Open Corrective Actions from visits. You might also use a metric component for something like Overall Compliance % or Average Score across all visits. This dashboard gives stakeholders a clear view of field visit quality and any issues that need attention.
General Tips: Keep dashboard components focused and uncluttered – each chart or table should answer a specific question. Use clear titles and, if needed, add labels or tooltips in charts to clarify metrics (for example, label a percentage or a target line). It’s often helpful to mix high-level metrics (KPIs) with detailed tables so users can drill into the data after seeing a summary.
Also, remember that all components on a Salesforce dashboard are derived from reports – if you need a new metric, you might have to adjust the source report (for example, add a formula field or summary in the report to use in a dashboard gauge). Fortunately, FieldKo leverages Salesforce’s reporting engine, so you have a lot of flexibility in slicing and dicing the data. By combining the right reports and visualisations, FieldKo dashboards will give your team real-time insight into field operations and performance, all within the Salesforce Lightning interface.