Known issues

Version 0.5

Following issues and workarounds (where applicable) have been identified with the latest release of RapidCMDB:

1. Issue: There is a list of [reserved words] which can not be used in model definitions. When a model is defined through RapidCMDBModeler, an error is displayed for the user. If a model is defined via a script, the properties named as one of those reserved words are ignored when the script is run. Also, if the model name is set to one of the reserved words, then you will get an error when the script is executed.
   Workaround: Refer to [reserved words] before selecting names for your model, properties and relations.
2. Issue: Some model changes can cause data to be lost. Data may need to be exported before the change and imported after the change. Some changes will require data to be transformed before being imported.
   Workaround: See The Impact of Modeling Changes on Existing Data for details.
3. Issue: Search is supported only for properties, not the relations of an object. (see http://ifountain.org/jira/browse/CMDB-284)
   Workaround: Search by property and then loop through the set for instances with desired relations
4. Issue: RapidCMD supports findBy methods only for ONE property (relations are not supported)
   Workaround: Use compass searches and get instead.
5. Issue: Searching does not work properly when multiple modeled classes have attributes with the SAME name but DIFFERENT types (see http://ifountain.org/jira/browse/CMDB-395)
   Workaround: Make sure the names of the properties are different among classes when types are different.
6. Issue: When renaming a model, property, or relation same name with different case (e.g. modifying SmartsHSRPGroup to SmartsHsrpGroup) causes problems. (see http://ifountain.org/jira/browse/CMDB-771)
   Workaround: Make sure a different name is used when the name is changed.