User Permissions Needed
Choose a Sandbox
Salesforce offers Developer, Developer Pro, Partial Copy, and Full sandboxes. Developer sandboxes copy your configuration but no data. Partial Copy sandboxes add a sample of data, and Full sandboxes copy all of it. Which types you have depends on your edition and contract. See Sandboxes: Staging Environments for Customizing and Testing in Salesforce Help. For FieldKo, test sync and reports in a sandbox with realistic data: accounts with owners, call cycles, and visits. In a Developer sandbox, load a small test set first. See Import and Update Data.Prepare a Sandbox After a Refresh
A new or refreshed sandbox has its own domain and its own collected metadata, so the app doesn’t work there until you complete these steps:1
Add the Sandbox's Remote Site Setting
The sandbox’s Visualforce domain for FieldKo Native is different from production. From the App Launcher, find and select Metadata Collector, and copy the domain from your browser’s address bar. Then add it as a remote site. See Remote Site Settings.
2
Run the Metadata Collector
Click Collect Objects and Layouts Metadata, and then Collect Profiles Metadata. See Run the Metadata Collector.
3
Check FieldKo Settings and Jobs
Check that FieldKo custom settings, such as Sync Configurations and Visit Configurations, have the values you expect. From Setup, in the Quick Find box, enter
Scheduled Jobs, and then select Scheduled Jobs, and schedule any FieldKo jobs you need to test. See Scheduled Jobs.4
Decide About Email
New and refreshed sandboxes send only system email, and Salesforce changes users’ email addresses so they don’t receive sandbox email. To test visit summary or order emails, update the test users’ email addresses and change Deliverability in Setup. Never send test emails to customers’ contacts.
5
Check Test Reps
Make sure each test rep is active, has the FieldKo permission sets, owns test accounts, and has an active call cycle that covers today.
6
Log In to the Sandbox from the App
On the app’s login page, use the login server picker to choose the sandbox server, or add your sandbox’s My Domain login URL, and then log in with the sandbox username. See Log In and Set Up the App.
Move Your Changes to Production
Build and test your own changes, such as fields, layouts, record types, validation rules, and flows, in the sandbox, and then deploy them:- Change sets move metadata between your production org and its sandboxes. See Change Sets in Salesforce Help.
- DevOps Center tracks changes as work items and moves them through a pipeline with source control. See DevOps Center in Salesforce Help.
- You can’t change FieldKo’s packaged components, such as its objects’ packaged fields, flows, and Apex. Deploy only your own changes.
- Custom setting values aren’t metadata. Most FieldKo settings are custom settings, so change sets don’t move their values. Re-enter them in production, or load them with Data Loader. Custom metadata records, such as FieldKo Layout Override and Visit Type, can be deployed.
- Rerun the Metadata Collector in production after you deploy layouts, fields, or record types, and then ask reps to tap Sync, and then run Reset Sync.
Upgrade the FieldKo Packages
FieldKo package upgrades don’t change your settings, but they can add fields, objects, and features that the app uses. Upgrade in a sandbox first:- Get the upgrade links from your FieldKo contact. Upgrade the FieldKo package first, and then the FieldKo Native package.
- In the sandbox, rerun the Metadata Collector, and then test your key flows: login, visits, surveys, orders, ranging, and your own automation.
- Review what’s new. The FieldKo Atlas release notes cover the app. For package changes, ask your FieldKo contact.
- Upgrade production, preferably outside reps’ working hours.
- Rerun the Metadata Collector in production.
- If layouts or fields changed, ask reps to tap Sync, and then run Reset Sync. Syncing first uploads their unsynced changes.
- Check that reps’ syncs succeed in Sync Details, and that reps run the app version you expect, using Mobile App Version on their Attendance records.