function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Erik RodgersErik Rodgers 

Custom fields not accessible through API on opportunity

We have added several new custom fields to the opportunity object, yet none of these fields are accessible via the API or our Jitterbit Middleware tool. The tool uses a user who is assigned a profile called System Integration. This profile has edit capabilities on each of the new fields. Is there any other reason these fields would not be accessible through SOQL?
Best Answer chosen by Erik Rodgers
Erik RodgersErik Rodgers
It turns out there was a metadata refresh in Jitterbit that was not occuring. Once Jitterbit refreshed, the field were accessible. Our fault.

All Answers

Sumitkumar_ShingaviSumitkumar_Shingavi
What's the error it is throwing? Are these fields deployed through metadata or manually created?

 
Erik RodgersErik Rodgers
The field were manually created. They simply do not display for selection in our Jitterbit tool, but I also assume they are unavailable for SOQL and would likely through an error. Jitterbit is just doing a getDescribe to determine which fields are available for selection. It has a wizard for building SOQL to pull data from Salesforce.
Mohit Bansal6Mohit Bansal6
Erik

Is meta data API enabled for the "System Integration"? Kindly verify once.


Please mark this as solution by selecting it as best answer if this solves your problem, So that if anyone has this issue this post can help
 
Erik RodgersErik Rodgers
It turns out there was a metadata refresh in Jitterbit that was not occuring. Once Jitterbit refreshed, the field were accessible. Our fault.
This was selected as the best answer
JeeTJeeT
in Profile Administrative Permissions is "API Enabled" is enabled ?