Gantt LWC - Save As (Clone) Function

Last Modified On: July 10, 2026

Save As Function Overview

The Save As function provides an alternative way to create a new project by cloning an existing project or project template. Instead of creating a project from scratch, users can quickly create a copy while retaining existing project tasks, settings, and related information.
 

This functionality helps streamline project creation by allowing users to reuse existing project structures, reducing the time and effort required to manually recreate project details.
 

The Save As function can be used to clone:

• Existing Projects
• Project Templates

Please Note:
This help article has been updated to include support for the new features and enhancements introduced in the Inspire Planner July 2026 Major Release, which will be available in Production environments on August 11, 2026.

Create a New Project using Save As

To create a new project using the Save As function, first open the project or project template that you want to copy. If the project contains any unsaved changes, save the project before proceeding with the Save As function.
 

Once the project is saved, click the Save As icon from the Project Toolbar to begin creating a new project.

When using the Save As function, you can define which project information should be copied from the source project to the new project. The available options allow you to control what data, assignments, and related records are carried over.

• Name
  Enter the name of the new project.
   
• Description (Optional)
  Enter a brief description of the new project.
   
• Include Task Assignment
  When set to TRUE, task assignments from the source project are copied to the new project. This includes copying the project team records and creating the related Salesforce Tasks.
  
  Note:
  If the source project contains tasks assigned to inactive Salesforce users, those assignments are not copied.
  
  If Add as Collaborator is set to TRUE on a Salesforce User project team record, the related Collaborator records are also automatically created in the new project.
   
• Include Attachments
  When set to TRUE, all files shared within Project Task Chatter are copied to the new project.
   
• Include Baseline Dates
  When set to TRUE, the Project Task baseline information is copied to the new project, including:

  • Start Baseline Date

  • Finish Baseline Date

  • Duration Baseline

• Include Risks & Issues
  When set to TRUE, related Risk and Issue records from the source project are copied to the new project.
   

• Include Change Requests
  When set to TRUE, related Change Request records from the source project are copied to the new project.
   

• Include Other Custom Objects
  When set to TRUE, related records from supported custom objects associated with the Project are copied to the new project.
   

• Default Task Status
  Allows you to specify the default status that will be applied to all project tasks in the new project.

  • When a Default Task Status is Selected
    If a default task status is set, all project tasks in the new project will use the selected status.
    
    For example, if the default task status is set to Not Started:

    • All project tasks will be set to Not Started.

    • Completed checklist items will be reset to Open.

    • The Actual Start Date and Actual Finish Date fields will be cleared.
      ​​​​​​​

  • When No Default Task Status is Selected
    If no default task status is selected, each project task will retain the status from the original project.
    
    The following information is preserved:

    • Task statuses

    • Checklist item statuses

    • Actual Start Dates

    • Actual Finish Dates

When you have finished configuring the Save As options, click Save As to create the new project or project template.
 

The page will refresh, and you will be redirected to the newly created project or project template.

Save As Considerations

When cloning a project, the new project inherits the settings from the source project, including:

• Project time zone
• Non-working days

In addition, any checklist items associated with project tasks are copied to the new project.

Best Practices

After creating a new project or project template using the Save As function, it is recommended that you review the copied information to ensure it is still applicable to the new project or template.
 

Before beginning work, review and update the following areas as needed:

• Project Settings – Verify that the project settings inherited from the source project are appropriate for the new project. Update any settings that may differ based on the new project requirements.
• Non-working Days – Review the inherited non-working days and confirm they accurately reflect the schedule and availability for the new project. Add, remove, or update non-working days as necessary.
• Checklist Items – Review any checklist items associated with project tasks to ensure they are still relevant for the new project. Update, add, or remove checklist items as needed.
• Project Team Members and Collaborator Records – If task assignments were copied, review the project team members and collaborator records to ensure the appropriate users are assigned to the new project. Update assignments and collaborator access where necessary.
• Baseline Dates – If baseline dates were copied, review the project task baseline information to ensure the baseline dates and durations are still applicable to the new project schedule.
• Risks, Issues, and Change Requests – If these records were copied, review the inherited records to confirm they are relevant to the new project. Update or remove any records that do not apply.
• Related Custom Object Records – If related records from custom objects were copied, review the inherited records to ensure they are still applicable and accurately associated with the new project.
• Project and Task Attachments – If attachments were copied, review the files attached to the project and project tasks to confirm they are still relevant and required for the new project.
  ​​​​​​​

Reviewing these settings ensures that the new project is configured correctly and that the project schedule accurately reflects the requirements of the new project.