User Permissions Needed
What You Can and Can’t Change
Managed packages protect the components that FieldKo needs to work. Exactly which attributes you can edit depends on the component type and your package version, so check in Setup before you plan a change.Customize Without Breaking the App
- Don’t rename or remove what FieldKo looks for. Keep the Visit and Task record types, and the status picklist values on visits and tasks, as installed. FieldKo uses them to move visits from Not Started to Completed.
- Don’t deactivate FieldKo’s own validation rules, flows, or triggers unless FieldKo Support asks you to.
- Keep required fields mobile-ready. A field that’s required on desktop but not on the rep’s layout makes records fail at sync.
- Keep your own automation bulk-safe. The app uploads reps’ changes in batches when they sync. A flow or trigger that fails for one record can stop others from saving. Test with several visits completed offline at once.
- Rerun the Metadata Collector in every org you change. Collected metadata is stored as records in each org, so deploying a layout to production doesn’t update it there. After each deployment, run the Metadata Collector in the target org and ask reps to run Reset Sync.
Naming Conventions
Clear names keep your fields apart from FieldKo’s, in Setup, reports, and the app:- Don’t give your fields the same label as a FieldKo field on the same object. Reps and report builders can’t tell them apart.
- Use a consistent label style and a short prefix in the field name for your company’s fields, so they sort together in Setup.
- Fill in Description on every field, flow, and validation rule: what it’s for, who asked for it, and the date.
- Name flows by object and purpose, such as
Visit - Notify Manager on Cancellation.
Document and Test Changes
Keep a change log, such as a shared spreadsheet, with each component you add or change, why, who owns it, and when it reached production. When you contact FieldKo Support, include the recent entries, because a recent customization is often the cause of a new sync error. Test every change in a sandbox that has the same FieldKo package versions as production, with a test rep on a real device:- Make the change in the sandbox.
- Rerun the Metadata Collector, and run Reset Sync as the test rep.
- Complete a visit offline, including the changed screens, and then sync.
- Check Sync Details for errors. See Sync Details.
- Deploy to production, and repeat step 2 there.
Some customizations, such as your own Apex triggers, need a Salesforce edition that supports them. If you’re not sure what your edition includes, check your Salesforce contract or ask your Salesforce account executive. See Licenses and What’s Included.