Modifying base application layouts in extensions doesn't work

[bandtank]

I modified the layout for the Account entity, which works fine when the detail.json file is in custom/Espo/Custom. However, moving the file to custom/Espo/Modules/MyModule does not work. Is there a way to modify the configuration of base entities in modules?

[yuri]

There's no any recommended approach. It's possible to change the module for the Account scope, but it will require some additional changes.

https://github.com/espocrm/espocrm/blob/9.1.8/application/Espo/Modules/Crm/Resources/metadata/scopes/Account.json#L7

[bandtank]

Ok, thanks. I will leave the changes in Custom. The only potential issue is upgrading the application in a container, which can be worked around without a lot of hassle.

[rabii]

I modified the layout for the Account entity, which works fine when the detail.json file is in custom/Espo/Custom. However, moving the file to custom/Espo/Modules/MyModule does not work. Is there a way to modify the configuration of base entities in modules?

you can achieve this using layouts metadata. i have done this many times and it works fine.

https://docs.espocrm.com/development/metadata/app-layouts/#app-layouts

e.g

{ "Account": { "detail": { "module": "YourModule" } } } 

then just put the new detail under layouts > account > detail in your extension and it should work

https://github.com/espocrm/espocrm/blob/1c155c4e19b523e00848ae3c879195069afa4054/application/Espo/Tools/Layout/LayoutProvider.php#L69

[bandtank]

rabii Thank you. This is very helpful. Does the full layout need to be defined in the module, or does it still work the same way as before? I.e., Is the customized layout appended to the base layout?

[rabii]

Hi @bandtank

you need to define the whole layout. e.g the whole detail layout for detail.