Deserialising JSON with variable property names using JKI JSON

[DavidFCannock]

Yeah like I was saying, the only VIM I had in my project was one from JSON Text (something like "Find Item (by LV Type).vim"). Replacing that with "Find Item.vi" and parsing the JSON string it returns as a fractional number was the only change I needed to make to allow VIPM to build my package successfully. I also confirmed this by rolling back to a previous commit before I'd started using JSON Text.

Really lucky it was that too. If I wasn't aware of this issue VIPM has with VIMs and I'd made tons of changes between this release and the last, I might have been stumped trying to figure this out for hours or days. "Error 10 occurred at New VI Library.vi" really doesn't give you a lot to go on.

 

[drjdpowell]

As a workaround, you can use the (off pallet) “JSON Text to Variant” that is called inside the VIM and does the actual work.   But also, make a bug report to JKI, with simple example if possible.  I provided the simple example that JKI used to debug the problem — perhaps it was too simple!

[DavidFCannock]

As I mentioned in the original post, I'm already using a workaround I'm happy enough with ("Find Item.vi" -> "Fract/Exp String To Number.vi").

I'd also love to report this to JKI but their forums are really awful. For one thing it doesn't even let you register your account over a secure connection. I bit the bullet and registered anyway (I use a unique password for each site so at least there's that) and got an email saying that they don't have an automated system in place to handle registrations, so an admin would need to review it. Now that I think about it, I'm sure I tried to sign up to JKI's forums months or maybe years ago, and yet nothing.

I'll report this if/when my registration succeeds.

[drjdpowell]

I've come across the exact same bug, and have found a minimal test case (attached).   It is a VI, calling a VIM, that itself calls another VIM that causes Error 10 in VIPM.   I will make a bug report to JKI.   Work around (for JSONtext) seems to be to avoid this (which I think I can do easily enough).  

Added: JKI bug report: #13909

[DavidFCannock]

Nice to know, thanks.

I'm actually trying to build a VIPM package for a library I've just finished developing, but it fails with this error:



JKI's error messages are as helpful as ever. I use "Stall Data Flow.vim" in my library but that's it. No VIMs being called from other VIMs, and a different error message that appears right at the end of the build process. Likely unrelated to VIMs.

I'd like to be able to see your bug report, but unfortunately it requires me to sign in to view it. Here's a picture of me still waiting for JKI to authorise my forum registration request from last year.



For what it's worth, I tried looking at their member page to see if my account was at least listed there, but that didn't work either:

[Jim_Kring]

Thanks for reporting the issue where VIPM throws an error building packages with VIs calling VIMs. We've been able to reproduce and fix this issue. It's confirmed to be fixed in VIPM 2018 Beta, which has been released along with the LabVIEW 2018 Beta. Please contact us if you would like to gain access to the beta.

[Jim_Kring]

We've been working to resolve some IT issues. Thanks for your patience. If you need some support for your issue, you can contact us directly.