Returning to the old question, your case is basically suitable for implementation, but I noticed that in certain cases, namely in my case with memory modules, this option is not suitable, because it seems that in my network there are computers whose memory modules may not be fully defined, and the reports do not contain the first mandatory field, which I could cling to and on the basis of it consider the script instance
In other words, in AIDA reports, in such sections where there are many devices (monitor, memory modules, network cards, etc.), it is not certain that the first field from the ifield column will always be one for all instances.
It turns out that there may be a case that the first 2 memory modules are modern and AIDA understands them, and the first field uses their name, and the third module may be some unsupported / old module, AIDA does not define it, the field does not create with the name -> and the script breaks down, and the whole point is lost