Default constituent restrictions are not populated on a sublevel event

When registering for an event the default constituent restrictions populate the constituent restrictions for an event. If a constituent registers for the main event of a multi-level event and then after adds a registration for a sub level event the restrictions are not populated to the sublevel event. If the constituent registers for both the main and sub level event at the same time the restrictions are populated correctly on the sublevel event.
We’re currently evaluating this issue for a fix in a future service pack.
 

Steps to Duplicate

1. Create or use a constituent with a Default Event Restriction.
2. Create a multi-level event.
3. Register the constituent with the Default Event Restriction to only the main event.
4. Click on the constituent from the registrations tab, click on restrictions tab. Note the default restrictions are populated.
5. Navigate back to the main event, registrations tab. Edit the registrations for the above constituent.
6. Register for a sublevel event.
7. Navigate to the sublevel event and click on the constituent from the registrations tab. Note the default restrictions are not populated to sub-level event.  
 

Environment

 Blackbaud CRM
 4.0
 4.0.178.0

Was this article helpful?