Want to get rid of Google Ads, click here.
+ Reply to Thread
Results 1 to 2 of 2

Thread: Visual Basic .NET 2003 and ChangeManagement WSDL

  1. #1
    Senior Member fid509's Avatar
    Join Date
    Feb 2002
    Location
    Brussels
    Posts
    381

    Unhappy Visual Basic .NET 2003 and ChangeManagement WSDL

    Hello,

    I encounter a problem when using the CM WSDL from SC 6.2.7 in VB .NET 2003.
    I can import the WSDL without problem an write a a program around it but when I compile the program if fails because 'RecordId' is already declared as Public Dim RecordId as StringType in this class.

    Turns out "RecordId" the API caption of the field record.id in file cmcalendar which is also part of the WSDL. The name conflicts with a attribute name "recordid" because VB is case-insensitive in variable names. The only solution I can think of is to change the API caption for this field but wouldn't this break the ChangeCalendar? Dit somebody already encounter this problem and found a solution to it?

    Thx,
    Fid509

  2. #2
    Senior Member
    Join Date
    Sep 2008
    Posts
    115

    Default

    Slightly off topic, but any chance you can post your working code for talking to it via .NET? I can talk to SM7 ok via WS using soapUI, but can't get it working via .NET.

+ Reply to Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

     

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts