You need to sign in to do that
Don't have an account?

sObject type 'Opportunity' is not supported.
Hi all
I'm executing this query from Java code using REST service:
SELECT Id, Name, StageName, Amount FROM Opportunity WHERE AccountId = 'xyz' AND OwnerId = 'abc'
I have System Administrator role, View All permission, Object level full permission on Opportunity object, all field level permissions on Opportunity fields.
Still i'm getting this error:
sObject type 'Opportunity' is not supported. If you are attempting to use a custom object, be sure to append the '__c' after the entity name. Please reference your WSDL or the describe call for the appropriate names.","errorCode":"INVALID_TYPE"
can you please suggest what i'm missing
I'm executing this query from Java code using REST service:
SELECT Id, Name, StageName, Amount FROM Opportunity WHERE AccountId = 'xyz' AND OwnerId = 'abc'
I have System Administrator role, View All permission, Object level full permission on Opportunity object, all field level permissions on Opportunity fields.
Still i'm getting this error:
sObject type 'Opportunity' is not supported. If you are attempting to use a custom object, be sure to append the '__c' after the entity name. Please reference your WSDL or the describe call for the appropriate names.","errorCode":"INVALID_TYPE"
can you please suggest what i'm missing
Can you check if you have 'API Enabled' at the profile level? If you are using the standarad 'System Administrator' profile, then this should be enabled by default.
yes i'm 'API Enabled' at the profile level. Still getting this error.
"sObject type 'Opportunity' is not supported."
yes, full access to read/edit Oppportunity object.
same code is working in production but not in sanbox.
I have verified that user permissions/role are same in both production and sandbox.
what could be wrong with the sanbox?
thanks.
Facing the same issue: Making REST request from Java code fails with "message" : "sObject type 'LoginEvent' is not supported.", Developer console query when unchecked box tooling api works.
Please update if anyone has figured out a solution to this.
This issue is has happened on my team a few times.
The solution that works for us is unchecking the "Use Tooling API" checkbox next to the "Execute" button, within the "Query Editor" Tab.