User Permissions Needed
Before You Begin
- Check which page layout each rep profile uses for the object and record type. Visits and tasks have a layout per status record type. See Record Pages, Layouts, and List Views.
- If the field is on one of your own objects, check that the object syncs. See Add an Object to the App.
- Make the change in a sandbox first if reps rely on the layout every day.
Add a Field to the App
Follow these steps for a new field, or for an existing field that reps can’t see:1
Create the Field
From Setup, open Object Manager, select the object, click Fields & Relationships, and then click New. Choose a supported field type. For field basics, see Create Custom Fields in Salesforce Help.
2
Give Reps Field Access
Grant Read access, and Edit access if reps fill it in, in a permission set that reps have. FieldKo’s packaged permission sets can’t be edited, so use your own permission set or permission set group. See Profiles, Permission Sets, and Permission Set Groups.The app never downloads a field that the rep can’t read, and skips fields the rep can’t edit when it uploads, without showing a message.
3
Add It to the Page Layout
Add the field to the page layout assigned to the reps’ profile for every record type they use. Set it to Read-Only or Required on the layout if you need to: the app follows both settings.
4
Run the Metadata Collector
From the App Launcher, find and select Metadata Collector. Click Collect Objects and Layouts Metadata, and then Collect Profiles Metadata. See Run the Metadata Collector.
5
Ask Reps to Reset Sync
Ask reps to tap Sync first, so their unsynced work uploads, and then run Reset Sync. The field appears after the reset.
Picklists, Record Types, and Dependencies
- New picklist values: Adding a value to a picklist is a field change. Add the value to each record type that should offer it, rerun the Metadata Collector, and ask reps to reset.
- Values by record type: When reps create or edit a record in the app’s record screens, the app offers only the values allowed for that record’s record type.
- Record types: When a rep creates a record of an object that has several record types available to them, the app asks them to choose one, and then shows that record type’s layout. Reps can’t change a record’s record type in the app.
- Dependent picklists: The app follows field dependencies. When a rep changes the controlling field, the app clears dependent values that are no longer valid. Put both fields on the layout.
Field Types the App Supports
The app shows and edits these field types on its record screens.
These field types don’t work as you might expect:
- Geolocation fields don’t appear on the app’s record screens.
- Encrypted text appears as plain text, not masked.
- Time and other types not in the table appear as a plain text box. Test them with a rep user before you rely on them.
What Doesn’t Show in the App
FieldKo’s own screens, such as surveys, ordering, and core ranging, have fixed fields or their own settings. Page layouts change the app’s record screens, not those screens. See Configuration Reference.