allow custom fields to be accessible/readable via API (for all objects which support custom fields)

Follow

Nicholas Shorter

• 22 February 2023 22:28

Hi guys,

 

It would be great to be able to read and write (GET and PUT/POST) to custom fields across all objects (similar to the related post here, but not restricted to only the Workshop object).

 

In my specific instance I am wanting to tie across students and organisations to our CRM system, but without having to consume the "Optional ID" fields as these can only be used for a single optional ID and we have need of storing more than one ID field to each student

2

• 

  Mark Gilmore

  • 22 February 2023 22:31

  Hi Nicholas

  Thank you for your suggestion. Which object are you looking to read/write custom fields for?

  I have worked with other customers who have successfully done so for contacts using the /contact/:contactID  endpoint and the customField_[variableName] parameter.

  Cheers
  Mark

  0

  Comment actions Permalink
• 

  Nicholas Shorter

  • 22 February 2023 22:42

  Hi Mark,

   

  That was quick!  I am looking at both Contacts and Orgs.  I've just had a play around with the Contact custom fields and can indeed GET and PUT the custom field. 

   

  This does not appear to be the case for Orgs though...

  0

  Comment actions Permalink
• 

  Nicholas Shorter

  • 22 February 2023 22:52

  In fact, I cannot even update the 'ORGOPTIONALID' standard field via API

  0

  Comment actions Permalink
• 

  Mark Gilmore

  • 23 February 2023 02:45

  Hi Nicholas

  I've just checked the documentation and tested it myself, it seems neither custom fields nor the OrgOptionalID is supported via API, I apologise for this!

  I'll keep this post open to gauge feedback from other users within our community.

  Thanks
  Mark

  0

  Comment actions Permalink
• 

  Nicholas Shorter

  • 23 February 2023 03:11

  Hi Mark,

   

  That's a shame.  I'm not sure why an API would be setup with such restrictions on standard object like this.  Please see related idea here (this relates solely to Organisation objects, which is why I started this idea separately, as it seems unnecessarily restrictive to not have this functionality enabled on standard objects in the API system in the first place.
  
  I'm not sure how big aXcelerate is in terms of number of users, and how many of those would look for/require API functionality, but I can certainly say it limits functionality and our ability to integrate into CRM systems, etc

  0

  Comment actions Permalink

Please sign in to leave a comment.