Workaround or ability to exclude the primary property of an object from the creation UI form

Develop, Build & Integrate
1

Hello,

I am creating a custom object for my CRM. The primary property is a calculation of component objects that the backend creates and updates. This calculated primary property is what I am designing to be displayed on association preview cards for contacts, which works, since the primary display property is a required field on the association preview display.

However, on the create object form for my custom object, the primary property appears to be a required field. Even if the primary property was not specified as requiring unique values. This is an issue since I would like users to fill out each component property in the UI creation form which then calculates the primary property.

Is there or workaround or can you make this feature available?

The workaround I have been using for now is telling team members to submit a dummy value in the calculated field (note: this calculated field is calculated using a server + API, not a hubspot calculation field, thus it can be edited). My backend detects the dummy value and clears it/overwrites it.

However, this is a bit messy and non-technical users often forget what the dummy value or are unsure of what the instructions were, thus leading to a messy user experience.

I will note that the API creation endpoint works even with the omission of a value for the primary property, it will just generated the object record ID with empty fields. That indicates that the omission of the primary property is not a backend limitation within HubSpot but rather a UI limitation it seems.

I can’t make a component field the primary display property since then the association preview cards require that property on the preview card and, additionally, any single component or all components may be supplies as empty (that is a valid configuration).

2

Update: I was able to set a default dummy value for the primary property. So it’s still required on the form but the value does not require entry. This is still a workaround as it would be cleaner if the form was allowed to exclude the primary property but it is a marginal improvement.

3

Hey @RLehrhaupt, thanks so much for taking the time to share this feedback and the workaround you found with the HubSpot Community!

I’d recommend submitting it through the HubSpot Developer Feedback form as well, so it can reach the right team directly.

For reference, here’s some documentation that may be helpful:

In the meantime, I’d love to bring in some of our Top Experts to see if there’s another workaround we can explore. Hi @evaldas, @Anton and @Mike_Eastwood do you have any ideas that could help @RLehrhaupt here?

Thanks again for sharing this, and I hope you have a brilliant day! :blush:

Bérangère

5

Hi @RLehrhaupt and thanks so much for sharing this workaround with the HubSpot Community, we really appreciate it!

Have a wonderful day!

Bérangère