In Dynamics, spaces in which an event can take place are described hierarchically. I think, buildings contain rooms contain layouts.
Dynamics has two tables, "Building", name, "msevtmgt_building", and table, "Venue", name, "msevtmgt_venue"
There is a field on the venue table, "msevtmgt_buildingid", which suggests the venue is a child of a building. But there is also a field on the venue table, "msevtmgt_parentvenueid", which suggests a venue can be a child of another venue.
When you create an event, you can add a location (see attached screenshot). It seems what you are doing is adding a building record to the building table. You can then, if neccessary, add rooms within that building and layouts within those rooms.
Whenever you create a building, a venue record is created on the venue table, with the same details as the building.
Questions:
a) Is my description above correct?
b) Why does Dynamics have both venues and buildings, if the information in both is the same and kept syncronised? If I am correct, and events take place in buildings, where are venues used?
c) Do venues contain buildings or do buildings contain venues? Or neither or both?
d) Where do I find the, "plugin or other back-end Microsoft process that keeps things synchronized"? (See comment from @Tom_G)
e) We want to add some custom fields to the location for our events. Does it matter if I add these to the building or venue or both?
f) Does migration from Outbound marketing to real time journeys change any of this?
Thank you for your help. Guy
