• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Integration / Customization IPA/ProcessFlow

XML Builder help

 3 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
PFneo
Send Private Message
Posts: 5
8/4/2009 4:44 PM
Hello everybody!  I'm having some trouble getting an XML Builder to parse some XML input that I give it.  I'm using the SQL Query node to pull data out of the LSAUDIT table in logan, when I'm evaluating the R_BEFORE & R_AFTER columns, I'm using an XML Builder node to parse the data.

I have verified that the XML Node is configured correctly, but I'm not sure about the XML Schema file - attached is what I'm using:

The problem is that no data is being parsed out.  I created an email node to show what values are parsed, and nothing was stored in the variables. 

I have attached a word document with screenshots from my XML Builder node, and the email that displayed the output.

Any ideas?  Any help would be greatly appreciated!

Thank you!
Attachments
David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
8/4/2009 5:03 PM
The Input value should be the output from your SQL Query. The schema file might be okay but if you're not referencing the data from the SQL Query there's nothing to parse.
David Williams
PFneo
Send Private Message
Posts: 5
8/4/2009 5:11 PM
Thank you for the response.  I initially thought that was the problem too!  What I have in there is what was loaded in by default.

I changed the input again to give it another test and I recieved a workunit error that says, "Illegally formed XML syntax" - which I'm assuming is the change I made to the input.

Maybe my syntax is bad.  I put in:
SQLQuery2060_R_BEFORE   ......  but with the defined variable tags for ProcessFlow around the var name.  This forum would keep that information in this reply.  Should those be there or not?
<!--LQuery2060_R_BEFO-->

Is that incorrect?
PFneo
Send Private Message
Posts: 5
8/4/2009 5:17 PM
nevermind, I tested and the XML builder isn't looking for the var tags. That's what generated the error, I took them off and tested with success. I feel like a goof, I could have figured this out - but kept banging my head on the wall with the default way the input was loaded. Thanks for the help!!