Save is save -- I simply highlighted the fact that unless you save the file the resolved links will not be *permanently* updated.
And yes, there is the potential for a performance impact which is why MAP is a better solution to use than SEARCH.
I cannot speak for earlier versions of Solid Edge, but I tested both SEARCH and MAP in ST8 to confirm if the links would be permanently updated once saved before posting that it worked.
Once the Linkmgmt.txt file is set, use the OpenSave utility to save them with their correct links.
There is a consideration for the use parts with duplicate names can interfere with the results .
It's in the custom folder and my understanding is it's a utility to bring files up to the current SE version.
@12GAGE As Bruce has said it is in the Custom folder and it has a few different functions around batch opening and saving files. So if you had alot of files with bad links due to randomly moved files, you could get your Linkmgmt.txt file set and the use the OpenSave utility to fix the links by it opening and saving each file in a folder structure in batch.
If the files were part of a structured move, or the result of a server name change, then redefine links is the way to go, but you must have the old path and the new path but it works in batch mode also.
@KennyG My (very possibly faulty) understanding is that Insight managed SE doesn't use the linkmgmt.txt file although unmanaged would. I asked this before but is foldermap.txt the analog to linkmgmt.txt in the managed environment?
@bshand You are right that Insight does not use the Linkmgmt.txt file but instead finds moved files natively, and even files that have been renamed!. The job of the foldermap.txt is when importing unmanaged files into Insight and maps unmanaged file locations to the corresponding Insight managed location.
Makes sense, in fact I just used foldermap for the first time in an extensive way to restore a large assembly to our database. Rather a PITA, actually.
Anyway, to take issue with your statement that Insight will find files that have been renamed in the case of doing so outside of the "system" of SE, RevMan, Sharepoint and such. Files moved around with Win Explorer, for example, can become problematic in terms of broken links even if done within and between the sql folders although some have argued otherwise.
@bshand Insight is reliant on that SEDocID. If that gets duplicated because of a copy or removed because of a move, then you will have issues. And I beleive that there is an issue of indexing... If you attempt to open a file with links that were recently moved/renamed and they haven't been indexed yet, then you will also have problems, but if you wait a while then you won't have a problem.