>> I beg to differ with you that the problem >> is one of truncating and not importing. >> UFT source localities do not currently >> import to TMG at all. In ver 4.0a, they >> did and went into a field that was too >> short (second location). In ver 4.0c and >> d they do not import.
You're mistaken.As you have no doubt heard by now, the difference between the behavior you were seeing and that we were seeing was the setting of an import option ("[ ] Import Source Categories, Components, and Templates").
It is true that I mistakenly thought that the data was being truncated because your example ending with a comma.In fact, with that option off, it imported it without truncating it.
But the file that we sent you today import the localities regardless of the setting of that option.