Hi, could you help me with my project please?

[esforim]

I think I already gave you my advertisement post, it contain thread that I find interesting or it have solution to that question. Consider going to them as shalmaxb said, the search is a hit and miss.

[shalmaxb]

yes, and never regret

[punkyard]

you mean you have purchased this software of eblasoft ?

[shalmaxb]

Sorry, coding is not for me. I try from time to time, but always get stuck. The developer`s documentation of espoCRM is obviously really for developers. I don`t understand.....
One thread is here: https://forum.espocrm.com/forum/gene...-relationships

Another tip for searching: The search function in the forum itself is crap, but when you put it in a normal google search, it gets you to the useful threads.

[punkyard]

yes, I think I manage all that by now

you wrote earlier that multiple links only show the name of the entity, and that I would need coding to display other fields (or by a software which I won't afford) .. so i'm ready to try the coding .. I was asking you a lead (web link, key words) to understand where to start learning this skill ^^

[shalmaxb]

From your questions I have to guess, where you are stuck, for that maybe I give hints for things, you already know. The multiple link field is created automatically, when you establish a relationship, the field has the name of the relationship (as well in the original entity as in the foreign entity as appearing in the relationship). You have to put that field also in the layout manager in position.

[punkyard]

thanks a lot for your detailed answer

am i wrong: you are giving me the steps to create an entity?
Which I can manage ^^

I was wondering where to start with: "multiple link"

"The problem in espoCRM wih n:n is, that by default only the field name is multiple linked. That means, that you can display the names of the stages in every musicians account and vice versa all musicians accounts in every stage, but only the field name will be shown.
If you want to display more information from either of these entities in the related one, you will have to 'code' "

[shalmaxb]

Any entity, that is activated in espoCRM appears automatically in the folder custom/Espo/Custom/Resources/metadata/entityDefs/name of the entity, even those, which are part of espoCRM by default (like users e.g.). The reason for this is, that you may change these entities, by adding new fields, formulas and so on. All inside the custom folder will be update safe, what means, that any update of the core system would not affect the customized entities. Your work is protected in the custom folder.
Own, new entities will appear also in the custom folder.

Well, then you may change anything in the entity "users" and that will be saved in the respective custom entity "users".

For new fields you go to administrator -> entity manager -> entity to customize -> fields and klick in the upper left on "new field". Choose the desired field type, give it a name in the first input box as you want to name your field, e.g. "First Field". In the second input box, this name will be copied and in the first field the name wil be automatically adapted to the name convention of espoCRM, in this case firstField. (By the way this is called "camel case", because it starts with a small letter, has no spaces and the next word starts with a big letter, letting associate the appearance like the humps of a camel).
In the field configuration are more things to configure, depending on the field type. Most of it is self-explanatory.

Be aware, that you my change everything after the field has been created, except the name (first input box). This name goes to the database. If you want to change this, you will have to remove the field completely and start again to create it.

When the field is ready, you need to make it appear in your list or detail views, in the sidebar or wherever it is possible. For that you choose layout manager of that entity and pull the newly created field to a position in your layout. There you can add new empty placeholders for fields, can change the range of fields per line (1 to 4) and even create new panels for field placeholders. The panels you can give another name, appearance (color of header bar, or none) and make the panel show up conditional.

I will not describe everything, what is possible, play around a bit and you will see, how powerful all this is, without having to code.

[punkyard]

on step forward! I have created a relationship between Stages and Accounts, so when an Artist creates a new Stage he can link it to an Account (read/write by his team)
in the layout, ACCOUNT MUST APPEAR IN THE BOTTOM PANEL .. not in 'detail' .. took me a while to figure that out ^^ then it made a whole difference!

could you give me a lead on what to do to add other fields manually please? (links, terms to look for in the forum?)

[punkyard]

Sweet! that's moving forward! So it's going the direction I was imagining. I not sure about all the links yet, coz i'm not sure i'm getting the whole logic yet ^^
So the next part is to have a personnal area in which recording personnal info about the company behind the Stage.

Each artist would be able to create an account linked to a Stage, in which he'll write down his personal contacts and info about the stage.
Then I guess, it would work the same way between the artist/stage and the account/stage, right?

[shalmaxb]

Hi, ok, I understand better now. As you state in the comment above, it seems a lot easier, because you won`t have complicated user roles.

1. The musicians should be users with the right to post venues. You can define that in roles. Don`t foget to mark the necessary fields as required, so that nobody can save a record, that is not complete.

2. You may think about, if only registered users may read the index or if you open it to musicians, who are not registered. If you would like to have that, you may create a user typ guest, with only read rights. Understand, that espoCRM is not an open "Website", so without regarding te role, it will always be necessary to login and for that be registered. Either as Musician or Guest. My opinion: I would not do that, I would give access only to musicians, no guests.

3. Your entity venues will be the main entity, which you may fill with as many records as you want. For this entity you have to think, which fields are important and which relationships to other entities you will need. You could have a relationship to users there, so that in a venue a field could display, which user contributed the venue. In the user the other way round, you could see all venues, that this user contributed.
I would start with the venue and the ideas will come working with it.

4. You will have to think about the user`s entity as well, which field you will need and so on.

But it is not too complicated.

[punkyard]

you make me think shalmaxb ^^ thanks you

.. Artists don't book Stages through EspoCRM, they create an entry for each Stage, with its details - like an index.
Stages/Venues don't have access to CRM and don't book artists.
It would be a platform to help artists booking their gigs in alternative venues.

They are many little bars and restaurants, tiny theatres, associations (non-profit), that greet song-writers on their small stages.
But they are not listed. Sometimes the conditions are barely legal, but that's the working conditions of independent songwriters here ..

Alone, every artist has to spend a lot of time looking for venues like those, enter details, copy-paste, copy-paste, copy-paste .. make a call, send an email ..

With this index, they will be able to share their prospecting work, which can be filtered to find a venue, depending on its size, its city, ..
Simple thing in the end ^^

[punkyard]

thanks again shalmaxb, it gives me a lot to think about yes, i truly need to understand the logic

[punkyard]

I get it now, thanks

[esforim]

Hi punkyard, I was saying that if you plan to buy the extensions Link Multiple Inline Form, you can try ask the developer to add a feature to make it work for you. They might add it or might not but worth a try.