Transaction Objects Layout Editor Reference

This is the reference for the callouts, tabs, and buttons in the Transaction Objects layout editor.

Editor Layout Callouts

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 appears in the FieldFX Mobile App when the tablet is in landscape orientation.

Choose the correct tab to configure the layout for the desired orientation.

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

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.

See Geolocation Fields Note for more information about geolocation fields.

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 only 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.

For Transaction Object Layouts, there are four tabs:

  • Field Properties

  • Synced Fields

  • Cross Object Formula Fields

  • Mobile Lookup Filter

See Lookup Layouts for the two tabs shown on Lookup layouts.

5

Field Details Canvas

Shows the order of the fields in the layout. You can drag and drop fields to change their order.

6

Available Fields

The fields that can be dragged and dropped on the Details tab. Depending on the object chosen, the list of fields can be different.

7

New Blank Space and 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.

Unresolved include directive in modules/adminportal/pages/SyncProfMgr_TransObjLayoutReference.adoc - include::base:MobileRNApp:partial$FXM_FFX5240_GeolocFieldsColsnotshown.adoc[]

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.

A tile displays a maximum of five fields, in the order set under Selected Fields. The first field displays as the tile heading.

Back to Tile Tab callout

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.

Table tab

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

  • 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.

Unresolved include directive in modules/adminportal/pages/SyncProfMgr_TransObjLayoutReference.adoc - include::base:MobileRNApp:partial$FXM_FFX5240_GeolocFieldsColsnotshown.adoc[]

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, and User experience in lookups

The tabs 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

      With FX26R1, required fields are either sync-required (a field pulled in automatically because it’s referenced by a mobile filter, mobile rule, or Salesforce formula) or layout-required (an admin manually marks it required on the layout).

    • 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

When the Work Order module is enabled, the Override field on the Inventory Transaction object is always synced to the FieldFX Mobile App, regardless of whether it is added to the layout’s Synced Fields or Hidden tab. This field allows a mobile user to submit an inventory transaction that would otherwise fail on-hand-quantity validation.

  • 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.