The Field Model Names FiberParentClassModelName and FiberParent

Keep in mind, these are field model names assigned to fields of the same name (they do not have to be the same name, but they are in the standard data model). For example, the F_BUFFERTUBE has a field called FIBERPARENTCLASSMODELNAME and that field has the field model name FiberParentClassModelName assigned to it, which is illustrated in the following image:

Similarly, F_BUFFERTUBE has a field called FIBERPARENT and that field has the field model name FiberParent assigned to it

This arrangement holds true for all fiber features and tables. The class model names assigned to the fields act as the relationship step ladder, if you will, allowing the application to understand the relationship from parent to child (and possibly to grandchild and beyond). The FIBERPARENT field holds the actual GUID of the parent feature or table. This gives the application the specific and unique parent for each child. For example, in this image the five buffer tubes all have the same parent:

This begs the question, how does the application take the GUID from the parent and place it in the FIBERPARENT field of the child? And, what about the parent model name? How does that get into its field? Next, let’s discuss the autoupdater ArcFM Update Fiber Parent Field.