Hey everyone I've been seeing this a lot lately and am trying to figure out why this error is thrown when querying the SOAP API directly. I've tried several very basic SOQL queries such as
SELECT Body FROM AssetFeed
Only to be met with the
sObject type 'AssetFeed' is not supported. error.
The account that I'm currently querying is just a standard user who accepted permission from an app that was created by a Developer Account, so I'm wondering if it might be permissions from the user or permission from the app itself? Possibly because Developer accounts cannot use 95% of whats offered?
The WSDL used is a v27.0 generated Partner WSDL if that helps narrow it down.
I've noticed this in multiple standard objects, so I'm wondering what the trend really is? Seems like a good informational question for future googling of others?
Array (  => AggregateResult  => Attachment  => ChatterActivity  => CollaborationGroup  => CollaborationGroupFeed  => CollaborationGroupMember  => CollaborationGroupMemberRequest  => CollaborationInvitation  => ContentDocument  => ContentDocumentFeed  => ContentDocumentHistory  => ContentDocumentLink  => ContentVersion  => ContentVersionHistory  => EntitySubscription  => FeedComment  => FeedItem  => FeedLike  => FeedTrackedChange  => Group  => GroupMember  => HashtagDefinition  => Name  => TaskPriority  => TaskStatus  => User  => UserFeed  => UserPreference  => UserRecordAccess  => UserRole )
Where would all the rest of my SOAP SObjects be? This seems like a very thin list compared to the 295 SObjects advertised in the documentation