Single control module crashed after adding name aspect to it. How to correct it and why adding name creates issue?
Asked 1 year ago
Answers
0
Hi, too little information. What does it mean Single control module crashed? Normally Name aspect is created by default in each newly created object in 800xA. There is no need to add Name aspect. Can you recover your SCM from last AFW backup if available?
Answered 1 year ago
0
------------------------------
When i created a single control module in the library level in CBM and give a name as "Test", it will appear in the object type structure as Test but with "Relative name" aspect and not with a "Name" aspect.
So the issue i came across is that, i tried adding a name aspect to this, then the single control module name got changed to SM1 and all the child objects under the single control module vanished and was available at the unit level.
------------------------------
So it sounds like you created an Object Type, not a "Single" control module. Single control modules do not appear in libraries, they are unique Control Modules in an Application.
- A Relative Name aspect names a Child ( or Sub ) Module Relative to the parent module. Relative Names are only used by object types.
- A "Control Builder Name" aspect contains the name of the Object in Control Builder. Do not change this
- A "Name" aspect contains the Display name.
Do NOT manually create these aspects, or bad things will happen ( as you already know ). These aspects are created automatically when the objects are instantiated in the Library or Application.
If you are really lucky, you can simply delete the "Name" aspect that you created manually and the Program code will re-appear in Control Builder.
When i created a single control module in the library level in CBM and give a name as "Test", it will appear in the object type structure as Test but with "Relative name" aspect and not with a "Name" aspect.
So the issue i came across is that, i tried adding a name aspect to this, then the single control module name got changed to SM1 and all the child objects under the single control module vanished and was available at the unit level.
------------------------------
So it sounds like you created an Object Type, not a "Single" control module. Single control modules do not appear in libraries, they are unique Control Modules in an Application.
- A Relative Name aspect names a Child ( or Sub ) Module Relative to the parent module. Relative Names are only used by object types.
- A "Control Builder Name" aspect contains the name of the Object in Control Builder. Do not change this
- A "Name" aspect contains the Display name.
Do NOT manually create these aspects, or bad things will happen ( as you already know ). These aspects are created automatically when the objects are instantiated in the Library or Application.
If you are really lucky, you can simply delete the "Name" aspect that you created manually and the Program code will re-appear in Control Builder.
Answered 1 year ago
by AVK Rank: 3402 on 3/7/2019 12:29:45 AM | Like (0) | Report
Thanks Kamil Herman.
I understood the issue here. When i created a single control module in the library level in CBM and give a name as "Test", it will appear in the object type structure as Test but with "Relative name" aspect and not with a "Name" aspect.
So the issue i came across is that, i tried adding a name aspect to this, then the single control module name got changed to SM1 and all the child objects under the single control module vanished and was available at the unit level.
I would like to know why this issue appeared and also how can i correct it without using a backup. Also, i would like to know the difference between the "Relative name" and "Name" aspect
Add new comment