Like-named properties are just easier to spot when using the API and/or the HubSpot UI.Ĭreating a custom property involves a POST to the appropriate entity endpoint (e.g. “/properties/contacts/“).Using a convention will help us avoid potential clashes with 3rd-party HubSpot integrations.“delete all of our property groups that start with ‘bfg_property_group’”). If we have a well-defined convention, we can leverage that when writing scripts (e.g.We try our best to consistently use naming conventions – prefixing all properties, property groups and objects according to a company-wide standard.These are optional but highly recommended if you’re creating more than a few custom properties per entity type (e.g. HubSpot allows you to create “property groups” that can help visually separate properties in the UI. ![]() Feel free to use any client you prefer (e.g.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |