User Permissions Needed
Record Types That FieldKo Installs
Because visits and tasks change record type as they progress, each status can have its own page layout. Use this to show reps the right fields at the right time: planning fields on Not Started, task and photo fields on In Progress, and a read-only summary on Completed.
You can add your own record types to objects such as Account, Contact, or your own objects. Don’t add your own Visit or Task record types to tell kinds of visits apart, because FieldKo replaces the record type when the status changes. Use visit types or a custom field instead.
If you add account record types, select the ones reps plan visits for in Account Record Types for Visit Planning on the FieldKo Configuration tab, under Basic.
How the App Picks a Layout
For each record, the app shows the page layout assigned to the rep’s profile for the record’s record type. Records with no record type use the object’s master layout assignment. A FieldKo Layout Override record can replace the layout for some profiles or record types. See Page Layouts. After you change record types or layout assignments, rerun the Metadata Collector and ask reps to run Reset Sync. See Add Fields and Picklists to the Mobile App.How Validation Rules Affect Reps
Reps work offline, so Salesforce doesn’t see a rep’s changes until the app syncs. Validation rules, required fields, and triggers all run then. When a rule fails:- The record doesn’t save in Salesforce. The rest of the sync continues, and the sync finishes as Partial Sync.
- The rep sees the record under Sync History > ISSUES, with your rule’s error message.
- An Error Information sync detail record shows
FIELD_CUSTOM_VALIDATION_EXCEPTIONand the message. See Records Fail to Upload.
Write Mobile-Friendly Validation Rules
Use these patterns for rules on objects that reps change in the app:- Only require fields that are on the rep’s layout. If a rule needs a field the rep can’t see or edit in the app, the rep can’t fix the record. Add the field to the layout for every record type the rule applies to, and mark it Required on the layout so the app checks it before the rep saves.
- Exempt mobile users with a custom permission. Create a custom permission, such as
Bypass Desktop Validation, add it to a permission set for reps, and addNOT($Permission.Bypass_Desktop_Validation)to the rule’s formula. Enforce the rule for desktop users only. See Custom Permissions in Salesforce Help. - Don’t block status changes. Avoid rules that stop a visit from moving to In Progress, Completed, or Cancelled. If a check-out fails at sync, the visit stays open in Salesforce and reports show it as missed.
- Fix data later instead of rejecting it. For data quality checks, consider a flow or report that flags the record for a manager instead of a rule that rejects the rep’s work. See Keep Data Clean.
- Test with a rep user. In a sandbox, make the change in the app offline as a test rep, sync, and check Sync Details for errors before you activate the rule in production.