Dynamically Name Point Description

Using Parameter Sync, you can create a rule that dynamically names your point descriptions for eVolve's custom points. This would only apply to objects that use the eV_Point family to extract the point location and would not apply to Fabrication (ITM) hangers.

In this article, we are going to dynamically create point descriptions on sleeve points to provide a similar description to what is delivered automatically for fabrication hangers. In the screenshot below, you will note that sleeve points are typically blank and requires this information to be edited before point export. For instructions on manually editing these fields see Points Manager.

To automate this information, we are going to take advantage of eVolve's Parameter Sync feature which allows you to synchronize one or many parameters to another. The next screenshot shows the result we will get.

To achieve this, we create two separate rules. One for box out sleeves and one for round sleeves. The following screenshots show how the rule was defined:

First, we need to define the Element Filter rule that searches for the rectangular sleeves.

It is easiest to create and test your element filter outside of Parameter Sync with the select action and then use the copy option to use that rule in this Parameter Sync.

Here is the rule for box out sleeves

Here is the rule for round sleeves

Once the element filter is defined which tells the software to find and select these families, it is time to define which parameters will be synchronized to the point description field.

For box out sleeves, we want to create a rule that concatenates the information from sleeve width, sleeve depth, service abbreviation and family type name. The rule is:

<Sleeve_Width> x <Sleeve_Depth>_<eM_Service Abbreviation>_<Type Name>

For round sleeves, we want to create a rule that concatenates the information from sleeve diameter, service abbreviation and family type name. The rule is:

<Sleeve_Nominal_Diameter>ø_<eM_Service Abbreviation>_<Type Name>

The screenshot below shows the final setup for these rules.


How did we do?


Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)