User Permissions Needed
Choose a Tool
For details, see Choose a Method for Importing Data in Salesforce Help and the Data Loader Guide. Import tools list FieldKo objects and fields by API name; you can match them to the labels on this page in Setup > Object Manager.
Before You Begin
- Test in a sandbox first. FieldKo’s triggers and flows run on every record you load, and some loads, like visits, depend on call cycles and settings. Load a sample in a sandbox, sync a test rep, and check what the rep sees. See Manage Releases.
- Add external ID fields. FieldKo doesn’t include external ID fields on accounts, products, or price books. Add your own, such as ERP Account Number, so you can upsert and link records without Salesforce IDs. See Use External IDs and Upsert.
- Turn on your bypass. Run the load as a user with your automation bypass permission so your own flows, such as manager alerts, don’t fire. See Bypass Your Flows for Integration Users.
- Back up first. Before you update or delete existing records, export them. See Export FieldKo Data and Photos.
Load in This Order
Load parents before the records that look them up. Work through the objects in this order:
For what each object does, see Set Up Products, Ordering, and Ranging and FieldKo Data Model.
Accounts
Accounts decide which reps get which stores, so check these fields carefully:- Record type: If you leave it blank, FieldKo sets the default record type for your profile, or Store if there’s none. Only accounts with a record type selected in Account Record Types for Visit Planning are used for visit planning.
- Owner and account team: By default, a rep gets the accounts they own or where they’re on the account team. See Accounts in Scope.
- Coordinates: The app compares the rep’s location with the account’s coordinates at check-in. Import shipping latitude and longitude if you have them. Otherwise, fill them in afterward. See Where Account Coordinates Come From.
Call Cycles
Call cycles have strict rules: they must cover the fiscal year without gaps, and you can’t change their dates or rep after you save. Create them on the Call Cycles tab, or scheduleCallCycleBatchscheduler, instead of importing them. See Call Cycles.
Visits
When you import visits, FieldKo checks each one as if you’d created it in Salesforce. A visit without an account, a sales representative, or an active call cycle that covers its date fails with the messages in Visit Rules Enforced by Salesforce. FieldKo sets each visit’s owner to its sales representative. For most plans, it’s faster and safer to create visits with field campaigns or recurring visits than to import them.After You Load
- Check a sample of records in Salesforce, and fix any rows that failed. Your tool’s error file shows each failed row with its message.
- Ask a test rep to sync, and check that the accounts, prices, and visits appear in the app.
- If you moved accounts between reps, ask the reps who lost accounts to run Reset Sync. Records that move out of a rep’s scope stay on the device until they reset.
To retire products or price books, deactivate them instead of deleting them. Deleting a product also deletes its price book entries, and breaks the links from historical orders and ranging. See Keep Data Clean.