Design builder should be entirely agnostic to any naming of custom relationships, custom fields, or other built in properties/attributes/field names, etc that exist on models.
Observed Behavior
Certain named attributes throughout design-builder have effectively been implemented as reserved attributes/names and cause errors when referenced.
Steps to Reproduce
Create a custom model named Environment
Create a custom relationship between Device and Environment
Create a design that attempts to create a device (even without populating the custom relationship)
Run the design
Receive an error that 'Device' does not have an attribute named 'environmnet'.
Environment
Expected Behavior
Design builder should be entirely agnostic to any naming of custom relationships, custom fields, or other built in properties/attributes/field names, etc that exist on models.
Observed Behavior
Certain named attributes throughout design-builder have effectively been implemented as reserved attributes/names and cause errors when referenced.
Steps to Reproduce