shalmaxb you have to remember about changing all namespaces in your extension. Also you have to change in scope module from Custom to name of your extension.
Before namespaces was generated by EspoCRM, so they're "Custom", and you have to change them in Repositories, Controllers, Services folders to propper for your extension
Pack an entity to make it installable
Collapse
X
-
Hello shalmaxb don't know if you have seen this posting, maybe it can help you https://forum.espocrm.com/forum/deve...able-extensionLeave a comment:
-
Hello, I created an entity and after that, following the blog article about creating PM entity as installable extension, I succeeded in packing the files correctly and installation worked. But in the end there appeared the error 500, telling that one class would not exist in repositories. As far as I see, the class is there, but I don`t get it to work.
Anybody any idea?
emillod , thank you for the hint, I did it in that direction.Leave a comment:
-
Yes, Yuri is right. You can use their template, but if you don't have skills to do so, you can create propper structure of fail, create manifest file and just prepare a package. I started from that, because it is the easiest way.Leave a comment:
-
No such tool from UI yet.
If you don't mind to work from CLI you can utilize the template repository. See https://github.com/espocrm/ext-templ...ension-in-espoLeave a comment:
-
Pack an entity to make it installable
I did not find an answer for this especially. Is there a possibility to pack a whole entity with layout, relationships and custom fields as extension so that deployment could be done easily?Tags: None
Leave a comment: