FXL Deep Copy
Introduction
To create copies of a record with any related or child records, you can add the Deep Copy Lightning Component to any custom object. The Deep Copy Lightning Component feature is available for Lightning pages in FieldFX Back Office. Use Deep Copy to add a new record by copying an existing record and its related items.
For the latest updates, see FX Lightning Package Release Notes.
|
Copied records and all of the related or child records are locked during the copy process until the copy completes. This includes both the items being copied from and the new records being copied to. |
|
Deep Copy is a Lightning Component. This component expands on the functionality of the Deep Copy feature, but only works in Lightning Experience. FXL Deep Copy is included in the Base Managed Package and does not require installation of the separate Lightning Managed Package. |
You can add a new job by copying an existing job and its tickets, ticket items, and scheduled crew.
|
To use the FieldFX Lightning package starting with version 1.225, you must use the FieldFX Managed Package version 1.529 or higher. To find the version numbers you have installed, see Check Version Number for FieldFX Managed Package and FieldFX Lightning Managed Package. |
Key Features
|
You can use this to copy a selected record and its related child items, including children of the child items. Doing this ensures that all associated data is replicated in the new record. |
|
By default, records are copied asynchronously, meaning one record at a time period this approach helps manage system performance during the duplication process. |
|
Users can exclude specific fields from being copied by adding them to a clone blackout fields field set. Fields such as ID, external ID, status, sync ID, tracking number, auto number, and formula are not copied by default. |
|
This mode allows users to preview the data that will be copied without actually performing the duplication. It’s useful to her testing and troubleshooting. |
|
Users can apply filters to exclude certain records from being copied. For example, to avoid copying archive items, a filter can be set to include only non-archived records. |
-
Saves time by eliminating repetitive data entry
-
Reduces the chance of errors or omissions when creating similar records
-
Ensures consistency in data structure and related items
Best Practices
-
Permissions
Ensure that users have the necessary sharing access and permissions for all records they need to copy. -
Testing
Test the deep copy functionality in a sandbox environment before deploying it to production. -
Avoid Duplicates
Be cautious with the self-referencing parent slash child relationships, as the FXL deep copy component supports up to two levels of records.
Prerequisites
To set up or use the Deep Copy feature:
| Required Licenses | Required Permissions | Before continuing, complete these tasks |
||||
|---|---|---|---|---|---|---|
|
|
Performance of Deep Copy depends on various factors including, but not limited to, the number of
|
Common Use Cases
FXL Deep Copy can be used in these common cases:
| Use Case | Description | Example |
|---|---|---|
Creating Similar |
When a new job or work order has similar requirements to an existing one, FXL Deep Copy can replicate the record and its associated tickets, line items, and other details |
A field service technician needs to create a new work order for a repeat service at the same location with minor modifications. |
Recurring Projects |
For organizations handling recurring projects, copying a base template with pre-configured settings saves time and ensures consistency. |
A company creates annual maintenance contracts that include standard terms, tasks, and materials. |
Streamlining |
Sales teams can quickly duplicate an existing quote or proposal to use as a starting point for a new client. |
A salesperson duplicates a proposal for a new client who requires the same configuration as an existing customer. |
Training |
Teams can use a master project or template that includes all necessary fields, child records, and associated tasks, and then copy it for new projects. |
A construction company uses a project template with predefined tasks, resources, and schedules. |
Replicating |
Businesses can replicate multi-level data structures to accommodate complex workflows without manually creating each layer. |
A project manager copies a parent record (like a service call) with multiple nested records (like tasks, subtasks, and dependencies). |
Correcting |
If a record needs to be recreated due to errors but must retain most of the original data, Deep Copy ensures this can be done quickly. |
A dispatcher recreates a job ticket that was incorrectly synced with a minor adjustment. |
Archiving |
Teams can duplicate records for archiving purposes while continuing to work on the active version. |
An engineer saves a copy of a completed job ticket for historical reference before creating a new one for follow-up work. |
Handling |
When slight variations are required in a standard process, users can duplicate and then modify only the necessary details. |
A customer orders a slightly modified version of a previous job with updated specifications. |
Managing |
Companies handling seasonal work, like winterizing equipment, can copy previous records for similar seasonal tasks. |
A landscaping company duplicates service orders for routine seasonal maintenance. |
Step-by-Step Guides
| Before the FXL Deep Copy component can be used, you must set it up on the record page. |