Passing this information on, maybe it will help someone avoid an issue down the road.
I modified an existing Explorer by adding a couple of columns and wanted to alias the column names (was adding elements that were dependent on the customer's main address and I wanted that to be clear in the column's name). For the aliased name, I used parenthesis to clarify which element it was sourced from. This is a problem with the way the Explorers are coded to construct the XML that gets passed over to any of the Manage tasks and results in the Explorer crashing.
In my case, it was the Sales Order Line explorer that I added an aliased column of...
CustPriceGroupID(Main Addr)
and it crashed when selecting Manage>View/Edit Sales Order.
The Explorer code needs to be encoding these values to allow for special characters to be used when constructing the XML. Until Sage fixes that bug, you will want to avoid using parenthesis (and any other special characters that fall into this group) in any aliased column names that are used in Explorers when they may interact with a Manage task.
