LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Vestigial fields when exporting shared variables

Hello,

 

Is this a bug? I have a network-published shared variable that used to have aliasing enabled. After I cleared the "Bind to:" field and disabled aliasing, I exported its library into CSV mode. However, it still contained the columns (among others):

Network:ProjectBinding = TRUE

Network:ProjectPath = <old variable that it was bound to>

 

The extra columns messed up my CSV parser. The only way I could find to prevent their appearance was to delete all the variables that used to have project binding, and re-create them 😞

Certified LabVIEW Developer
0 Kudos
Message 1 of 4
(2,469 Views)

Forgot to add: I'm using LabVIEW 2012

Certified LabVIEW Developer
0 Kudos
Message 2 of 4
(2,457 Views)

JKSH,

 

I was able to reproduce the same issue here.  I'll look into this a little more and see if this may in fact be a bug.  

James K.
National Instruments
Applications Engineer
Message 3 of 4
(2,434 Views)

Hi James,

 

Thanks for looking into this. Any updates?

Certified LabVIEW Developer
0 Kudos
Message 4 of 4
(2,403 Views)