OroCRM allows creating custom bundles with different functionality. And working with OroCRM you may notice that bundles without an entity is a rare case. It is not difficult process and you can easily create an entity with different configurations. But what if you want to remove an entity? In our article we share the tips on how to do it correctly.

Grid in OroCRM is a very convenient way to display information about all or few records of an entity. Default OroCRM has a lot of grids for different entities. OroCRM developers provided a useful and easy way to create grids for a custom entity or display some specific information for default entities.

How to change the configuration of the field's entity using migration in OroCRM

Sometimes we can face with the different dependencies between the system bundles or bundles that are already created by other developers, and we will have to change the configuration for such bundles. Usually, it can be easily done because OroCRM has a quite good GUI interface. So, using GUI you will be able to change the configuration for any bundle. Nevertheless, pay attention that if you need the bundle for deployment to different servers, this way is not convenient. In case of deployment, you will need to add a description of the appropriate settings and it is also important to follow these settings in further development. The best way is to use the migrations scripts. In this article, we will show you how to change a config of a single entity in the bundle.

How to change or remove ownership scope in OroCRM entity configuration

Every OroCRM developer can face with a situation when there is a necessity to change a configuration for the entity config in the bundle. And it is no problem if we have an ability to remove a full bundle with the database tables. Recently, we’ve tried to change the ownership scope for the existing entity, but we could not delete the tables because there were a lot of data.