I’m curious as to why the transaction groups export to xml and not csv or have a csv export option.
Roughly, the short answer is “because it was easier and fit the data better”. Unfortunately, I know it’s not as user friendly. From the very first release of Ignition we had intended to put CSV format back in for groups, but never got around to it. We were never all that happy with the CSV format of FactorySQL, but I guess it was at least functional, so we probably should have just ported that over for backwards compatibility at least.
I’m not sure what the timeline would be on this, but we definitely know it’s something that people want.
We have approximately 400 expressions to input. Although a little cross eyed, it’s not as bad as initially anticipated. In any case, a csv would be quicker to edit and less prone to the possibility of errors. Did consider a gateway script but opted for the transaction group.
At one point, I had made some python scripts that helped automate the creation of xml files, but I don’t know where they’re at… if I look around I might be able to find them. Using something like that, or macros in your text editor of choice, could help a lot. If you just had an expression per line, you could have a macro run through them and wrap them in item xml or something.