The first one has the advantage that tHashOutput_1 never changes its name, but the disadvantage that if you've given tHashOutput_1 a meaningful name then you have to hunt around clicnking on all your tHashOutput components to find the right one. The latter has the advantage of matching what is on the canvas, but the disadvantage that if you get around to giving row1 a meaningful name, then your code breaks.
I'm thinking of building a tool that scans an export and loads all this information into a spreadsheet or database, and attempts to search for and correlate all the globalMap references to the links and components that they refer to. Sadly I'm not on this project much longer and probably will not be using Talend on my next project so this will not happen for a while.
That's an interesting idea. You could use the .item files to do this. They XML files, so you could quite easily build a job in Talend to do this. I have written jobs to do similar things in the past.
It should be pointed out that the component names don't actually change. You are simply assigning a label which is just for ease of reading. I agree, it can be frustrating when searching for which component the globalMap value is coming from though.
