Edit a Sync Profile Manager Layout

You can edit and customize a Sync Profile Layout for Transaction Object Layouts or Lookup Layouts.

Layouts for Transactional Object, Lookup, and Global can be created in the FieldFX Sync Profile Manager admin tool; however, they are not currently functional. This feature is part of planned future enhancements and will be available in an upcoming release.

Transaction Objects Layout Editor Layout / Details tab

Transaction Objects Tab Editor callouts

Callout Name Description

1

Layout Title
Base Object

The name of the layout plus the object that the layout is based on.

2

Editor section
Tabs

These are tabs within the edit screen.

Tab Description

Details
(Default)

The canvas where you can design the layout by dragging and dropping fields into position. This is how the layout appear in the FieldFX Mobile App when the tablet is in landscape orientation.

Tile

This tab is where the tile is built that appears when the table is rotated to the portrait orientation.

Table

This tab is where the card/tile view used in certain list or summary screens is defined. Users utilize this to see a compact snapshot of a record.

Hidden

This tab includes fields that shouldn’t be displayed in any UI but are required for rules, filters, or automation.

3

Action Buttons

These buttons perform the following:

Button Description

Back

Returns to the list of layouts.

Import

You can import another record of the same type into the layout. The button is active when you have opened a layout.

Save

Saves any changes to the layout.

4

Field Detail Tabs

You can see the details for the selected field or where else the fields used on the layout are used.

Depending on the field selected, the properties shown may be different.

Transaction Object Layouts
has four tabs:		 Lookup Layouts
has two tabs:

  • Field Properties

  • Synced Fields

  • Cross Object Formula Fields

  • Mobile Lookup Filter

  • Field Properties

  • Synced Fields

6

Available Fields

The fields that can be dragged and dropped on the Details tab.

7

New Blank Space &
New Section
Buttons

Drag one or both of these onto the details pane to insert a blank space between fields or to group fields in a new section.

Editor Interface Layout

The interface when editing a Transaction Objects Layout has a drag-and-drop interface where you can build a layout by dragging fields over to a Details tab.

Edit Interface callouts
Callout Name Description

1

Layout name
Object based

The name of the layout and the object its based on.

2

Tabs

The edit interface has the following tabs:

Tab name Description

Details

This tab is the main canvas to build the layout.

Tile

This tab is where the tile is built that appears when the table is rotated to the portrait orientation.

Table

This tab is where the card/tile view used in certain list or summary screens is defined. Users utilize this to see a compact snapshot of a record.

Hidden

This tab includes fields that shouldn’t be displayed in any UI but are required for rules, filters, or automation.

3

Action Buttons

Use these action buttons:

Button Name Description

← Back

Click this button to return to the list of layouts.

Import

Click this button to import a sync profile.

Save

Click this button to save the changes to the layout.

4

Field Detail Tabs

You can see the details for the selected field or where else the fields used on the layout are used.

Depending on the field selected, the properties shown may be different.

For Transaction Object Layouts, there are four tabs:

  • Field Properties

  • Synced Fields

  • Cross Object Formula Fields

  • Mobile Lookup Filter

5

Layout Canvas

This shows the order of the fields in the layout.

6

Available Fields

This is a list of the fields that can be used on the layout. Depending on the Object chosen, the list of fields can be different.

7

New Blank Space
New Section
Buttons

Use these buttons to add blank space between fields or add a new section to group fields.

Tile Tab

Tile tab

The layout of this tab, used when the layout is shown in a portrait orientation, is basically the same as the Details tab except for:

  • No New Blank Space button

  • No New Section button

Only a total of five fields can be displayed.

Pick key fields you want to appear on each tile (title, sub-lines, badges, etc.) so users can scan and identify items quickly.

Limit the tiles to essential information to optimize the scroll performance on mobile.

If you want quicker at-a-glance comprehension for Mobile users, use tiles. Tiles enable the user to see essential information without opening each record.

Back to Tile Tab callout

Table Tab

Table tab

The layout of this tab, used to show items in a list view and grid view, is shown in a landscape orientation. This view allows the user to view and edit multiple records.

It is basically the same as the Details tab except for the:

  • No New Blank Space button

  • No New Section button

A maximum of 20 fields can be displayed.

You can choose which columns the mobile user sees and their order.

An improvement to the grid is a locked first column, alternating row colors, and a clearer active cell styling all for better user navigation during bulk edits.

Back to Table Tab callout

Hidden Tab

Hidden tab

This tab includes fields in the sync payload that should not display in any UI (detail, tile, or table). They are required however for rules, filters, or automation.

Mark supporting fields (IDs, flags, derived values) as hidden so they sync for logic/filters while staying out of the UI.

Keep the visible UI clean while ensuring background SOQL filters and other conditions remain fully functional.

If a field is needed for sync logic, calculations, or back‑office processes but adds noise or confusion if shown to end users, use this view.

Back to Hidden Tab Callout

Field Details Tabs

These tabs give admins granular control over:

  • Data Visibility

  • Sync Efficiency

  • Dynamic data presentation

  • User experience in lookups

are comprised of:

Tab Name Purpose Usage

Field Properties
(Editable)

Visibility and behavior of individual fields for transactional objects in the FieldFX Mobile App.

The specifics of the highlighted field (from the details tab) can change depending on the field. They are:

  • Label - Field Name

  • API Name - API Name

  • Type - varies depending on the field. Possible types are: picklist, reference, boolean (formula), boolean, string, double, datetime, currency

  • Behavior checkboxes:

    • Required - The field is required

    • Editable - The field can be edited

    • Readonly - The field is readonly

  • Reference To - An object this field refers to

  • NOTE - Optional information

  • Formula - The formula used in this field

  • Added From - where the field applies: layout, tile, table, hidden

Synced Fields
(Read Only)

The fields that are synced between Back Office and the mobile device.

They are critical to ensure mobile user have the needed data and not overload the device.

Example: You can sync "Job ID" and "Customer Name", but skip internal audit fields.

Here is a sample table:

This tab has two columns:

  • Name - The API Name or Label of each field currently synced for the lookup object. The fields can be added manually or automatically when the layout was created. The object’s metadata in Salesforce (FieldFX-managed objects) is the source which reflects the actual field name defined on the object.

  • Added By - This column is how the field was added to the layout. There are values of:

    • Default Layout - If the field was part of the base layout when the object was first configured

    • Manual - If an admin explicitly added the field using the drag-and-drop editor

    • Global Layout - If the field was propagated from a global layout and applied to multiple profiles

  • Select fields that need to sync for offline access

  • Exclude non-essential fields for improved performance and reduced sync time
Reference for Synced Fields Tab in Transaction Objects Layout

This table shows typical examples of fields synced for a Transaction Object Layout. The Name column lists the API names of transactional fields, and the Added By column indicates how each field was introduced into the layout.

Name Added By

FX5__Job__c

Default

FX5__Ticket__c

Manual

FX5__Quote__c

Global

FX5__Start_Date__c

Manual

FX5__End_Date__c

Default

FX5__Primary_Job_Contact__c

Global

FX5__AFE_Number__c

Manual

FX5__Site_Address__c

Default

FX5__Warehouse__c

Global

Cross Object Formula Fields
(Read Only)

Admins can create formula fields that pull data from related objects.

  • Define calculated fields that combine or reference data across objects (such as Jobs and Tickets).

  • These fields are useful for displaying aggregated or derived values without creating redundant fields in Salesforce.

  • These formulas are evaluated server-side and synced to mobile for display.

    Example: A formula that shows “Total Estimated Cost” by summing line items from related objects.

Mobile Lookup Filter
(Read Only)

This tab controls which records appear in lookup dialogs on the FieldFX Mobile App.

To see the filter, click on the lookup field.

The lookup field must be editable to have a Mobile filter.

  • Apply SOQL-based filters to limit lookup results to relevant records.

  • Improves usability by preventing users from scrolling through thousands of irrelevant options.

  • Used for objects like Accounts, Equipment, or Price Books.

    Example: Filter Accounts by region so a field tech only sees customers in their territory.

Lookup Layouts Editor

Lookup Layouts Edit Callouts
Callout Name Description

1

Layout Title
Base Object

The name of the layout plus the object that the layout is based on.

2

Tabs

There are 2 tabs in the Edit screen:

Tab Description

Layout

This tab shows the fields up to a maximum of 10.

Hidden

This tab defines which fields shouldn’t appear in the user interface but are important for business rules, filters, and automation logic. These fields remain part of the sync profile so calculations, workflows, or conditional logic can correctly run, even though the end user never sees them.

3

Action buttons

The Back button returns to the list of lookup layouts while the Save button saves any changes to the open layout.

4

Available Fields

The list of available fields that can be used on a lookup layout are more extensive than for a transaction object layout and can vary depending on the object chosen at layout creation.

5

Fields list

You can drag up to 10 fields maximum and arrange them in any order.

6

Field Properties
and
Selected Fields (Layout)

They can vary depending on the field.

Field Properties

Show properties of the field you highlighted. Select a field to see the properties.

Selected Fields (Layout)

Shows if the fields are available on a layout, table, or a tile. The field can appear on one or all of them.

Layout Tab

This tab is the design canvas where you can configure how fields appear in the FieldFX Mobile App. Drag a field from the Available Fields list over to the canvas and arrange them for the lookup object. The defined layout determines what users see when interacting with lookup records such as Accounts and Equipment in the mobile app. Different orientations and views (landscape, tile, table) are supported. The primary purpose is a visible UI design for mobile users.

Hidden Tab

This tab defines which fields shouldn’t appear in the user interface but are important for business rules, filters, and automation logic. These fields remain part of the sync profile so calculations, workflows, or conditional logic can correctly run, even though the end user never sees them.

File Details Tabs

Field Properties tab Synced Fields tab

Field Properties tab

Synced Fields tab

These tabs provide admins are comprised of:

Tab Name Purpose Usage

Field Properties
(Editable)

Visibility and behavior of individual fields for transactional objects in the FieldFX Mobile App.

The specifics of the highlighted field (from the details tab) can change depending on the field. They are:

  • Label - Field Name

  • API Name - API Name

  • Type - varies depending on the field. Possible types are: picklist, reference, boolean (formula), boolean, string, double, datetime, currency

  • Behavior checkboxes:

    • Required - The field is required

    • Editable - The field can be edited

    • Readonly - The field is readonly

  • Reference To - An object this field refers to

  • NOTE - Optional information

  • Formula - The formula used in this field

  • Added From - where the field applies: layout, tile, table, hidden

Synced Fields
(Read Only)

The fields that are synced between Back Office and the mobile device.

They are critical to ensure mobile user have the needed data and not overload the device.

Example: You can sync "Job ID" and "Customer Name", but skip internal audit fields.

This tab has two columns:

  • Name - The API Name or Label of each field currently synced for the lookup object. The fields can be added manually or automatically when the layout was created. The object’s metadata in Salesforce (FieldFX-managed objects) is the source which reflects the actual field name defined on the object.

  • Added By - This column is how the field was added to the layout. There are values of:

    • Default Layout - If the field was part of the base layout when the object was first configured

    • Manual - If an admin explicitly added the field using the drag-and-drop editor

    • Global Layout - If the field was propagated from a global layout and applied to multiple profiles

  • Select fields that need to sync for offline access

  • Exclude non-essential fields for improved performance and reduced sync time

Synced Fields tab within a Sync Profile Manager Lookup Layout. The Name column lists the API names of synced fields, and the Added By column indicates how each field was introduced into the layout (Default, Manual, or Global):

Name Added By

FX5__Job__c

Manual

FX5__Customer__c

Default

FX5__Status__c

Global

FX5__Start_Date__c

Manual

FX5__End_Date__c

Default

FX5__Location__c

Global

Global Layouts

This is a reusable layout (for either Transaction Objects or Lookup Layouts) the admin creates once and can assign to multiple sync profiles. The key benefit is when the admin edits the global layout (field positions in Layout, or rule-only fields in Hidden), the changes propagate to every sync profiles using it. There is no rework per sync profile.

Transaction Object Layouts

When you edit a global layout (such as rearranging fields on the Details tab or add rule-only fields to Hidden), those changes propagate automatically to every sync profile using that layout. This eliminates repetitive edits and ensures consistency across teams.

Global layout take precedence: If a sync profile references a global layout, any updates to that global layout apply immediately.

Profile-specific layout overrides global: If you assign a custom layout to a profile, that layout takes precedence for that profile. Best practice: Use global layouts for standardization and minimize profile-specific layouts to reduce maintenance overhead.

Lookup Layouts

Each sync profile has sections for Transaction Objects and Lookup Objects. For each object, you select which layout it will use—either:

  • a global layout (shared across profiles), or

  • a profile‑specific layout (unique to that profile, if you decide to diverge)

Once assigned, the Layout tab determines the fields and arrangement the mobile user will see; the Hidden tab carries non‑UI fields your rules, filters, and automations depend on. Both tabs are honored by the mobile app runtime.

The FieldFX Mobile App renders these lookup layouts directly, ensuring consistency between Back Office and Mobile.

Global vs Profile-specific

Global layout ➜ many profiles: Any edit to a global layout (on Layout or Hidden) is centralized and automatically reflected everywhere that layout is assigned. This is the fastest way to keep multiple teams aligned.

Profile‑specific layout: If a profile needs a different arrangement or set of hidden fields, you can create (or clone) a layout and assign that variant to just that profile. That profile then follows its assigned layout rather than the global one.

Assignment determines precedence. The layout assigned to the profile/object combination is the one the mobile user sees; a global layout only applies where it is assigned.

Best Practices:

  • Default to global for core objects (Accounts, Equipment, Price Books) to minimize maintenance

  • Keep calculation/flag fields in Hidden (e.g., region, entitlement flags, crew membership) so filters and automations are reliable without cluttering the UI

  • Use profile‑specific layouts sparingly—only when a team truly needs a different experience; otherwise rely on global layouts for consistency and upgrade resilience

  • Confirm admins have permissions to the Mobile Object Layout custom object and related entities; layouts won’t assign or propagate correctly without the required access

Edit a Transaction Objects Layout

You can edit a Transaction Objects layout once its open.

These objects are used to store operational data that users interact with on a daily basis and users make use of them when they need to view, edit, or create that specific type of data on mobile.

  1. On the Transaction Objects Layout tab, open a layout to begin editing it.

  2. Drag new fields onto the Details tab.

  3. You can also drag and move fields on the Details canvas to a new location.

  4. If you want to add space between fields, drag the New Blank Space button onto the canvas and position it before or after the desired field.

  5. If you want to group fields in a new section,

    1. Drag it to a blank space on canvas.

    2. Enter the name of the section in the New Section modal under the Section Name.

    3. Click Confirm to save the section name.

    4. Click and drag the desired field block underneath the new section.

      You will see a green line indicating a valid location.

  6. Click Save button.

  7. To configure the Tile Tab:

    You can have up to 5 fields maximum. Only fields with a move icon can be dragged to the canvas.

    1. Drag the field from the Available Fields section to a blank space on canvas.

  8. To configure the Table Tab:

    You can have up to 20 fields maximum. Only fields with a move icon can be dragged to the canvas.

    1. Drag the field from the Available Fields section to a blank space on canvas.

  9. To configure the Hidden Tab:

    Only fields with a move icon can be dragged to the canvas.

    1. Drag the field from the Available Fields section to a blank space on canvas.

Edit a Lookup Layout

  1. On the Lookup Layouts tab, click on the layout you want to edit.

  2. Use the Move icon next to the field in the Available Fields over to the Layout canvas.

    You can add up to the 10 fields.

  3. Click on the field to see the field’s properties in the Field Properties tab.

  4. To remove the field from the layout,

    • Click the X next to the field or

    • In the Field Properties, click the red Remove Field From Layout.

  5. Click Save button.

Import a Layout

You can import an existing layout into a new transaction object or lookup layout. Unless you want to overwrite an existing layout, you should create a blank layout then import an existing layout.

Key Benefits

  • There is a faster setup with reusing existing layouts

  • The UI and rules are consistent across multiple profiles

  • There is reduced admin overhead when global layouts are updated

Potential Issues

Issue Description

Permission-Related Problems

  • Insufficient Object/Field Access
    An admin may lack CRUD access to all relevant Salesforce objects and fields and the imported layouts may be incomplete. Missing permissions can cause certain fields not to sync even if they are in the layout.

  • Custom Object Access
    Lack of access to the Mobile Object Layout custom object (FX5__ffxMobile_Object_Layout__c) prevents proper layout management and may block imports

Layout Refresh and Field Behavior Issues

  • Delayed Refresh
    The layout may not refresh immediately after importing which could lead to confusion about the success of the import.

  • Field Properties Not Saving
    Some lookup layouts may fail to retain their required or read-only settings after import. This could lead to inconsistencies between the intended and actual layout behavior.

eForms and UI Display Problems

Imported layouts sometimes do not display correctly in both the main page and mobile app, especially when linked to eForms. This can disrupt workflows that rely on those forms.

Global Layout Propagation Risks

There could be unintended changes across profiles if the imported layout is set as a global layout, where any subsequent edits propagate across all profiles using that layout. Without careful planning, this can introduce unintended changes to multiple user profiles.

Dependency on Back-Office Configuration

Imported layouts rely on back-office configurations (field requirements, read-only settings). If these configurations are incorrect or outdated, the imported layout will carry those issues forward.

Best Practices

  • You should verify admin permissions before importing.

  • Confirm field behaviors and refresh the layout after import.

  • Validate back-office configurations prior to import.

  • Test your eForms and UI display in both desktop and mobile environments.

  • Use global layouts cautiously and document changes before propagation.

Process

  1. Open a Transaction Object Layout.

  2. Once opened, click Import to open the Import modal.

    Only when an existing layout is opened is the Import button available. The available layouts depend on the object type selected when you opened the layout.

  3. At the Import modal, select the layout to import.

    This will bring in another record of the same type into the current layout.

  4. Verify the field properties of the layout.

  5. Save changes.

Recommended Reading

For more information, see:

FieldFX Documentation Salesforce Documentation

  • n/a