Bulk xml export

[Tracy_Parmeter]

We have a client that is asking for our project data to be exported to MS Project and provided to them. I know we can export each individual project but I am not seeing any way to do a bulk export to xml. We have 450+ projects that need to be exported multiple times. Does anyone know the best way to do this? Maybe it can be done with a Fusion scenario?

[Kurt_Jones]

Tracy,

There isn't a native way in Workfront to create xml data.  If you have Fusion there is an xml module that can be used to create XML data where you could map the fields from projects that you need into an XML structure to have it be created...sorry not better news.

[lgaertner]

Hello Tracy,

If you have a look into the API-Explorer and switch the API version to API unsupported, you will see, that there is an action under Projects (PROJ), which is called exportAsMSProjectFile.

Running that (PUT), I do get an UUID. Unfortunately that action is not documented, but i could imagine, that this UUID could refer to a temporary created file, which has to be downloaded in a second step...
Perhaps someone has an idea?

Regards

Lars

[Sven-iX]

Hi @Tracy_Parmeter  

Turns out it's quite simple: In Fusion

1. get the Workfront session
2. download the XML
3. save (or upload) the XML file

Here's how it works: 
The "Export MS Project" action calls the endpoint /exportMSProject and passes the projectID. 
The response is the XML file. 

JSON attached.

CC: @lgaertner @Kurt_Jones 

[nathan_at_bbw]

Hey @Sven-iX ,

I imported your XML and for me it runs successfully...kind of. I get a 404 status code, but it produces a file. The file, however, says this:

"Note: Since your browser does not support JavaScript, you must press the Continue button once to proceed."

Any ideas what I've got wrong?

[Sven-iX]

Can't tell without more context/screenshots... 

[nathan_at_bbw]

Here's more detail. LMK if you need more.

I tried both "exportMSProject" and "exportAsMSFile" (as spec'd in the Unsupported API actions for PROJ.

The outputs were the same.

exportAsMSProjectFile

exportMSProject

[kautuk_sahni]

@Tracy_Parmeter just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!