Import a Layout

At present, you can’t 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.

Lookup Layouts are supported for importing an existing layout through this process. When a Lookup Layout is first created, FieldFX automatically copies the associated object’s Salesforce search layout as the starting point, but there is no button or process to reset or re-import that layout afterward. See Layout Tab for more information.

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

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.

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

Open a Transaction Object Layout.
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.
At the Import modal, select the layout to import.

This will bring in another record of the same type into the current layout.
Verify the field properties of the layout.
Save changes.