Now everthing is working as we want, thank you very much! Now only the styling is missing and regarding the styling we would like to ask if following structure would be possible for the columns on the right side:
Screenshot_3.png (9.15 KiB) Viewed 527 times
The left column is the room and the right column the seat.
thanks for your response and sorry for not providing more informations so I will try again.
For our use case, we need to be able to book seats/tables for each room. We could already implement this with the help of the mergeCells and it looks like this:
Screenshot_2.png (40.29 KiB) Viewed 466 times
This is how we structured our resources currently:
How the data structure should looks like?
Room contains tables, that's clear. How persons should be stored? Do they child nodes of rooms or just separated entities?
Or one person has few rooms inside? As for me, I don't understand why do you need to store rooms and persons (different entity types) in one store. Maybe data structure should be changed? Or all of them are Resources? Or you only need to mark that some person is staying in some room?
I have now clarified the requirements again and the resources should look as follows:
The structure for the rooms and tables stay the same but the persons are separated entities/resources. The reason for this would be to have the availability of the rooms/tables with the availability of the people at a glance and to be able to book the tables accordingly.
So is it possible to use different entities or resources in one scheduler?
That's the general question for your database structure as well. One table usually contains records with one data model. Same with Store. If you set some "type" attribute and will base your extra logic on that value, that's doable.
I would suggest you to look at these instruments and decide which one will better fit your needs:
Also is it possible to remove the header of the columns of the resources?
You could provide empty text as a value for column title, but you cannot hide it because it will affect on time axis part also, it should be on the same level to look synced.