Hi!
We currently have a setup where multiple business units are handling their own Events, doing so with a shared marketing form/event registration form.
Basically all the forms are being developed/customized/owned by the adminteam located in parent Business unit, and access is then shared to the child business units.
Contacts are NOT shared between business units, so each and every regular user is limited to access the data belonging to that specific BU.
A Contact-record might exist multiple times in the database, spread over the different BU's.
Our problem arises when a Contact registers for an Event through the registration form (standard realtime marketing form), and the matching strategy is done against the whole Contact-table. In our case it should have been limited to searching/matching against the Contacts belonging to the same BU as the owner of the related Event. As it is now the Contact which is selected can and in many cases does belong to a different BU than the one handling/owning the Event - presenting a host of problems.
Long story short:
Does anyone have a suggestion for a workaround in this case? Matching of the contact should be done against the Contacts belonging to the same BU as the owner of the Event.
If no match is found in the BU...a new Contact should be created as usual etc (this works just fine out of the box).
I have pondered the idea of passing the guid/name of the BU from the Event-owner through to the form and then returning this value with the submission/registration - then building this into the matching strategy.
I'm not sure how I'd go about passing this data through though..
Really open for suggestions here, as this is quite an issue :(
Share
Report
All responses (
Answers (
170
