Unable to import binding 'SforceServiceBinding' with the Summer 19 Tooling API WSDLTooling API – how to use LastSyncDate?tooling API workflow alert updateDeploying a Profile Update via Tooling RESP API - INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITYUser Fields on Tooling APIUsing the Tooling API to create trigger, getting Error No such column 'Email' on entity 'User'Simple SOAP Example in C#Unable to get ApexPageMember ID Tooling APIRetrieving StandardValueSet with the Tooling API.Net Core 2.0 and async/await UsageWhich Summer '19 (v46) sObject types are returning field describe results of soapType “tns:json”?
Definition of 'vrit'
How can I restore a master database from its bak file?
How can I ping multiple IP addresses at the same time?
The Amazing Sliding Crossword
Print 'A' 1000 times with BrainFuck
Name for a function whose effect is canceled by another function?
Make symbols atomic, without losing their type
My student in one course asks for paid tutoring in another course. Appropriate?
How to make all magic-casting innate, but still rare?
Counterfeit checks were created for my account. How does this type of fraud work?
Story of a Witch Boy
Draw a symmetric alien head
Teferi's Time Twist and Gideon's Sacrifice
Synaptic Static - when to roll the d6?
'No arbitrary choices' intuition for natural transformation.
Understanding “en comprend”
Are there examples of rowers who also fought?
Am I legally required to provide a (GPL licensed) source code even after a project is abandoned?
How Hebrew Vowels Work
Is Newton's third law really correct?
How to compute the inverse of an operation in Q#?
Densest sphere packing
What is the most suitable position for a bishop here?
"What is the maximum that Player 1 can win?"
Unable to import binding 'SforceServiceBinding' with the Summer 19 Tooling API WSDL
Tooling API – how to use LastSyncDate?tooling API workflow alert updateDeploying a Profile Update via Tooling RESP API - INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITYUser Fields on Tooling APIUsing the Tooling API to create trigger, getting Error No such column 'Email' on entity 'User'Simple SOAP Example in C#Unable to get ApexPageMember ID Tooling APIRetrieving StandardValueSet with the Tooling API.Net Core 2.0 and async/await UsageWhich Summer '19 (v46) sObject types are returning field describe results of soapType “tns:json”?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I'm trying to update to the Summer `19 (v46.0) Tooling API WSDL in a .NET project.
When I attempt to update the service reference from the v45.0 WSDL I get the following error from MSDiscoCodeGenerator:
Attempting the same conversion from the command line gives:
wsdl.exe tooling_46_0_scratch.wsdl
Error: Unable to import binding 'SforceServiceBinding' from namespace 'urn:tooling.soap.sforce.com'.
- Unable to import operation 'create'.
- The datatype 'urn:metadata.tooling.soap.sforce.com:AnalyticsSettings' is missing.
How can I import this Tooling API WSDL into a .NET project?
tooling-api c# summer19
add a comment |
I'm trying to update to the Summer `19 (v46.0) Tooling API WSDL in a .NET project.
When I attempt to update the service reference from the v45.0 WSDL I get the following error from MSDiscoCodeGenerator:
Attempting the same conversion from the command line gives:
wsdl.exe tooling_46_0_scratch.wsdl
Error: Unable to import binding 'SforceServiceBinding' from namespace 'urn:tooling.soap.sforce.com'.
- Unable to import operation 'create'.
- The datatype 'urn:metadata.tooling.soap.sforce.com:AnalyticsSettings' is missing.
How can I import this Tooling API WSDL into a .NET project?
tooling-api c# summer19
add a comment |
I'm trying to update to the Summer `19 (v46.0) Tooling API WSDL in a .NET project.
When I attempt to update the service reference from the v45.0 WSDL I get the following error from MSDiscoCodeGenerator:
Attempting the same conversion from the command line gives:
wsdl.exe tooling_46_0_scratch.wsdl
Error: Unable to import binding 'SforceServiceBinding' from namespace 'urn:tooling.soap.sforce.com'.
- Unable to import operation 'create'.
- The datatype 'urn:metadata.tooling.soap.sforce.com:AnalyticsSettings' is missing.
How can I import this Tooling API WSDL into a .NET project?
tooling-api c# summer19
I'm trying to update to the Summer `19 (v46.0) Tooling API WSDL in a .NET project.
When I attempt to update the service reference from the v45.0 WSDL I get the following error from MSDiscoCodeGenerator:
Attempting the same conversion from the command line gives:
wsdl.exe tooling_46_0_scratch.wsdl
Error: Unable to import binding 'SforceServiceBinding' from namespace 'urn:tooling.soap.sforce.com'.
- Unable to import operation 'create'.
- The datatype 'urn:metadata.tooling.soap.sforce.com:AnalyticsSettings' is missing.
How can I import this Tooling API WSDL into a .NET project?
tooling-api c# summer19
tooling-api c# summer19
asked 8 hours ago
Daniel BallingerDaniel Ballinger
75.8k16161421
75.8k16161421
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Looking into the v46.0 Tooling API WSDL at the complexType AnalyticsSettings (which is new in v46.0):
<xsd:complexType name="AnalyticsSettings">
<xsd:complexContent>
<xsd:extension base="ens:sObject">
<xsd:sequence>
<xsd:element name="DurableId" minOccurs="0" type="xsd:string" nillable="true"/>
<xsd:element name="FullName" minOccurs="0" type="xsd:string" nillable="true"/>
<xsd:element name="IsInsightsEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsPowerInsightsEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsSmartDataDiscoveryEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsWaveReplicationEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsWaveSharingInheritanceEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsWaveTemplateEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="Metadata" minOccurs="0" type="mns:AnalyticsSettings" nillable="true"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
This is defined in the schema for the "urn:sobject.tooling.soap.sforce.com" namespace. The element "Metadata" with the type "mns:AnalyticsSettings" is in the "urn:metadata.tooling.soap.sforce.com" namespace.
The schema for the urn:metadata.tooling.soap.sforce.com namespace doesn't have a definition for the complexType AnalyticsSettings.
I added a stub for the missing complex type in the urn:metadata.tooling.soap.sforce.com namespace schema.
<xsd:complexType name="AnalyticsSettings">
<xsd:complexContent>
<xsd:extension base="mns:MetadataForSettings">
<xsd:sequence>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
After that I got a similar error for another type:
The datatype 'urn:metadata.tooling.soap.sforce.com:UserManagementSettings' is missing.
So I added that as well:
<xsd:complexType name="UserManagementSettings">
<xsd:complexContent>
<xsd:extension base="mns:MetadataForSettings">
<xsd:sequence>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
After adding those I've been able to generate the integration code from the WSDL.
There would likely be further issues if you tried to use the metadata fields on either of these sObjects.
I've raised support case # 23301433 about getting the WSDL fixed properly.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "459"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f266142%2funable-to-import-binding-sforceservicebinding-with-the-summer-19-tooling-api-w%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Looking into the v46.0 Tooling API WSDL at the complexType AnalyticsSettings (which is new in v46.0):
<xsd:complexType name="AnalyticsSettings">
<xsd:complexContent>
<xsd:extension base="ens:sObject">
<xsd:sequence>
<xsd:element name="DurableId" minOccurs="0" type="xsd:string" nillable="true"/>
<xsd:element name="FullName" minOccurs="0" type="xsd:string" nillable="true"/>
<xsd:element name="IsInsightsEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsPowerInsightsEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsSmartDataDiscoveryEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsWaveReplicationEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsWaveSharingInheritanceEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsWaveTemplateEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="Metadata" minOccurs="0" type="mns:AnalyticsSettings" nillable="true"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
This is defined in the schema for the "urn:sobject.tooling.soap.sforce.com" namespace. The element "Metadata" with the type "mns:AnalyticsSettings" is in the "urn:metadata.tooling.soap.sforce.com" namespace.
The schema for the urn:metadata.tooling.soap.sforce.com namespace doesn't have a definition for the complexType AnalyticsSettings.
I added a stub for the missing complex type in the urn:metadata.tooling.soap.sforce.com namespace schema.
<xsd:complexType name="AnalyticsSettings">
<xsd:complexContent>
<xsd:extension base="mns:MetadataForSettings">
<xsd:sequence>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
After that I got a similar error for another type:
The datatype 'urn:metadata.tooling.soap.sforce.com:UserManagementSettings' is missing.
So I added that as well:
<xsd:complexType name="UserManagementSettings">
<xsd:complexContent>
<xsd:extension base="mns:MetadataForSettings">
<xsd:sequence>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
After adding those I've been able to generate the integration code from the WSDL.
There would likely be further issues if you tried to use the metadata fields on either of these sObjects.
I've raised support case # 23301433 about getting the WSDL fixed properly.
add a comment |
Looking into the v46.0 Tooling API WSDL at the complexType AnalyticsSettings (which is new in v46.0):
<xsd:complexType name="AnalyticsSettings">
<xsd:complexContent>
<xsd:extension base="ens:sObject">
<xsd:sequence>
<xsd:element name="DurableId" minOccurs="0" type="xsd:string" nillable="true"/>
<xsd:element name="FullName" minOccurs="0" type="xsd:string" nillable="true"/>
<xsd:element name="IsInsightsEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsPowerInsightsEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsSmartDataDiscoveryEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsWaveReplicationEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsWaveSharingInheritanceEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsWaveTemplateEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="Metadata" minOccurs="0" type="mns:AnalyticsSettings" nillable="true"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
This is defined in the schema for the "urn:sobject.tooling.soap.sforce.com" namespace. The element "Metadata" with the type "mns:AnalyticsSettings" is in the "urn:metadata.tooling.soap.sforce.com" namespace.
The schema for the urn:metadata.tooling.soap.sforce.com namespace doesn't have a definition for the complexType AnalyticsSettings.
I added a stub for the missing complex type in the urn:metadata.tooling.soap.sforce.com namespace schema.
<xsd:complexType name="AnalyticsSettings">
<xsd:complexContent>
<xsd:extension base="mns:MetadataForSettings">
<xsd:sequence>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
After that I got a similar error for another type:
The datatype 'urn:metadata.tooling.soap.sforce.com:UserManagementSettings' is missing.
So I added that as well:
<xsd:complexType name="UserManagementSettings">
<xsd:complexContent>
<xsd:extension base="mns:MetadataForSettings">
<xsd:sequence>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
After adding those I've been able to generate the integration code from the WSDL.
There would likely be further issues if you tried to use the metadata fields on either of these sObjects.
I've raised support case # 23301433 about getting the WSDL fixed properly.
add a comment |
Looking into the v46.0 Tooling API WSDL at the complexType AnalyticsSettings (which is new in v46.0):
<xsd:complexType name="AnalyticsSettings">
<xsd:complexContent>
<xsd:extension base="ens:sObject">
<xsd:sequence>
<xsd:element name="DurableId" minOccurs="0" type="xsd:string" nillable="true"/>
<xsd:element name="FullName" minOccurs="0" type="xsd:string" nillable="true"/>
<xsd:element name="IsInsightsEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsPowerInsightsEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsSmartDataDiscoveryEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsWaveReplicationEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsWaveSharingInheritanceEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsWaveTemplateEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="Metadata" minOccurs="0" type="mns:AnalyticsSettings" nillable="true"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
This is defined in the schema for the "urn:sobject.tooling.soap.sforce.com" namespace. The element "Metadata" with the type "mns:AnalyticsSettings" is in the "urn:metadata.tooling.soap.sforce.com" namespace.
The schema for the urn:metadata.tooling.soap.sforce.com namespace doesn't have a definition for the complexType AnalyticsSettings.
I added a stub for the missing complex type in the urn:metadata.tooling.soap.sforce.com namespace schema.
<xsd:complexType name="AnalyticsSettings">
<xsd:complexContent>
<xsd:extension base="mns:MetadataForSettings">
<xsd:sequence>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
After that I got a similar error for another type:
The datatype 'urn:metadata.tooling.soap.sforce.com:UserManagementSettings' is missing.
So I added that as well:
<xsd:complexType name="UserManagementSettings">
<xsd:complexContent>
<xsd:extension base="mns:MetadataForSettings">
<xsd:sequence>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
After adding those I've been able to generate the integration code from the WSDL.
There would likely be further issues if you tried to use the metadata fields on either of these sObjects.
I've raised support case # 23301433 about getting the WSDL fixed properly.
Looking into the v46.0 Tooling API WSDL at the complexType AnalyticsSettings (which is new in v46.0):
<xsd:complexType name="AnalyticsSettings">
<xsd:complexContent>
<xsd:extension base="ens:sObject">
<xsd:sequence>
<xsd:element name="DurableId" minOccurs="0" type="xsd:string" nillable="true"/>
<xsd:element name="FullName" minOccurs="0" type="xsd:string" nillable="true"/>
<xsd:element name="IsInsightsEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsPowerInsightsEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsSmartDataDiscoveryEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsWaveReplicationEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsWaveSharingInheritanceEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="IsWaveTemplateEnabled" minOccurs="0" type="xsd:boolean" nillable="true"/>
<xsd:element name="Metadata" minOccurs="0" type="mns:AnalyticsSettings" nillable="true"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
This is defined in the schema for the "urn:sobject.tooling.soap.sforce.com" namespace. The element "Metadata" with the type "mns:AnalyticsSettings" is in the "urn:metadata.tooling.soap.sforce.com" namespace.
The schema for the urn:metadata.tooling.soap.sforce.com namespace doesn't have a definition for the complexType AnalyticsSettings.
I added a stub for the missing complex type in the urn:metadata.tooling.soap.sforce.com namespace schema.
<xsd:complexType name="AnalyticsSettings">
<xsd:complexContent>
<xsd:extension base="mns:MetadataForSettings">
<xsd:sequence>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
After that I got a similar error for another type:
The datatype 'urn:metadata.tooling.soap.sforce.com:UserManagementSettings' is missing.
So I added that as well:
<xsd:complexType name="UserManagementSettings">
<xsd:complexContent>
<xsd:extension base="mns:MetadataForSettings">
<xsd:sequence>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
After adding those I've been able to generate the integration code from the WSDL.
There would likely be further issues if you tried to use the metadata fields on either of these sObjects.
I've raised support case # 23301433 about getting the WSDL fixed properly.
edited 7 hours ago
answered 8 hours ago
Daniel BallingerDaniel Ballinger
75.8k16161421
75.8k16161421
add a comment |
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f266142%2funable-to-import-binding-sforceservicebinding-with-the-summer-19-tooling-api-w%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown