Subject:External Class : Invalid linking operation Author:Robert Mattax Date:29 Jan 2007 09:08 AM
I am trying to use a custom class for some data manipulation in my XQuery mapping. I am not having any trouble getting my function to show up in the mapper by right clicking and adding my custom class. However, whenever I try to drag any of my data elements to the ports on the function box, it gives me the error: "Invalid linking operation." Any ideas?
Subject:Re: External Class : Invalid linking operation Author:(Deleted User) Date:29 Jan 2007 09:29 AM
Hi Robert,
would it be possible for you to send us the XQuery file? (if it
contains proprietary informations, you can e-mail it to
stylus-field-report@progress.com)
Subject:Re: External Class : Invalid linking operation Author:Robert Mattax Date:29 Jan 2007 01:07 PM
I have sent an email with the necessary files to the address mentioned in the earlier reply.
I attempted adding the example IntDate class as well to my query, just to see if I could get any class to load, and I ran into the same issue. The "J" function block shows up on my mapper, but attempting to drag a source or destination node leads to the error.
Also, if I attempt to input a text value by double-clicking on the port and entering a value, the whole application crashes.
Subject:Re: External Class : Invalid linking operation Author:Tony Lavinio Date:01 Feb 2007 02:53 PM
In the meantime, I went over the files you sent to Alberto, and
noticed something interesting.
You do not need JavaScript extension functions at all.
The Convert-to-XML adapter knows many different kinds of datatypes:
In this file, you have some numbers that are encoded with '{' and
'}' in them. I recognize those as 'Zoned' numbers. In Convert-to-XML,
you can change the 'Source Data Type' from the default of 'String'
to the 'Zoned' value, and they will be properly decoded.
'ChargeOffAmount' is an example of this kind of field. There are many
others.
Similarly, you have a column called 'InterestRate' which most probably
should be rendered as a 'Number' with a scaling factor of -2 for two
decimal places. 'CommissionRate' is also such a field.
And the 'ReceiptDate', 'ContractDate' and 'ChargeOffDate' columns
should be coded as 'Date' in YMD format, and they will be properly
converted into ISO dates. Or they can be left as 'String', if you
want them to be passed through unchanged.
Subject:Re: External Class : Invalid linking operation Author:Robert Mattax Date:01 Feb 2007 02:59 PM
Tony,
Thanks for taking time to look at this as well. I assumed there would be some data transformation for these types, I just couldn't find them anywhere in the documentation. In times past, I've seen them labeled as Packed Sign, or EBCIDIC, and a couple other names. I attempted using some of the other types but came up empty, so I'm glad there was some provision made for these.