Cannot fetch new standard objects added to API versions after 32.0

[Tosakai2]

Hi,

I had below error and can not process but this object/table was existing.
Please let me know how to avoid this.

Thanks,
Sakai

2018-08-31 10:12:16,154 thread1 DEBUG src:Sandboxberry.MainForm - Progress message: Unexpected error: INVALID_TYPE: sObject type 'ServiceTerritory' 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.

[codeulike]

Hi, I'm not sure why this isn't working. I see that ServiceTerritory is a farily new Salesforce object, part of the new Field Service Lightning product.

Check that 'Field Service Lightning' is enabled in your Org

Check that the login you are using has access to the ServiceTerritory object.

If neither of those are the problem, then I'm not sure what to do.

[Tosakai2]

Hi,

Thank you for your comment and update.
I was already checked both and some Field Service Lightning object can not access.
I love your tool and use to deploying test environment among Field Service Lightning Org.
Please confirm!

Thanks,
Sakai

[Tosakai2]

Hi,

Is there any update?
If I can access other objects that I can not access right now I can introduce your tool to another Japanese customers!

[Tosakai2]

Hi,

I found that "PersonAccount" objcet this is not NEW one and very traditional one can not transform from production to sandbox with same error so I guess any fetch process is not correct.

[tonyeggers]

Same issue with standard objects such as PersonAccount, WorkOrder, Address, etc ... Any chance this could be fixed?

[codeulike]

A few different things going on here I think.

PersonAccount is not a real object - if you have the 'Person Accounts' feature enabled, the actual data is in Contact and Account. PersonAccount sometimes shows up in the list of available objects but it doesn't hold data, its there as a sort of placeholder for other metadata like RecordTypes and page layouts for the 'Person Account' feature - see https://salesforce.stackexchange.com/a/164223/4126

ServiceTerritory was added in API version 38.0
WorkOrder was added in API version 36.0
Address was added sometime after API version 38.0, not sure when

SandboxBerry is quite old now and was built with Partner Web Services API Version 32.0

Probably whats going on is that even though the 'Partner' API doesn't have object definitions baked into it (like the Enterprise API does) it still only lets you access objects from that API version.

So probably the fix would be generate new Parter API WSDL inside Salesforce (in the Setup/API bit) for the latest API version or whichever you need, stick the wsdl file on top of "SandboxberryLib\SalesforceWsdl\partner.wsdl", refresh the Web Reference in SandboxberryLib that points to that .wsdl file, and then re-build. I will try and get around to it if I have time.