Error while calling COM objects method - RTC

sridhar
sridhar Member Posts: 171
edited 2009-10-14 in NAV Three Tier
Hi,

I am getting an error message "This message is for C/AL programmers: The call to member TextCase failed: Method
Adapter.AddressService.ValidateRequest.TextCase not found"

Where TextCase is of type Enum.

Actually the codeunit I am using is calling a method of COM object (dll) which in turn calls the webservice method.

I am not seeing this kind of error message in the Classic Version. Please guide me to resolve this error.

Thanks,
N.Sridhar

Answers

  • sridhar
    sridhar Member Posts: 171
    Any idea on this issue?

    Additional Info: TextCase is of Enum type at the dll side and I am passing integer value to the TextCase at the Nav end.

    Thanks.
  • sridhar
    sridhar Member Posts: 171
    Is this issue is because of the Enum datatype used in methods of dll?
  • Tatevik
    Tatevik Member Posts: 28
    hi did you resolve your problems with working with events?
  • sridhar
    sridhar Member Posts: 171
    I haven't resolved...I haven't tried working with event too..
  • Tatevik
    Tatevik Member Posts: 28
    mm it's pity, I suppose from your topic we have same problems. I hope you will be able to help, anyway thanks a lot
  • xyz123
    xyz123 Member Posts: 7
    enum is not supported in the RTC. you will have to create a new function/method in the DLL which takes/return integer values instead of the enum
  • sridhar
    sridhar Member Posts: 171
    ah...unfortunately enum variables place a major part in the methods of dll...
    any ways thanks for the reply.
  • PhilThome
    PhilThome Member Posts: 5
    I have a similar problem...

    First time I've encountered it was while using a StringBuilder as a parameter for calling an automation method:
          public int decodeToFile(StringBuilder base64String, string filename)
        {...}

    There's no problem using this function with the classic client. It works. Calling it on the RTC it leads to the error "method not found". It did work some time ago. But something changed and since then it doesn't work anymore. So I've changed the method signature to
            public string decode(Object base64String, string filename)

    Casting the object to string in the method stub. Works fine.

    Today I've tried to use another automations library, which is rather large on the RTC. Most of the funtion have a signature like this:
            public string getProperties(out PropertyQueue properties)

    where PropertyQueue is an automation of its own. Using this on the classic client works fine. On the RTC again the error message. It seems to me, that the Service Tier does not support complex data types as parameters besides "Object". If there were only one or two methods, I'd change them using Object, but there are plenty of them and I'd like to keep the type safety.

    Another thing that doesn't work on the Service Tier is overloading methods.

    Is there any solution / suggestion for this problem?

Categories