APIs & Integrations

DEsposito
Membro

Differentiating Custom and Non-Custom Properties in a Get Schema Request

resolver

We want to be able to get the schema for one of the standard objects (like contacts/companies etc.) and use that response to update our system tables with the custom properties we write for those objects (in the case that the info somehow gets deleted from our tables or out of sync from what's on Hubspot). However, when we get the schema for these objects, there doesn't seem to be an obvious way to tell the custom properties from the standard properties. Is there a known way to tell them apart?

0 Avaliação positiva
1 Solução aceita
webdew
Solução
Orientador(a) | Parceiro Diamante
Orientador(a) | Parceiro Diamante

Differentiating Custom and Non-Custom Properties in a Get Schema Request

resolver

Hi @DEsposito ,

Standard properties will be required properties or inbuilt properties created by hubspot like https://prnt.sc/1b0saw7 and custom properties created by user with hubspot and using hubSpot api.

Hope this helps!


If we were able to answer your query, kindly help the community by marking it as a solution.

Thanks and Regards. 

Exibir solução no post original

2 Respostas 2
webdew
Solução
Orientador(a) | Parceiro Diamante
Orientador(a) | Parceiro Diamante

Differentiating Custom and Non-Custom Properties in a Get Schema Request

resolver

Hi @DEsposito ,

Standard properties will be required properties or inbuilt properties created by hubspot like https://prnt.sc/1b0saw7 and custom properties created by user with hubspot and using hubSpot api.

Hope this helps!


If we were able to answer your query, kindly help the community by marking it as a solution.

Thanks and Regards. 

DEsposito
Membro

Differentiating Custom and Non-Custom Properties in a Get Schema Request

resolver

Ok, we'll look into using that to check. Thanks for the help!