From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
G Web Development Software
More new user questions
Solved!
Sorry for the simple questions, but I'm not familiar with NXG and its way of doing things, and I'm not familiar with LabVIEW's Unflatten from JSON. (I always use Dr. James Powell's JSON library for LabVIEW.)
1) Easy question: How do I resize the array of strings (going into the top of the Unflatten from JSON) so that it shows two elements? If I try to resize it, it just resizes the string.
2) Why isn't the "type/defaults" on Unflatten from JSON adapting to my input cluster? I also tried not wiring in the "path", but that didn't help.
3. I also tried just wiring in the path to one of my items, which is the "array of readings" in my example above. It will let me wire in an array of cluster of string and reading, but when I run, I get the undocumented -375006 error. Any idea what's wrong?
Thanks.
For resizing the array to show more elements, I was doing it right, but didn't realize it. The separator between elements is very subtle... off-white on off-white. Since I was expecting it to look more like traditional LabVIEW, with a clearer visual differentiation, I just thought I was resizing the string.
For those who don't have the software, here's an example of an array showing two strings.
2) Why isn't the "type/defaults" on Unflatten from JSON adapting to my input cluster? I also tried not wiring in the "path", but that didn't help.
The Unflatten from JSON / Flatten to JSON primitives do not support the Timestamp data types. This is because the JSON format itself does not support date/time formats. The recommendation would be to instead use a cluster that directly maps to the JSON object format (so that value is likely one of string or number, etc) and then after parsing the JSON data you can post process it to do the appropriate parsing of how the JSON originator chose to format dates into strings, numbers, etc.
It should go without saying--but I'll say it anyway--a clearer error message would be so much more helpful here.
