2

I am attempting to do web reference of Tooling WSDL in MS Visual studio but I am unable to do so. I am getting below error: enter image description here

Is there any fix? I have tried it in different version of MS Visual Studio but no luck.

3

I had to modify the namespace of AuraDefinitionBundle to get it to import correctly with the Spring '17 (v39.0) Tooling API WSDL.

Under <xsd:complexType name="AuraDefinition">

Change

 <xsd:element name="AuraDefinitionBundle" minOccurs="0" type="ens:AuraDefinitionBundle" nillable="true"/>

To:

 <xsd:element name="AuraDefinitionBundle" minOccurs="0" type="mns:AuraDefinitionBundle" nillable="true"/>

All I did was move the AuraDefinitionBundle from the ens ("urn:sobject.tooling.soap.sforce.com") to mns ("urn:metadata.tooling.soap.sforce.com") namespace.


Generally speaking the Tooling API is full of all sorts of fun oddities.

One of the best is the usage of xsd:import at the start of each schema. Essentially each Namespace imports the other two. It creates all sorts of problems with name conflicts with strongly typed languages.

What the xsd:imports look like in the Tooling API wsdl Tooling API xsd:imports

See also:

  • WOW just work like a charm. – Avijit Mar 9 '17 at 14:51

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.