It has served me well, Chuck.
So, I did a quick test using an already exported Ss4 XML element template and it seemed to run OK.
What surprised me was that the spreadsheet did not contain the full XML information for Terrain Element Templates.
Interestingly, If you use Excel to Get External Data from XML, the result does contain the extended terrain settings. Also, the result is very similar, but with more columns and less informative column headers. It is a capability I have explored in the past with XIN files (which has too many nodes, so only sub-areas can be explored)
I have not tried to re-import - I need to review the steps.
This process screams for a PDF handout and a nice PPT, BTW.
P.S. Not to hijack my own thread, but where does the variable $(_DGNLIB) come from? In one of the examples I tried, the Material Type contained the following:
$(_DGNLIB)|Materials_Imperial.dgnlib|Bentley-Civil.pal