A double dose of Business Intelligence goodness today for Project Online users – and also applicable to Project Server 2013 – we have a new post from Marc on Creating burndown charts for Project using Power Pivot and Power Query, and some great news of the release of the SQL Server Integration Services (SSIS) OData connector for SQL Server 2012 - http://www.microsoft.com/en-us/download/details.aspx?id=42280, as announced at the Project Conference 2014 This connector will allow our Project Online customers to pull data from Project Online using OData to populate their own SQL Server (or other supported destination) databases. These could be online or on-premises – and would then open up the ability to report via SQL Server Reporting Services or any other desired reporting tools. We will have some getting started material coming soon (this will be on the Project blog – I will most likely post too on Project Support blog) but if you want to get started then take a look at Mike McLean and Andrew Lavinsky’s Project Conference session - http://channel9.msdn.com/Events/Project/2014/PC248. If you were at the conference you should remember the demo in the keynote if you didn’t see Mike and Andrew’s session. If you weren’t there then also see Ludo’s keynote - http://channel9.msdn.com/Events/Project/2014/KEY002 and Mike’s appearance to do the reporting piece at around 50 minutes.
And while I’m at it – I posted over on Project Support a posting about matching patches between client and server and also keeping clients at a common level - http://blogs.technet.com/b/projectsupport/archive/2014/03/25/project-server-patch-matching-from-client-to-server-is-it-necessary.aspx
Enjoy! And keep an eye out for Marc’s getting started documentation for the SSIS stuff – we will have some best practices for getting a good experience pulling OData from Project Online. I’ll certainly be posting again once I see it!
***Update - you might like to take a look at the posting from Paul Mather for a step by step walk through - http://pwmather.wordpress.com/2014/03/26/projectonline-data-via-odata-and-ssis-in-sql-database-table-on-premise-msproject-sharepointonline-bi-ssrs-office365-cloud/. Great article Paul! Our getting started documentation will also cover this, as well as other best practices around limiting data that you are returning to get the best experience - such as only getting the columns you need and filtering for a data range or looking for new data ***
A couple of recent posts worth highlighting. The first relates to installing SharePoint 2013 and Project Server 2013 on Windows Server 2012 R2 – and the need to have the new slipstreamed install packages. I was building up a virtual farm just last week and hadn’t realized that I’d added an R2 Server – and the SharePoint Pre-requisite installer was failing to configure IIS. Finally hit me that we didn’t support R2 until SP1, but even though I had manually created a slipstream by putting the SP1 bits in the Updates folder – the RTM pre-req installer was still giving me problems. The answer is out there - http://blogs.technet.com/b/office_sustained_engineering/archive/2014/03/03/announcing-availability-of-slipstreamed-office-2013-and-sharepoint-server-2013-with-sp1.aspx. The exact error you will see in the Microsoft SharePoint 2013 Products Preparation tool is “Application Server Role, Web Server (IIS) Role: configuration error”
*** Update 4/4/2014 - these slipstream releases are NOT affected by the recently announced issues with the SP1 package - http://blogs.msdn.com/b/brismith/archive/2014/04/03/project-server-2013-and-sharepoint-2013-sp1-download-deactivated.aspx ***
The other post of note – and thanks to Marc, Heather, Mike and I’m sure plenty of others – we have a great post on Power BI for Office 365 as it relates to Project Online - http://blogs.office.com/2014/02/27/power-bi-for-office-365-with-project-online/ a great read!
Just realized the post is tagged for Project Server 2013 and Project Online – although SP1 is only relevant to the former, and Power BI to the latter.