Skip to main content
The FieldKo Atlas app downloads part of your org to each rep’s device so reps can work offline. This page has 2 parts:
  • How FieldKo Chooses What Syncs explains which objects, fields, and records each rep gets. Read it when a rep is missing data.
  • Change What Syncs has the steps to narrow records, add an object, run the Metadata Collector, and choose the layout reps see.
New to sync? See Key Concepts.

​
How FieldKo Chooses What Syncs

This part explains the rules. To change them, go to Change What Syncs.
Salesforce sharing always applies. FieldKo then narrows what each rep receives with its own rules, so reps don’t get everything they can see in Salesforce.

​
Which Objects Sync

The app syncs the objects that have an Object Metadata record. The Metadata Collector creates these records from:
  • The FieldKo objects (accounts, contacts, visits, tasks, survey answers, orders, price books, products, ranging, contracts, incidents, and others)
  • Every object listed in the Objects To be Fetched custom setting
  • Parent objects referenced by lookup fields on your page layouts, and child objects shown in related lists
FieldKo leaves out every object listed in Objects To Exclude. You can sync custom objects and these standard objects: Account, Contact, Note, Event, Case, Asset, Task, and Opportunity. Other standard objects can’t sync, even if you add them to Objects To be Fetched.

​
Which Fields Sync

For each object, the app gets every field that appears on any of its page layouts. It also gets:
  • Every field on FieldKo package objects
  • Every custom field, and the address and owner fields, on Account
  • Record type, last modified date, and a few system fields on every object
Fields that a rep can’t read through field-level security are always left out.
To make a field available in the app, add it to a page layout for that object, give reps field-level access, and rerun the Metadata Collector.

​
Which Records Sync

FieldKo decides which records each rep gets from 2 things: the rep’s accounts and a date window.

​
Accounts in Scope

By default, a rep receives the accounts they own or where they’re on the account team. Records that a rep can see only through the role hierarchy or sharing rules don’t sync. If User Reporting Hierarchy is set to Public Group (on the FieldKo Configuration tab, under Basic; stored in the User Hierarchy Base custom setting), accounts come from account sharing to the public groups the rep belongs to instead. These accounts are limited to the record types selected on the FieldKo Configuration tab, under Basic.

​
The Date Window and Call Cycles

Visits, tasks, survey answers, orders, ranging, notes, and Next Visit To Do’s sync only within a date window:
  • From: The first day of the previous month
  • To: The end of the rep’s active call cycle, or the end of next month, whichever is later
If a rep has no active call cycle that covers today, none of these records sync. No error appears, and the rep sees no visits. Check this first when a rep says their visits are missing. See Call Cycles.

​
Rules for Each Object

To narrow the records of a specific object, see Narrow Records with Duration of the Data to Be Fetched.

​
Records That Leave a Rep’s Scope

When a record is deleted in Salesforce, the app removes it from devices at the next sync, while the record is still in the Recycle Bin. Records that move out of a rep’s scope, for example when an account is reassigned, stay on the device until the rep runs Reset Sync.

​
How Many Records per Request

Sync fetches records in pages. Number of Records in the Sync Configurations custom setting sets the page size. It’s 999 after install.

​
Conflicts

If a rep edits a record offline and the same record changes in Salesforce before the rep syncs, the result depends on the object:
  • Objects with a Last Modified (FieldKo) field (visits, tasks, survey answers, orders, ranging, notes, incidents, pack-outs, accounts, and contacts): If the Salesforce version is newer, FieldKo keeps it and doesn’t apply the rep’s change.
  • Other objects: The rep’s change overwrites the fields they edited.

​
Change What Syncs

This part has the steps to change what reps get. For the rules these steps change, see How FieldKo Chooses What Syncs.

​
Narrow Records with Duration of the Data to Be Fetched

To control which records of an object sync, add a record to the Duration of the data to be fetched custom setting:
  1. From Setup, in the Quick Find box, enter Custom Settings, and then select Custom Settings.
  2. Next to Duration of the data to be fetched, click Manage.
  3. Click New.
  4. In Name, enter the object’s API name. Find it in Setup > Object Manager.
  5. Set the fields in the following table.
  6. Save your changes.
Objects listed here also follow the call cycle requirement in The Date Window and Call Cycles.

​
Add an Object to the App

Use these steps to make one of your own objects, or a supported standard object, available offline in the app:
1

Check That the Object Can Sync

It must be a custom object, or Account, Contact, Note, Event, Case, Asset, Task, or Opportunity.
2

Add It to Objects To Be Fetched

From Setup, in the Quick Find box, enter Custom Settings, and then select Custom Settings. Next to Objects To be Fetched, click Manage, and then click New.Fill in the record, and then save your changes:
  • Name: Enter the object’s API name. Find it in Setup > Object Manager. If it’s longer than 40 characters, enter it in Object Name instead.
  • Upsertion Order Value: Enter a number greater than 50.
  • Show In Menu: Select this to show the object in the app’s side menu.
  • Optional: Set Menu Label Override and List View Fields.
3

Make Sure It Isn't Excluded

Check that the object isn’t listed in Objects To Exclude.
4

Prepare Layouts and Access

Put the fields reps need on a page layout. Give reps object and field-level access.
5

Decide Which Records Sync

Check which records reps get under Rules for Each Object.Optional: To narrow the records, add a Duration of the data to be fetched record. See Narrow Records with Duration of the Data to Be Fetched.
6

Run the Metadata Collector

See Run the Metadata Collector.
7

Ask Reps to Reset Sync

Ask reps to run Reset Sync. The object appears after they reset.

​
Run the Metadata Collector

The Metadata Collector reads your objects, fields, layouts, record types, and profile layout assignments, and stores them for the app. Run it after you install FieldKo, and every time you change any of these.
Before you begin, make sure you have the FieldKo Native Permission Set and a remote site setting for your FieldKo Native Visualforce domain.

​
Collect Metadata

Collecting objects and layouts replaces all previously collected metadata. Run both collectors, and then ask reps to reset:
  1. From the App Launcher, find and select Metadata Collector.
  2. Click Collect Objects and Layouts Metadata. Wait for “Objects and Layouts Metadata stored successfully.”
  3. Click Collect Profiles Metadata. Wait for “Profiles Metadata stored successfully”.
  4. Ask reps to tap Sync, and then run Reset Sync.
    • Syncing first uploads their unsynced changes so they aren’t lost.

​
Metadata Collector Messages

​
Limit Which Profiles Are Collected

These are list custom settings. From Setup, in the Quick Find box, enter Custom Settings, select Custom Settings, and then click Manage next to the setting. Add one record per profile, with the profile name in Name. By default, the Metadata Collector also adds the child objects shown in your page layouts’ related lists. To stop this, in the Metadata Configurations custom setting, select Skip Child Objects Metadata on the Metadata Configuration record.

​
Choose the Layout Reps See

The app uses the page layout assigned to each rep’s profile and record type. To use a different layout in the app, add a FieldKo Layout Override custom metadata record. See Page Layouts.

​
See Also

Last modified on October 20, 2026