View ProjeQtOr On SourceForge.net
ProjeQtOr - Project Management Tool
Support us on Capterra
OIN - Open Invention Network
ProjeQtOr free project management software - Problem with the export MS Project XML - Page 2 - ProjeQtOr
 
 

Problem with the export MS Project XML

More
08 Oct 2013 10:01 #7 by Garden Dwarf
Hello,
I have the same with MS Project 2010 when trying to open the xml file (export from Project'Or RIA 3.4.4). If something has been made to solve this, could you please provide the workaround?
Thanks!

Please Log in or Create an account to join the conversation.

More
08 Oct 2013 13:35 #8 by babynus
Hi,

Several issues may happen.

1) the namespace used does not exist anymore on Microsoft website.
Replace
<Project xmlns="http://schemas.NotAllowedScript6636a2b2ccde9microsoft.com/project">
with
<Project>

2) Some project names with tabulation car

Both are fixed and will be deployed on next version.

Babynus
Administrator of ProjeQtOr web site

Please Log in or Create an account to join the conversation.

More
08 Oct 2013 13:48 #9 by Garden Dwarf
Hello,
Thank you for your answer.
Here is the first 3 lines I have:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Project xmlns="schemas.NotAllowedScript6636a2b2ccde9microsoft.com/project">
<Name>export_planning_20131008_125911.xml</Name>

I have tested with <Project> and I got the same message.

I also exported an empty project from MS Project in XML in order to compare with my export from Project'Or RIA. I noticed a UNIX/DOS format difference (Project'Or RIA is running on a Linux server whereas I try to open it under Windows) which I fixed without success (well, changing from UNIX to DOS was done with success, I meant that I got the same message again).

I have seen also a lot of variables which exists on one file but not on the other one, but I am novice into this and so not able to go further for now.

I went on MS website to check versus the MS Project XML format standards, but it can take time. So in the meantime, any other advise is welcome ;)

Please Log in or Create an account to join the conversation.

More
08 Oct 2013 14:14 #10 by Garden Dwarf
Ok, I found it.

The problem was in the <Group> section of <Resource>.
The content was "<Group>Security & Compliance</Group>" and removing the ampersand character has fixed the import.

I suspect that other fields have the same constraint.

Please Log in or Create an account to join the conversation.

More
09 Oct 2013 16:35 #11 by babynus
Ticket #1198 recorded and fixed.

Babynus
Administrator of ProjeQtOr web site

Please Log in or Create an account to join the conversation.

More
09 Oct 2013 17:07 #12 by Garden Dwarf
Thanks.
Just one more question: fixed for this specific field, or did you checked versus other ones?

Please Log in or Create an account to join the conversation.

Moderators: babynusprotion
Time to create page: 0.091 seconds

Cookies settings

×

Functional Cookies

Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.

Session

Please login to see yours activities!

Other cookies

Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.