Description of problem:
This can lead to a troublesome situation when an object that is used in rules is renamed. After renaming the object and saving the Data Modeler, the project will have build errors (unresolvable object type), and if you closed the Data Modeler after saving the change, it will be quite difficult to fix the errors because the renamed object will not be loaded. The only way to fix it in the UI is to re-create the renamed object with its original name, including all its used fields and reloading the Data Modeler.

Surprising, hard to fix.

Steps to Reproduce:
1. Open Data Modeler in mortgages sample project.
2. Rename LoanApplication to LoanApp, save changes, close Data Modeler.
3. Reopen Data Modeler.
4. [optional] Create some new objects, save changes, close, reopen.

Actual results:
LoanApp is not there, so it cannot be renamed back to LoanApplication to resolve project build errors. Any new objects created when project has build errors are not loaded into Data Modeler.

Expected results:
Data Modeler should always display up-to-date objects. If this is "won't fix", then at least display a warning: "Project has errors, cannot load data model completetly". Also it should be possible to easily revert the object rename, that broke the project build.

Additional info: