Hi Tom, were you logged in to the same company in which you created the report? Make sure you are opening in the right company.  

If the templates were created in an older version maybe some of the newer functionality does not work for the older template. With that said, I don't think saving the report should affect the report so maybe contact tech support to see if there are others issues involved.

Sandra.

Same company.  Yes.

I don't think that just saving it should be a problem either.   Has to be something in the environment causing it,  but what I don't know.

Hi Tom.

I'm not sure if this will work but have you tried un-linking the template first so that you can select the template type you want to save the workbook as. Maybe see if saving as xlt and xltx makes a difference.

Another thing to try is open the template in design mode and check the format of the column that is giving the problem. You could then also check the format of the expression in the container.

Hi Tom,

Peter is correct.  After you save the changes, the standard procedure is to re-link the template to the report in Report Manager.  Have you followed that process and still having issues?

Yes.   Poor wording on my part.  By saving,  I meant relinking.   The strange thing is that it is not a single column or cell,  but virtually the entire spreadsheet gets a formatting change?

I have not tried unlinking and then relinking or changing as xlt vs xltx yet.

On the last try we found that on the first relink during a session everything looks good, but on the second relink things blow out.

sometimes the Excel version might cause the issue.  try save the excel to 2007 and re-open then relink.

also, it is best to open the Excel locally rather than open over the network.  it happens to me.

Saving with Excel 2007 is not an option.  Only 2010 is available.

Can you define locally?

Tom - I used to have lots of trouble with the templates getting corrupt if I didn't choose unlink first and then relink.

I haven't had that problem in 2014 with 2010 but it might be worth trying.