02-20-2013 07:18 PM
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 😞
02-20-2013 11:20 PM
02-21-2013 02:45 PM
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.
02-28-2013 07:56 PM