Hi, could you help me with my project please?

[shalmaxb]

Think about the following:

1. Either venue owners and musicians should be users of your app.
2. Create the different user groups and roles. In the roles there will be the tweaking in the end, and it will be a lot, be aware.
3. Well, a venue will have the venue group and a role, that only shows, what this user needs.
4. A musician will have the musician`s group and as well the specified role.

The role you can define in a last step. First organize the user groups. As nearly every other entity, you can create your custom adaption directly in the user entity. Create all fields, that are imaginable necessary. For field, that one usergroup should not see, you can use conditional field, groups of fields, you may put on panels in the layout manager, wher you have another possibility to hide or show, depending on user group or role.

In both groups you could attach persons, that belong to the main user of that group. For example: A venue has a boss and several other people, that belong to that venue.
Or musicians play in a band and only one is a registered user, the other members of the band you register like contacts, that belong to the band.
By relationships you can show them, where you need. I do it this way with galleries. There is an owner, but also e.g. a secretary. The secretary will be a contact, that belongs to the gallery.

Generally spoken, in databases it is in the majority of cases best practice, to separate the different (sub) database entities. In the example you would not give every band member an user account of his own, because normally that is not necessary. So you put all connected band members in another entity, in my case in contacts.
In the end you will have a number of entities, all separated and easy to maintain and connected by relationships. This way you will achive the least redundance of data and much less work.
But it has to be well thought and surely you will have to stat over from time to time.

[shalmaxb]

yes, it is one contact in the artists work portfolio. This contact bought one painting (which is pulled from the main entity of total list of artworks from this artist) and with another relation the respective invoice is shown in the contact. Means, if you call the contact, you can see, which artwork this contact/client bought and the vinculated invoice with that sale. Vice versa, this contact is shown in the artwork detail view, wehre the work is marked as sold and showing the buyer (this contact).
In this view three different entities are shown (contact, artwork and invoice), but I related yet more for other purposes, that are not seen in this view.

[shalmaxb]

Hi, I am not sure, if this ist the right approach. You will see, if everybody who wants to book a stage has an account, you will have a lot of tweaking, what the single user will be able to see or what has to be hidden. Complicated.
espoCRM is mirroring workflow from real world, where there is kind of hierarchy (one is the boss and there are a few others with certain tasks and rights, the rest are contacts and company accounts - I know it is a bit simplyfied), accounts are more for companies with which you work together and as far as I know, it is not meant to be a user account. Though you can bend the system to do that, but, as said, it will be complicated, I think.

I understand, that you want to create kind of an exchange place, where musicians/bands and venue owners could meet, all self organized by the different participants. I think, this will be possible somehow, but I don`t have an idea yet. But I will think a bit about it.

To integrate a button, you will need to code. There are several threads here and something in the documentation about it.

[punkyard]

shalmaxb, to sum up, your picture shows an artist Contact page, which shows the artist art work, and bellow, the contact name whom bought the art piece and the price of in an invoice?

[punkyard]

now, I start liking the idea of personal Accounts created by each artist aside of each Stage. The Account field would just have to be hidden on the Stage layout, right?
Though, could I integrate a button "Create new account" on the Stage page?

[punkyard]

my first attempt, was to show personnal/private/hidden-to-others fields in the Stages entity
so every artist can create a public Stage, in which every artist will created hidden personnal notes in a personnal pannel (as in CiviCRM)
but i think I read somewhere that hidden/personnal fields were not possible in EspoCRM

[punkyard]

let me put it in other words, to make sure I describe things properly :
In my expectation ..

an artist will create a 'public' Stage in the Stages entity, every other artist can see (size of the stage, number of seats, town, country)

but every artist needs a personal company Account in Accounts entity related to that public Stage, in which writing down personal datas (negociated prices, contacts, phone numbers, ..)

so, every artist can see every stage, but only his own account related to one stage

[punkyard]

hi espcrm, i guess my english's got a limit, I didn't not understand your reply. Could you reformulate please?

[punkyard]

thanks a lot shalmaxb, again. I'll look into this .. i'm not certain that i understand yet correctly the possibilities you expose here .. but i'll try ^^

[esforim]

If it were up to me, and if I were to use the extension but it lack a certain function for in this case I would just ask if the developer can add it in. Who know, they might agree to it. punkyard

[shalmaxb]

Hi,

the approach itself is right (one stage can have many musicians, one musician can have many stages = n:n relationship). 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 or use the extension "Link Multiple Inline Form" by Eblasoft (https://www.eblasoft.com.tr/product-...le-inline-form). This extension is not free, but does the job very well.

But even with this extension, there is no way to use the other fields than "name" for priniting (PDF) or Email templates out of the box. Neither you perhaps might know, that you cannot print the list view, in case you want any PDF or hardcopy lists of you records. In these cases you must use workarounds.

Here a screenshot from my contact`s entity, n:n related with two other entities. All customized and using the extension by Eblasoft. For the display of the fields in the related list, you can freely choose, which fields you want to show.

[punkyard]

Hi,

I'm trying to build a DB of Stages for independent song-writers to share a list of small venues with which they could arrange concerts.

All the artists/Users will share a common list of Stages (with common info as: addresse, principal email)
but all informations about accounts and contacts would remain personnal to the artist and/or the members of his band/team.

I thought of a multiple-to-multiple link between the tables :
to one Stage could be added several accounts that would stay personal to each User
to one company Account could be added several Stages when one company owns several venues)
but I don't find a way to do it yet ..

The best would be to show the personal data of each artist in the Stage Entity - but I think I read somewhere that it's not possible with Espocrm.
The least would be to show the list of the Stages related to an Account, through the account entity.

would someone take a moment to think about this and share one's thoughts?
it could be very simple to put in place, but i just can't manage ..

thank you all