can not delete a Batch Unit CMT due to Alarm & Event List reference
A error message came up when I tried to delete a Batch Unit CMT in Control Builder M.
"[Error] An Alarm & Event List references this aspect. If you are sure that you want to delete this aspect, first delete the Alarm & Event list that references this aspect
"[Error] An Alarm & Event List references this aspect. If you are sure that you want to delete this aspect, first delete the Alarm & Event list that references this aspect
Transaction Cancelled."
after I click ok button, another message popped up like below.
The 800xA system version is 5.1 rev D.
Is there a way to find the alarm & event list?
Thank you.
Asked 1 month ago
Voted best answer
1
Hi YZEN,
No, not really.
Most likely the CMT has an Alarm and Event Configuration Aspect that is used somewhere else in the Object Type Structure. Right Click -> Properties -> References on this aspect might help. Try deleting that aspect on its own to see if it tells you any more.
Next I would suggest looking in other library versions of this CMT, then looking in other similar object types that may have been forked or copied from this object type.
No, not really.
Most likely the CMT has an Alarm and Event Configuration Aspect that is used somewhere else in the Object Type Structure. Right Click -> Properties -> References on this aspect might help. Try deleting that aspect on its own to see if it tells you any more.
Next I would suggest looking in other library versions of this CMT, then looking in other similar object types that may have been forked or copied from this object type.
Answers
1
I’m guessing that the object has an Alarm and Event List filter aspect that is in use by some list.
AFAIK, there exist no tool to find the dependencies (one or more a/e lists).
You are likely facing a manual effort here. The search scope shouldn’t be too large, though.
AFAIK, there exist no tool to find the dependencies (one or more a/e lists).
You are likely facing a manual effort here. The search scope shouldn’t be too large, though.
Add new comment