Tree structure for customizing Entity

[zkuun8]

Hello,
I use EspoCRM for few weeks and would like to learn how to customize an existing Entity: "Opportunity"
In my case, I would like to :
1) customize an existing view "Details" by adding a calendar "FullCalendar" : the aim is to match the calendar with a new field "customdate"
2) create a new view "Custoview" and adding a FullCalendar library to this view, in which all records appears (using le field "customdate")

I don't ask you to work for me by giving me the code to do this, but I ask you to help me to understand the needed tree structure of files/folders to perform this kind of customization.
I feel lost with the ressource I found.
Any advice would be really appreciated !

thanks

[yuri]

Hi,

As the project is quite big, we do not have a strict structure except for metadata, I18n, layouts, Controllers, Entities, and EntryPoints. Needed classes and views are defined by metadata.

You might need to add a new list view mode? Like the Kanban view for Opportunities.

https://docs.espocrm.com/development/metadata/client-defs/#listviewmodelist

https://docs.espocrm.com/development/metadata/client-defs/#recordviews

In metadata, you can specify a frontend record view. Then, your view will be for example: client/custom/src/views/some-path/your-record-view.js

[zkuun8]

Hi and thanks for your answer.

1) coulD you confirm that in order to create a new view, step 1 = specify in metadata the new view. Step 2 = building file/tree structure that match with what is specified into the metadata file (eg:
client/custom/src/views/some-path/your-record-view.js)

2) in the case I need to customize an existing view, like kanban. Do i need to rewrite from scratch tge kanban view ? In my case i want to split the kanban view into 2x div, and make the kanban element clickable in order to synchronize it with the second div. Are this kind of customization possible ?

Thanks you !

[yuri]

1). Yes.

2). It's tricky to say for sure. You can repurpose such built-in views. As long as you access only public methods and properties, it can be deemed as a future-proof.

[zkuun8]

Thanks again !
and in 2nd case in which I need to customize and existing view (kanban for oportunity) what is the workflow in term of tree structure / files to customize it (in the case I only need public methods and properties?

[yuri]

Define a custom record view in clientDefs > recordViews

{
    "kanban": "custom:views/record/kanban"
}

You custom view will extend the existing views/record/kanban.

https://docs.espocrm.com/development/custom-views/