Hey appreciate the reply. Yeah definitely possible that I am looking at it the wrong way. Though I have come across this use case for Custom Objects a bunch over the past 10 years. Especially with Salesforce. Basically it is similar use to the main Deal object. Wanted a unique custom object for an individuals Registration/Application to an event or training school. This allows multiple individuals to be associated to a single registration in the case of groups, couples, and families with kids. It also gives better record keeping and reporting for the events and it’s attendees. I have attempted to manage registrations simply on a contact record using custom properties and it is a nightmare. So yeah this custom object is not for the event itself, though I am considering another object for that, just not a priority to get started. The challenge I came across in my original post was that I could insert the custom object properties in a form, though because each submission sent through the same event name it just associates every contact that submitted it to a single Event Registration record. So yeah ultimately the issue comes down to having a Unique Name or not. The main workaround, which seems to be the case even for deals, is to have a workflow triggered by the form submission that create each unique custom object record. It is working well I just hate having to have so many different steps involved when creating new events. Makes scaling difficult. Anyways hope that clarifies.