Jump to content

LVOOP to XML misleading behaviour


Recommended Posts

Hi all,

I have been working on a project that warranted saving data as XML. I am using LV 8.5 and have implemented LVOOP classes in the project and developed the code to flatten the class data (actually an array of classes) to xml. No broken wires and things are going fine. When I started testing, I found that LV could write the flattened (array of classes) to an xml file that I could open in a browser and confirm was a complete record of the class array. Unfortunately, when I tried to unflatten the xml file I got nothing. After a little investigation I discovered the following:

In LV 8.5 you CAN'T wire a class to the flatten to XML primitive.

In LV 8.5 you CAN wire an array of classes to the flatten to XML primitive.

post-4848-1201759094.jpg?width=400

Here is the resulting XML string output.

post-4848-1201759181.jpg?width=400

And when you try to unflatten the XML data you get the following msg.

post-4848-1201759234.jpg?width=400

Overall I have found the inconsistant behaivour quite annoying, and the de-bugging time was frustrating also. Incidently, in LV 8.2 you cannot wire either a class or an array of classes (as above) to the flatten to XML primitive. Which agrees with the error message that is displayed in LV 8.5.

Just something for you all to be aware of.

Cheers & Beers

:thumbup: :beer:

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.