Survey SMD chain label

If you are using the OpenRoads Survey tools in Power GEOPAK, you can use the VBA "LinearFeatureDescription" to automatically annotate the pipe sizes.  To do this, the pipe size would have to be imported as a description for the linear feature:

Then you can set up the VBA Macro to annotate the linear feature description:

For an example of setting up Survey to use the VBA Macro, check out this video:

If you are using the OpenRoads Survey tools in Power GEOPAK, you can use the VBA "LinearFeatureDescription" to automatically annotate the pipe sizes.  To do this, the pipe size would have to be imported as a description for the linear feature:

Then you can set up the VBA Macro to annotate the linear feature description:

For an example of setting up Survey to use the VBA Macro, check out this video:

Hello Kevin. I'm using VBA macros in OpenRoads. My issue is a result of the problem described in this post......
communities.bentley.com/.../linear_feature_description_incorrect

So my workflow to overcome the issue is this...
1. Import FBK files to OpenRoads.
2. Resolve all line work connectivity issue.
3. Add or revise the chain descriptions in OpenRoads survey details. (get rid of the "JoinPoint Chain" from the description)
4. Apply the appropriate labeling macros to the chains.
5. Export the chains to Geopak Survey from OpenRoads.
6. Visualize the survey chains from Geopak Survey into a clean dgn file.

The issue is I have never been able to label a linear element using the SMD and Geopak Survey. The issue in OpenRoads pertaining to the label is the label is not static. If for any reason the data file needs to be reimported the label goes away and I'm back to "JoinPoint Chain" for description.

An option is to label in a separate dgn. Like this..
1. Import FBK files to OpenRoads.
2. Resolve all line work connectivity issue.
3. Add or revise the chain descriptions in OpenRoads survey details. (get rid of the "JoinPoint Chain" from the description)
4. Apply the appropriate labeling macros to the chains.
5. Export screen graphics to separate model and maintain the labeling there.

Not very efficient but I can get it done. Any ideas for a better way?

Cliff