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

Implementation of the Jacobi Symbol in C

Counterfeit checks were created for my account. How does this type of fraud work?

Is there a term for the belief that "if it's legal, it's moral"?

Make symbols atomic, without losing their type

Why isn't my calculation that we should be able to see the sun well beyond the observable universe valid?

The Amazing Sliding Crossword

Would a 7805 5 V regulator drain a 9 V battery?

Can a character learn spells from someone else's spellbook and then sell it?

What is the "ls" directory in my home directory?

What is this airplane that sits in front of Barringer High School in Newark, NJ?

What is that ceiling compartment of a Boeing 737?

Teferi's Time Twist and Gideon's Sacrifice

Why are there no file insertion syscalls

Is declining an undergraduate award which causes me discomfort appropriate?

Why is Havana covered in 5-digit numbers in Our Man in Havana?

King or Queen-Which piece is which?

Need help understanding the double sharp turn in Chopin's prelude in e minor

A conjecture concerning symmetric convex sets

In a list with unique pairs A, B, how can I sort them so that the last B is the first A in the next pair?

Understanding “en comprend”

Why is it 出差去 and not 去出差?

What mathematical theory is required for high frequency trading?

How to write a nice frame challenge?

If the mass of the Earth is decreasing by sending debris in space, does its angular momentum also decrease?



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 9 hours ago









      Daniel BallingerDaniel Ballinger

      75.8k16161421




      75.8k16161421




















          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 8 hours ago

























                answered 9 hours ago









                Daniel BallingerDaniel Ballinger

                75.8k16161421




                75.8k16161421



























                    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

                    ParseJSON using SSJSUsing AMPscript with SSJS ActivitiesHow to resubscribe a user in Marketing cloud using SSJS?Pulling Subscriber Status from Lists using SSJSRetrieving Emails using SSJSProblem in updating DE using SSJSUsing SSJS to send single email in Marketing CloudError adding EmailSendDefinition using SSJS

                    Кампала Садржај Географија Географија Историја Становништво Привреда Партнерски градови Референце Спољашње везе Мени за навигацију0°11′ СГШ; 32°20′ ИГД / 0.18° СГШ; 32.34° ИГД / 0.18; 32.340°11′ СГШ; 32°20′ ИГД / 0.18° СГШ; 32.34° ИГД / 0.18; 32.34МедијиПодациЗванични веб-сајту

                    19. јануар Садржај Догађаји Рођења Смрти Празници и дани сећања Види још Референце Мени за навигацијуу