Skip to main content

#ProjectOnline #ProjectServer oData "One or more Data Connections Failed to refresh"

I've been exploring the magical world of Project Online oData Reporting this last month. So far I've managed to pull together some pretty useful PowerPivot-based Timesheet dashboards, and some decent Project/Task Statusing reports.  Nothing as fun as on-premise, but not a bad start.  

However....as well as the well documented service change required to grant reporting access to project online (see here: http://office.microsoft.com/en-gb/office365-project-online-help/grant-reporting-access-in-project-online-HA104021109.aspx) there is another issue to be aware of.

One thing has been concerning me, and that is data set sizes. As we need to pull down some large tables to build a decent data-model  it has become clear that filtering the feeds is the only way to make these reports workable.  Unfortunately, with Project Online its not quite as easy as that.

SharePoint in Office365 uses WopiFrame to display published Excel reports in the browser.  This is basically the Office Web App, rather than the standard xlviewer seen in non-webapp installations.

You can see the behavior in the URL of the report when you view it in the browser

Unfortunately this Office Web App viewer has a limitation that it cannot accept filtered odata feeds when refreshing reports in the browser.  When refreshing reports with filtered feeds you will receive something like:

External Data Refresh Failed
An error occurred while working on the Data Model in the workbook. Please try again. 
We were unable to refresh one or more data connections in this workbook.
The following connections failed to refresh: 
etc

There is a powershell script (below) to switch the default behavior for an on premise installation but this isn't available online.

The command to change this behavior for on-premise is: New-SPWOPISuppressionSetting -extension xlsx -action view

So, what this is currently looking like (and I am hunting for alternatives here) is that - for project online, you cannot use filtered oData feeds  and still allow the report to be refreshed via the browser

This is a fairly fundamental limitation of this service, and one that I understand is known of (although it was new to me) so I am hopeful for a fix/change to this.

here's hoping....


.... oh, and don't get me started on the lack of OUTER join function in PowerPivot

Comments

Popular posts from this blog

#projectserver2013 VIEW FAILURE: The view failed to load. Press OK to reload this view with the default settings. Press cancel to select another view.

** UPDATE ** includes notes relating to secondary bug where Timesheet is created without Administrative tasks.

Does this ring any bells?

This has been bugging me for months, but finally I have a repro for this:

Issue Summary:  When a task is deleted from a plan that is approved into a previous or current timesheet - even when there are no actuals on the task - you can no longer view the timesheet

The following repro has been proven:
- Setup system with Single Entry Mode, with enforced Status Approval before Timesheet Approval
- Create resource as own timesheet manager
- Create new project
- Create two tasks in the same week, starting monday with 5 days duration:  1) Task to assign actuals, 2) Task to delete post submission
- Assign Resource to tasks
- publish project
- as Timesheet User, go to the appropriate timesheet period for the tasks created
- Assign actual work to one task (task 1), leaving task 2 with no actual work
- Submit timesheet
- as Project Status Manager, approve the time on task 1 …

What to do when your application server goes bang

What happens when someone kills your Application Server?
So imagine the scenario:
Three Server Solution - SQL - SharePoint 2010 and Project Server 2010 Application Server (Central Admin Host) - Wfe/ReportServer
We wake one bleary Monday morning to find that some numpty has killed the application server and the users are baying for blood.
Well surprisingly SharePoint handles this disaster recovery scenario particularly well.  Well.  Better than I thought it would to be honest.
Rough steps:
- quick SQL backup to be safe - Rebuild your application server - reinstall pre-reqs - reinstall SP, PS, SPFSP1, SPS+PSSP1, Cumulative Update and other stuff you usually put on there. - Run your configuration wizard to reattach to the Farm, and select Host CA Site
The last step was what I was VERY wary of.  Would the server simply reattach to the Farm, even when there is no CA server available?  
Bingo your back.... almost.... you are going to get errors a-gogo in your event log as things just aren't quite back…

Reporting from Project Server 2016 - multiple sites and userviews

Just a quickie...
I've been interested in how MS have handled the "multiple PWA sites in a Content DB" thing since I read that this was their new approach.  Most of my reporting is via SSRS so i am reliant (still... in 2016) on DB queries rather than OData feeds (tsk) and this "querying a PWA DB with more than one PWA site in it is unsupported" quote was worrying me.

So it looks like what is happening is this.

When you create the first PWA site in a Content DB it hard-codes the SiteID into the _Userview view design elements.  This means that your first PWA Site is the default.  All the data for subsequent sites are still held in the tables against separate SiteID's but you cannot utilise the OOTB _Userview components (see below)


SELECT        ProjectFields....
FROM            pjrep.MSP_TVF_EpmProject('FF19B767-CA6D-4C4C-B123-C0B5AE5354D6') AS MSP_EpmProject 
LEFT OUTER JOIN
                      pjrep.MSP_TVF_EpmInternalProjectHierarchies('FF19B767-CA6…