GI Webservice Mapping Issue

[362759690]

Hi Everyone,
I'm learning how to use the GI web-service feature.
And I wonder what should I do if the output is "Dataset", I can't bind the "Dataset" to a single element like textbox.
How I can handle this format ?

[mongonv (Ed)]

Your web service should return a data structure for the dataset. If you double click the icon in front of "Dataset" it should open up the mapping to the actual structure. You then map a CDFDocument, record, and field attribute mappings for each field in the data set.

Those fields can then be mapped to components on your forms or matrix layouts. To map to forms you use the CDF Mapping component that provides a form level access to the CDF document created by the mapping or a matrix that provides record list access to the CDF document.

I would suggest you at least skim thru the Component and Developer's guides for a good base understanding of how the mapping process works.

Hope that helps,
Ed

[362759690]

Hi Ed,
Thanks very much for your help.
I have the screenshot on the attachment, could you please help check it.
I understand what you said, but I can't open the structure doubling click the dataset node.
Perhaps I have an invalid wsdl file ?

[mongonv (Ed)]

If your data structure is coming thru from the WSDL properly, then you would double click the _jsx_null_jsx_ line or it should parse to your data structure. But based on that name for the output response, I would guess its not getting a properly parsed WSDL from your source.

Do you get any kind of message if you double click that line? Have you clicked the "Ru;le Node Profile" radio button below the Rules Tree window while the _jsx_null_jsx_ line is selected, that will tell you what it sees as comprising that line.

The response line should be mapped to a CDF Document name, the Result line should contain CDF Record as your mapping type, and the _jsx_null_jsx_ line/section is where your data structure should show up when its properly parsed. But showing a "_jsx_null_jsx_" would lead me to believe there is something wrong there, have never seen a WSDL parse to something like that.