Is there a way to import an XML file from local env with transaction group configuration through scripting?
Yes. As long as you are sure the named group doesn’t exist. There’s no enumeration of existing transaction groups. ):
I see system.groups.loadFromFile
and system.groups.removeGroups
but I don’t understand how to build an XML to import that configuration into Transaction Groups.
Exporting TG configuration gives me a .zip file with some .json files which don’t have the configuration I need. What I am missing?
You can export to XML. Right click the TG you want to use as a template, then ‘Export’. NOTE: There are 2 export options in the menu, use the bottom one to export XML (8.1.7) on my test VM.
You must hold down Shift and right click in the newest versions.
How do you have 8.1.7? I'm using one of Ignition's latest version that can be downloaded from the website:
I will download 8.1.16 today.
Some screenshots:

I'm still not able to find that option.
Don't open the export dialog. Shift-right-click on the transaction group in the designer tree.
I missed it so many times that I was going to post a crying face.
Since it’s called Legacy Export, are there plans to remove it? Is there a better way?
I’m hoping the storage format switches to XML directly, similar to what was done with named queries.
No plans to remove it, we just generally wanted to discourage people from getting confused between resource-specific export formats and the more general project import/export mechanisms.
This only seems to work if I select a SINGLE trx group or folder ... not if I select top level "Transaction Groups".
The "Legacy Export->to XML" appears and prompts me for a file, but nothing is created.
Is this intentional? Is there a way to export all transaction groups to XML?
Thanks.
-Shane
Not exactly, but no one has ever made it work for folders/the top level, and we have no plans to do so.
Not currently, though theoretically you could script something in the designer console that does it. I wouldn't really want to go down that road, though.
What are you trying to do with these XML imports, exactly?
In some future release, we're planning to migrate the storage format for transaction groups to that XML representation directly - then you would be able to manipulate them on the filesystem like most other project resources, as well as import/export them more easily using the standard mechanisms in the designer.
The internal ticket for that effort is IGN-8872; I've added this thread to our list tracking customer demand for the rework.
I'm facing an issue with a client who has 1000+ trx groups.
I'm trying to export everything to XML so I can scrape the data for which tags, databases, tables, columns, indexes are being used.
-Shane
So, I tried highlighting all the folders and legacy exporting that way, and it worked. So that's good enough.
Thanks.