Good Morning:
I am working on adding our Joint Use (Telecomm and fiber) to my Electric Utility Network. I have our poles added to the Structure Junction Feature Class - Medium Voltage & Low Voltage Pole Group(s). I've started appending the Joint Use Data from my existing GDB table into the Joint Use Utility Network GDB table. Figured out how to take the pole GlobalID and assign it to the table field to associate the record in the table to the pole in the feature class. However, I am getting this message in the Attributes box:
Some poles may have multiple fiber/telecom joint use attachments and we need to be able to see them. In my previous GDB, I had a relationship class to do that. However, little confused how to do this same thing in the Utility Network.
Reason why I am setting this up is because I've been asked to work with the ESRI Joint Use Solutions package to implement a new Joint Use Tracking/Review application.
Appreciate any feedback.
Solved! Go to Solution.
Thank you for the response. I did verify all of the rule(s) I need - Medium/Low Voltage Pole to Cable/Fiber/Telecom (Joint Use) Relate Rules are infact Enabled.
Still seeing the Red warning error in the attribute dialog box, but can "Drill-Down" to the Joint Use table and see the record.
Is there a part I am missing or did not do?
Then that appears to be a bug, please log a case with support. I was able to make the error go away by removing all the other rules associated with the fiber subtype, but that doesn't seem appropriate.
Right-click the relationship class between the structure junction class and the joint use table and set the relationship rules to meet your requirements. You will either need to configure explicit rules for all the subtype combinations, or remove all the rules.
Thank you for the response. I did verify all of the rule(s) I need - Medium/Low Voltage Pole to Cable/Fiber/Telecom (Joint Use) Relate Rules are infact Enabled.
Still seeing the Red warning error in the attribute dialog box, but can "Drill-Down" to the Joint Use table and see the record.
Is there a part I am missing or did not do?
Then that appears to be a bug, please log a case with support. I was able to make the error go away by removing all the other rules associated with the fiber subtype, but that doesn't seem appropriate.