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”?

What is the line crossing the Pacific Ocean that is shown on maps?

Fitting a mixture of two normal distributions for a data set?

How should I behave to assure my friends that I am not after their money?

MH370 blackbox - is it still possible to retrieve data from it?

STM Microcontroller burns every time

The use of "I" and "we" used in the same sentence and other questions

Counting occurrence of words in table is slow

Why isn’t the tax system continuous rather than bracketed?

Correct spacing in the alignat*-environment

Does the Paladin's Aura of Protection affect only either her or ONE ally in range?

Does ultrasonic bath cleaning damage laboratory volumetric glassware calibration?

Intuitively, why does putting capacitors in series decrease the equivalent capacitance?

What do you call the action of someone tackling a stronger person?

Why does Darth Sidious need bodyguards?

Bash echo $-1 prints hb1. Why?

How risky is real estate?

Find smallest index that is identical to the value in an array

Declining an offer to present a poster instead of a paper

How can Charles Proxy change settings without admin rights after first time?

What happens when your group is victim of a surprise attack but you can't be surprised?

Why do some games show lights shine through walls?

Finding closed forms for various addition laws on elliptic curves, FullSimplify fails even with assumptions?

How many satellites can stay in a Lagrange point?

Is there any set of 2-6 notes that doesn't have a chord name?



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;








2















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:



Unable to import binding 'SforceServiceBinding' from namespace 'urn:tooling.soap.sforce.com'.



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?










share|improve this question




























    2















    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:



    Unable to import binding 'SforceServiceBinding' from namespace 'urn:tooling.soap.sforce.com'.



    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?










    share|improve this question
























      2












      2








      2








      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:



      Unable to import binding 'SforceServiceBinding' from namespace 'urn:tooling.soap.sforce.com'.



      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?










      share|improve this question














      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:



      Unable to import binding 'SforceServiceBinding' from namespace 'urn:tooling.soap.sforce.com'.



      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jun 16 at 20:59









      Daniel BallingerDaniel Ballinger

      76.1k16 gold badges162 silver badges424 bronze badges




      76.1k16 gold badges162 silver badges424 bronze badges




















          1 Answer
          1






          active

          oldest

          votes


















          2














          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.






          share|improve this answer



























            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
            );



            );













            draft saved

            draft discarded


















            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









            2














            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.






            share|improve this answer





























              2














              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.






              share|improve this answer



























                2












                2








                2







                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.






                share|improve this answer















                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.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Jun 16 at 22:12

























                answered Jun 16 at 20:59









                Daniel BallingerDaniel Ballinger

                76.1k16 gold badges162 silver badges424 bronze badges




                76.1k16 gold badges162 silver badges424 bronze badges



























                    draft saved

                    draft discarded
















































                    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.




                    draft saved


                    draft discarded














                    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





















































                    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







                    Popular posts from this blog

                    Category:9 (number) SubcategoriesMedia in category "9 (number)"Navigation menuUpload mediaGND ID: 4485639-8Library of Congress authority ID: sh85091979ReasonatorScholiaStatistics

                    Circuit construction for execution of conditional statements using least significant bitHow are two different registers being used as “control”?How exactly is the stated composite state of the two registers being produced using the $R_zz$ controlled rotations?Efficiently performing controlled rotations in HHLWould this quantum algorithm implementation work?How to prepare a superposed states of odd integers from $1$ to $sqrtN$?Why is this implementation of the order finding algorithm not working?Circuit construction for Hamiltonian simulationHow can I invert the least significant bit of a certain term of a superposed state?Implementing an oracleImplementing a controlled sum operation

                    Magento 2 “No Payment Methods” in Admin New OrderHow to integrate Paypal Express Checkout with the Magento APIMagento 1.5 - Sales > Order > edit order and shipping methods disappearAuto Invoice Check/Money Order Payment methodAdd more simple payment methods?Shipping methods not showingWhat should I do to change payment methods if changing the configuration has no effects?1.9 - No Payment Methods showing upMy Payment Methods not Showing for downloadable/virtual product when checkout?Magento2 API to access internal payment methodHow to call an existing payment methods in the registration form?