Hanger Rule Migration

With added ANY rules in 4.0 you can now create material specific rules inside the service configuration. As such there is now no need for a separate material configuration within Hanger Settings and it will be deprecated in coming releases.

We recognize that you have many highly tailored rules and in order to make this switch easy, we have provided a hanger migration script within our resources folder.

Please follow the steps below to convert all your existing rules.In order to make this

For Existing Projects

The Powershell script must be run on each project containing different hanger specifications.

To export hanger specifiactions
  1. Open the desired project.
  2. From the eVolve Mechanical ribbon, in the Utilities panel, click Settings, then click Hanger Specifications.
  3. From the Hanger Specifications window, click the Export/Import and click Export to File.
  4. From the Save As window,
    1. Navigate to the Desktop .
    2. Enter HangerConfiguration.xml in the File Name dialog .
    3. Click Save.
To quickly access the import file, leave the Hanger Specifications window open in the background while performing the To run Powershell script steps.

To run the Powershell script
  1. From Windows File Explorer, navigate to C:\Program Files\eVolve\eVolve Mechanical for Revit 20xx\Resources .
  2. From the Resources folder, right-click on the UpdateHangerConfigurationFile.ps1 file and click Run with PowerShell .
  3. From the Windows PowerShell window, press any key, the HangerConfiguration.xml is updated. Press any key to close the Windows Powershell window.

To import updated specifications
  1. From the Hanger Specifications window, click the Export/Import and click Import from File.
  2. From the Open window, navigate to the Desktop, click the HangerConfiguration-Service.xml, and click Open.
  3. From the Notice window, click OK.

Verify Data

After importing, verify the data has been imported correctly and that no duplicate or conflicting rules exist.

Optional: click Save as Default - this may be beneficial if the rule sets are standardized across projects.

How did we do?

Powered by HelpDocs (opens in a new tab)