unexpected prefix behavior when renumbering points in a Revit family with parametric visibility

[tgoodwinX2SUJ]

I have a 'trapeze hanger' family, a length of strut suspended by two or three threaded rods. There is a GTP point nested into this family at the top of each threaded rod. The visibility of the center rod and its point are controlled by a yes/no instance parameter and are hidden by default. The point prefix for these points is supplied by the value ('HANG') of an 'APL_PointPrefix' text family parameter in the 'trapeze hanger' family.

There is some additional complexity in this family that I don't think is part of the issue, but that I'll describe just in case: the 'trapeze hanger' family also hosts a non-shared 'crossbar' family, which in turn hosts a shared 'strut' family. The 'strut' family has two additional GTP points, one at each end. The point prefix for these points ('STRT') is supplied by another 'APL_PointPrefix' text family parameter in the 'strut' family.

By default, the center rod of the 'trapeze hanger' family and its point are not visible. Placing any number of two-rod instances of the family into a blank project and running the APL renumber command works as expected. Placing any number of two-rod instances and then turning on the center rod for any number of them, and then running the APL renumber command also works as expected. However, starting again from a blank project, if you load in the family, run the renumber command, edit an instance of the family to show the center rod, and then try to run the renumber command again, the newly-visible center rod point will be renumbered but will not pick up the 'HANG' prefix as expected.

[s.hamel]

The key here is that the auto prefixing is not actually a part of the renumber functionality. When you trigger the renumber, if the point already has a prefix it will be kept during the renumber, but one will not be added during the process.
Auto prefixing is part of the general automatic numbering of points that do not currently have a number already set, and is triggered as a prerequisite of any function that needs points to have numbers (Which renumber does not), e.g. Import/Export points, Manage points.

So for your process, add the step of opening the Manage points screen just prior to triggering the renumber function, this will force that newly shown rod point to be given a number with its proper prefix, which will then be kept in place when you renumber.

Thanks,