Exporting to XML

[Shane]

Until now I have believed that exporting and importing using XML is a good
method to erradicate errors in a work plan and also a way to manually migrate
a work plan from Project Server 2003 to 2007.

Today I came across an issue with hours spreading in a work plan during an
import to server . Whilst I could not pin point the point of failure during
the import to server, I then checked export process locally.

To do this I exported the file to XML and then reimported it into MSP 2003
locally. This showed the hours spreading the same as in MSP 2007.

To further test, I then exported the "correct" version of the plan to .mpd.
I then opened this in MSP 2007 and the hours looked correct.

I suppose my question now is can anyone explain this behviour. Does
something happen in XML that causes this?

If this remains a problem, I need to rethink some of our troubleshooting
methods.

Thanks in advance,
Shane

 

[Gary Chefetz]

Shane:

The best thing to do is capture environmental facts such as system specs and
application patch levels and write down the steps to reproduce, and open a
case with Microsoft. Yours is not the only report I've head of bad data
generation in the XML translation process, so this may be a known issue, but
not a published one.