Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

displayLocationInDecimal missing in WSDL #8

Open
ttomaszewski opened this issue Feb 14, 2023 · 3 comments
Open

displayLocationInDecimal missing in WSDL #8

ttomaszewski opened this issue Feb 14, 2023 · 3 comments

Comments

@ttomaszewski
Copy link

The Metadata WSDL is missing the following tag element, which is causing the readMetadata method to fail when using the SOAP Metadata API.

com.sforce.ws.ConnectionException: unable to find end tag at:  START_TAG seen ...</fullName><displayLocationInDecimal>... @305:5283

This was reported in December in Trailblazer - https://trailblazer.salesforce.com/issues_view?id=a1p4V000002ML1YQAW&title=attribute-displaylocationindecimal-is-not-available-in-metadata-wsdl

@gbockus-sf
Copy link
Contributor

Howdy. Is this the element which is missing when looking at the org WSDL?

@ttomaszewski
Copy link
Author

ttomaszewski commented Feb 15, 2023

Howdy. Is this the element which is missing when looking at the org WSDL?

@gbockus-sf Yes, however, when I download the Metadata WSDL via Setup > API from my Org, this element is missing...

It is the same API version

<!-- 
Salesforce.com Metadata API version 57.0

Copyright 2006-2023 Salesforce.com, inc. All Rights Reserved
 -->
<definitions xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://soap.sforce.com/2006/04/metadata" targetNamespace="http://soap.sforce.com/2006/04/metadata">

@gbockus-sf
Copy link
Contributor

gbockus-sf commented Feb 15, 2023

@ttomaszewski understood. In order to get an answer on the in org WSLD you'll have to open a support investigations with Salesforce. Here we take the values in source and provide it in the repo, but don't have any insight into how the org generates the WSDL shown when accessed via that route.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants