Open joesinger12 opened 3 years ago
Original comment by: joesinger12
11/6/20 SC - "Undefined" (case insensitive) is a 'reserved word' in the rules and use of that as an object name is confusing the rule evaluator. I will look into this in more depth soon.
For the time being - best to avoid use of 'undefined' (of any case) for any object's name.
Longer term we can either fix the rule evaluation to not get tripped up in this situation -OR- fire through the model (via software) and rename any object by this name (like what is mentioned below, 'Undefined1').
Original comment by: joesinger12
Original comment by: joesinger12
Original comment by: joesinger12
Original comment by: joesinger12
Original comment by: joesinger12
Original comment by: joesinger12
11/5/20 CEC - The attached file throws an error related to terminal unit naming and it looks like the solution is the change the name of the parent HVAC system from ‘Undefined’ to ‘Undefined1’ or anything other than just ‘Undefined’.
My guess was that ‘Undefined’ might be a defined term in our Ruleset and therefore can’t be used for naming of objects, but we wanted to see if you could explain what’s going on here.
Reported by: joesinger12
Original Ticket: cbecc-com/tickets/3236