Quasar (v1.47) | Upgrade Instructions | December 2025

Quasar (v1.47) | Upgrade Instructions | December 2025

Our upgrade instructions provide guidance on new features that require manual updates in order not to conflict with any org-specific customization. Detailed information on Set-up, Configuration and Feature Information can be found through links on the Release Notes.
Contact support@verasolutions.org to share feedback.

Please note that the previous release Phoenix is v1.45 and Quasar is v1.47.
A version in between was not released.

Upgrading Amp Impact to Quasar - (v1.47)

Note:  
A Salesforce environment with Amp installed can be directly upgraded to the latest version of Amp as long as the current version is v1.17.1 or later. If the version of Amp Impact is an earlier version, you must first upgrade to v1.17.1 before upgrading to v1.47 (Quasar). When upgrading to this version and skipping previous upgrades, please be sure to follow the Upgrade Instructions for every intermediate release as well to ensure the app continues working as expected.

  1. To upgrade to the latest release of Amp Impact, log into your Sandbox environment and use the installation link.

    1. Vera Employees can navigate to this page to access the link.

    2. Partners & customers, please get in touch with your Vera point of contact to access the link.

  2. Information will be displayed confirming that you have an earlier version installed and it can be upgraded while preserving existing data. 

  3. Select which users you wish to install the package for (learn more here). 

  4. Click "Upgrade".

  5. Refer to the release notes document and learn about the new features and bug fixes for this release. 

  6. After reviewing the release notes, follow the steps outlined below. 

  7. Perform your current use cases in the sandbox and if you are using any of the new features from this release, ensure that they are operating as expected.

  8. When you are ready to deploy to Production, use this installation link.

  9. Update any changes you make, for example to custom settings, in Production as these will not "carry over" from your sandbox. 

Note: 
If My Domain has already been set up, replace “test” or “login” in the installation links with the specific domain appended by .my. for the org. See below for an example of a customized installation link: https://customdomain.my.salesforce.com/packaging/installPackage.apexp?p0=04t4o000002FIf5&isdtp=p1

If you upgrade Amp Impact, records of objects within that package will be updated. If custom validation rules have been created on those objects, the upgrade will fail if the records on those objects do not comply with those custom validation rules.

Packaging Changes

Certain changes to the configuration will be automatically updated on the installation of the upgrade, while others will need to be manually updated (in order not to conflict with any org-specific customization). For full details on what Salesforce supports when upgrading managed packages, refer to the Editing Components and Attributes After Installation and Special Behavior of Components in Packages pages.

Note: The table below details which types of configuration changes need to be made manually in this release, and if so, also include an example of where to change them. Additionally, the table also displays examples of some automatic changes that will occur when the package is upgraded.

Change

Automatic Update?

Manual Update Location

Example from Quasar (v1.47) Release

Change

Automatic Update?

Manual Update Location

Example from Quasar (v1.47) Release

New field

Yes

N/A

New field ampi__xx_Baseline_NumDen__c has been added to ampi__Project_Indicator__c and ampi__Indicator__c

New field

Yes

N/A

New field ampi__xx_Planned_Due_Date__c has been added to ampi__Activity__c

New field

Yes

N/A

New field ampi__xx_Profile_Name__c has been added to User object

New Custom Label

Yes

N/A

New Custom Label DOWNLOAD_SUBMISSION has been introduced.

Updated Custom Label

Yes

N/A

The value of the custom label - TARGET_NOT_DISAGGREGATED_POPUP_INFO has been changed

New Platform Event

Yes

N/A

New Platform Event Submission_Refresh__e was introduced.

The following fields were included in the Platform Event:

  • ampi__Date_and_Time__c

  • ampi__Message__c

  • ampi__Question_Ids__c

  • ampi__User_Details__c

Update Profiles and Custom Permission Sets for New Objects and Fields

While permission sets in the package are automatically updated to provide access to these new fields, profiles and custom permission sets must be manually updated to include these new artifacts if the relevant user(s) requires access to them. 

Refer to the Packaging Changes section in the release notes to determine which objects and fields need to be added to any custom profiles or permission sets. 

Upgrade steps to use Numerator/Denominator breakdown for Baseline

The following upgrade steps are relevant to organizations that aim to track Numerator and Denominator values for Baseline:

Add “Track Numerator Denominator for Baselines” field to the “Edit Project Indicator Popup” Field Set

  1. Navigate to Object Manager

  2. Navigate to the “Project Indicator”(ampi__Project_Indicator__c) object and click on it

  3. Navigate to Field Sets

  4. Click on “Edit Project Indicator Popup”(ampi__EDIT_PROJECT_INDICATOR_POPUP)

  5. Add the “Track Numerator Denominator for Baselines” (ampi__xx_Baseline_NumDen__c) to the Field Set

  6. Click “Save”. 

Add “Track Numerator Denominator for Baselines” field to the “Add New Project Indicator Popup” Field Set

  1. Navigate to Object Manager

  2. Navigate to the “ Indicator”(ampi__Indicator__c) object and click on it

  3. Navigate to Field Sets

  4. Click on “Add New Project Indicator Popup”(ampi__ADD_NEW_INDICATOR_POPUP)

  5. Add the “Track Numerator Denominator for Baselines” (ampi__xx_Baseline_NumDen__c) to the Field Set

  6. Click “Save”

Add the “Track Numerator Denominator for Baselines” field to the Page Layout of Indicator and Project Indicator Objects (Optional)

You can add the “Track Numerator Denominator for Baselines” field to the page layouts of the Project Indicator(ampi__Project_Indicator__c) and Indicator (ampi__Indicator__c) objects by following the steps mentioned below:

  1. Navigate to Object Manager

  2. Navigate to the “Project Indicator” object (ampi__Project_Indicator__c) and click on it

  3. Navigate to “Page Layout” and click on “Project Indicator Layout”

  4. Drag the “Track Numerator Denominator for Baselines” field to the Project Indicator Detail section

  5. Repeat the same for the Indicator (ampi__Indicator__c) object if needed

     

Upgrade steps to use Baseline for Milestone Type Activities

The following upgrade steps are relevant to organisations that aim to track Baselines for Milestone Activities:

Add “Planned Due Date” field to the “CREATE_EDIT_MILESTONE_POPUP” Field Set

  1. Navigate to Object Manager

  2. Navigate to the “Activity” (ampi__Activity__c) object and click on it

  3. Navigate to Field Sets

  4. Click on “CREATE_EDIT_MILESTONE_POPUP” (ampi__CREATE_EDIT_MILESTONE_POPUP)

  5. Add the “Planned Due Date” (ampi__xx_Planned_Due_Date__c) to the Field Set

Add the “Planned Due Date” field to the Activity Page Layout (Optional)

  1. Navigate to Object Manager

  2. Navigate to the “Activity” (ampi__Activity__c) object and click on it

  3. Navigate to “Page Layout” and click on “Activity Layout”

  4. Drag the “Planned Due Date” field to the Activity Detail section

Upgrade steps to use enhancements to Financials LWC excel templates

The following upgrade steps are relevant to organisations that aim to use upload/download excel templates on Planning and Reporting LWCs

Remove the field “Planned Cost per Unit” from the “Planning Excel Attribute Columns” field set

  1. Navigate to Object Manager

  2. Navigate to the “Financial” (ampi__Financial__c) object and click on it

  3. Navigate to Field Sets

  4. Click on “Planning Excel Attribute Columns” (ampi__PLAN_EXCEL_ATTRIBUTE_COLUMNS)

  5. Remove the “Planned Cost per Unit” (ampi__Cost_per_Unit__c) from the Field Set

  6. Click “Save”

Add “Planned Cost per Unit” and “FTE%” fields to the “Budget Planning Period” field set

  1. Navigate to Object Manager

  2. Navigate to the “Financial” (ampi__Financial__c) object and click on it

  3. Navigate to Field Sets

  4. Click on “Budget Planning Period” (ampi__BUDGETPLANNING_PERIODIC_COLUMNS)

  5. Add these fields to the Field Set:

    1. “Planned Cost per Unit” (ampi__Cost_per_Unit__c)

    2. “FTE %” (ampi__FTE_Percent__c)

  6. Click “Save”

Change the order of fields in the “Budget Planning Period” field set

  1. Navigate to Object Manager

  2. Navigate to the “Financial” (ampi__Financial__c) object and click on it

  3. Navigate to Field Sets

  4. Click on “Budget Planning Period” (ampi__BUDGETPLANNING_PERIODIC_COLUMNS)

  5. Rearrange the fields in the field set to match this order:

    1. FTE %

    2. Planned Cost per Unit

    3. Planned Quantity

    4. Amount Planned

Remove the field “Actual Cost per Unit” from the “Reporting Excel Attribute Columns” field set

  1. Navigate to Object Manager

  2. Navigate to the “Financial” (ampi__Financial__c) object and click on it

  3. Navigate to Field Sets

  4. Click on “Reporting Excel Attribute Columns” (ampi__REPORT_EXCEL_ATTRIBUTE_COLUMNS)

  5. Remove the “Actual Cost per Unit” (ampi__Actual_Cost_per_Unit__c) from the Field Set

  6. Click “Save”

Add “Actual Cost Per Unit”, “FTE%”, and “Comments” fields to the “Budget Reporting Period” field set

  1. Navigate to Object Manager

  2. Navigate to the “Financial” (ampi__Financial__c) object and click on it

  3. Navigate to Field Sets

  4. Click on “Budget Reporting Period” (ampi__BUDGETREPORTING_PERIODIC_COLUMNS)

  5. Add these fields to the Field Set:

    1. “Actual Cost Per Unit” (ampi__Actual_Cost_per_Unit__c)

    2. “FTE %” (ampi__FTE_Percent__c)

    3. “Comments” (ampi__xx_Comments__c)

  6. Click “Save”

Change the order of fields in the “Budget Reporting Period” field set

  1. Navigate to Object Manager

  2. Navigate to the “Financial” (ampi__Financial__c) object and click on it

  3. Navigate to Field Sets

  4. Click on “Budget Reporting Period” (ampi__BUDGETREPORTING_PERIODIC_COLUMNS)

  5. Rearrange the fields in the field set to match this order:

    1. FTE %

    2. Actual Cost per Unit

    3. Actual Quantity

    4. Amount Actual

    5. Comments