Skip to main content
This reference lists every FieldKo custom setting and custom metadata type that changes how the FieldKo Atlas app behaves, with each one’s fields, defaults, and effects in the app. Settings are grouped by the area of the app they affect. To find a setting, start with the Find a Setting table, or search the page (Ctrl+F or Cmd+F) for the setting’s label.

User Permissions Needed

Find a Setting

Before You Begin

From Setup, in the Quick Find box, enter Custom Settings or Custom Metadata Types, select that item, and then click Manage (custom settings) or Manage Records (custom metadata types) next to the setting. For hierarchy settings, the app uses the most specific value: user, then profile, then org default.

How to Read the Tables

  • Setting line: Each table starts with the setting’s name as shown in Setup, and whether it’s a hierarchy or list custom setting or a custom metadata type.
  • Field: The field label as shown in Setup.
  • What It Does: The effect in the app when the field is on or filled in.
  • Default: The package default for a new record. A blank default means the field is empty or has no package default.
Settings marked † are available in newer package versions. If you don’t see one in your org, your package version doesn’t include it, and the app uses its default behavior. Their labels in your org may differ slightly from the names shown on this page.

FieldKo Configuration Tab

From the App Launcher, find and select FieldKo Configuration. Each section of the tab saves to the settings in the following table, so you can change these options here instead of in Setup. If the Calendar Language or Map Language doesn’t save, set it in the Language Support custom setting. You set every other setting on this page in Setup.

Mobile App

The settings in this section control the app’s side menu, visit screen, sync, photos, and appearance.

Side Menu

Menu Configuration (hierarchy custom setting) controls which items appear in the app’s side menu.
If no Menu Configuration record exists, the app shows Accounts, Visit Map, and Visit Calendar. After a record exists, any unchecked or missing field hides that item. Before you create a record, decide which items reps need and select each one.
My Visits, Sync, Settings, and Logout always appear. The current app doesn’t use Display Expense, Display My Objectives, Display Order 2.0, or Display Planogram. Objects To be Fetched (list custom setting). Add one record per object you want in the app. See Add an Object to the App.

Visit Actions

Visit Actions Configuration (hierarchy custom setting). Each checkbox shows an action on the visit screen. As with Menu Configuration, after a record exists, a blank field hides that action. Object for visit action (custom metadata type). Adds an action that lists or creates related records from a visit. The package includes sample records: Asset, Contact, Create Task, Orders, Pack Out, and Visit. To use them, add their names to More Objects As Actions. Pack Out shows the pack-out screen.

Sync

Sync Configurations (hierarchy custom setting) controls background sync, the Sync Images default, and sync batch sizes.
If there’s no Sync Configurations record, the app turns background sync off. Installing the package creates the org default record. If reps say background sync isn’t running, check this record in Setup.
The current app doesn’t use Background Sync Batch Size, Enable Location Tracking, or Interval for Location Tracking. Enhanced Sync screen is deprecated.

Photos and Files

Object Names for Attachment Sync (list custom setting). Add one record per object. For the record Name, enter the object’s API name. Find it in Setup > Object Manager. Questions and FieldKo products always download all their images. Survey answer photos download from the start of last month. File Configurations (hierarchy custom setting) controls how photos upload and where survey answer photos are linked.

Appearance and Security

Fieldko Native Theme Colors (list custom setting). You can also edit these on the FieldKo Theme tab. Security Configuration (hierarchy custom setting) controls the app’s extra encryption.

Visit Configurations

Visit Configurations (hierarchy custom setting). Controls check-in, visit types, visit names, reminders, and check-out in the app. You can also set several of these fields on the Visit section of the FieldKo Configuration tab. Other fields affect Salesforce screens only, not the app: Skip Event Creation For Visit, Hide Subject on Add Task Popup, Expand All Task Groups By Default, Do Not Override Planned End Date?, and the Summary PDF dates.

Account Location Fields

Account search result Configuration (hierarchy custom setting). Besides account search results, this setting also holds these app settings.

Calendar

Calendar Configurations (hierarchy custom setting) controls calendar views, account cards, and account search.

Visit Duration, Visit Types, and Visit Creation

Visit Duration (list custom setting, record “Default Minimum”) sets the minimum visit length. Visit Type (custom metadata type). To set up visit types, see Set Up Call Cycles, Tasks, and Visit Templates. Visit Creation Configuration (custom metadata type). Lets reps create visits from objects other than Account. See Create Visits from Other Objects. The sample Account and Opportunity records are inactive.

Surveys

Survey Settings (hierarchy custom setting). You can also set these options on the Survey section of the FieldKo Configuration tab. On each question, you can set Answer Not Required?, Include Photo on Question, Make Photo Required, and Max Answer Photos † (up to 5). On each survey, you can set Allow Survey Completion Without Checkin?. See Build Surveys.

Orders

Order PDF Setting (list custom setting, record “PDF”). For the main fields, such as currency, hidden prices, and discounts, see Order Settings. Pricebook Entries Configurations and Order Line Items Configurations (list custom settings). Add extra columns to the order screen. For each record’s Name, enter the field’s API name. Find it in Setup > Object Manager. Do Show Cart On Place Order (hierarchy custom setting) controls the cart on the order screen.

Core Ranging

Core Ranging Configurations (hierarchy custom setting) adjusts the ranging screen, and Ranging Columns Configuration (custom metadata type) sets the columns reps fill in. For their fields, see Core Ranging.

Sync Scope and Metadata

These settings decide which records, objects, layouts, and accounts reach the app. Each row is a separate setting.

Page Layouts

The app uses the page layout assigned to each rep’s profile and record type. To show a different layout in the app, add a FieldKo Layout Override (custom metadata type) record. An override adds a layout for those reps alongside their assigned layout. After you add overrides, re-run the Metadata Collector. Read-only layout fields are read-only in the app.

Objects Outside the FieldKo Packages

Leave requests and pack-out Principal and Category values aren’t part of the FieldKo packages. If your org has a custom Leave object, add it to Objects To be Fetched with Show In Menu selected to give reps leave requests.

See Also

Last modified on October 20, 2026