-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
3
-
Severity 2 - Major
-
Issue Summary
Sometimes, when editing Insight object type attributes, the saving of an object type attribute will fail and subsequently, the attributes view on the object type will not render anymore. This is because the `defaultType` property has disappeared from one of the object type attributes that is of type "Default" - "Default" type attributes need the `defaultType` property to be set for them to work properly.
Steps to Reproduce
It is unknown why the `defaultType` property disappears from the object type attribute, or under what exact circumstances this happens. Therefore, I do not have steps to reproduce - all that is known so far is in both recorded cases of this happening, it happened after the saving of an object type attribute failed.
Expected Results
When an object type attribute is saved, it should either succeed or fail and show an error flag. The existing attributes should be visible on the object type attribute view, along with the updated attribute (if the save was successful).
Actual Results
There is a console error:
Uncaught TypeError: Cannot read properties of undefined (reading 'id')
at Object.RLABS.tpl.objecttype.attribute.operations
And the object type attributes view is blank:
Workaround
At this point, the only workarounds are to either abandon the object type and create a new one, or to have a developer manually fix the corrupted attribute record in the database.
- is duplicated by
-
JSDCLOUD-11528 Adding an object type attribute with empty Default type caused attribute UI not loading
-
- Closed
-