We have a few changes we are working on, and as promised in a previous blog we are looking to get the information out there before the changes happen. The first of these changes may be on a Project Online Project Web App (PWA) site near you soon – probably over the next few weeks – depending how the roll out progresses through our internal farms. It is a feature I am very pleased to see come to the Project Online space, and those of you familiar with Project Server 2010 and 2013 will already be acquainted with it. You will soon have the ability to control the version level of the connecting Project Professional 2013, or Project Pro for Office 365 clients. This will be surfaced under Additional Server Settings on your PWA (Server) Settings page. And I would suggest that the number you put in here be at least 15.0.4615.1000 (at the time of writing anyway (Aug2014) – the June CU fixed a bug you would really be best avoiding). Obviously you’d also need to make sure you patched your Project Professional clients to that level – and the Project Pro for Office 365 clients should already be there unless you have disabled the automatic update.
The error you get if you try to connect with a lower version is still not all it could be, but I understand we might also be working on that. The first screen will show
“The following job failed to complete. Job Type: Load, Error ID: 12015(0x2EEF), Error An Internal error occurred”. I’ve clicked More info and scrolled down to get to the meaningful bit – ActiveCacheUnsupportedProjectProfessionalVersion – and in this case I had set my server above the July CU level of 15.0.4629.1000 just to trigger the error. The next error you see will mention failure to get the enterprise global.
If you have read my other posts on controlling versions you may have remembered that you can break server scheduling if the version you are controlling is higher than the running server scheduling engine version. This shouldn’t be an issue for you on Project Online as the version of the client you are controlling, either Project Professional 2013 or Project Pro for Office 365, will have a lower version number than the server scheduling engine (which you have no visibility of anyway). But if you type something bad in – expect to see the ‘Loading’ spinner just go on spinning, if you try and edit a plan…
The other changes coming down the line – and no dates (or promises) for these yet – are the result of listening to our customers and hearing that you want more control over the creation of project sites, the syncing of permissions for these sites and syncing of the task list from the project to the site. More detailed information when these proposed changes get closer.