Skip to main content

We had been struggling with what we thought was a bug in the OOTB Work Dashboard.  Sometimes the number of projects on the dashboard against the datamart didn’t match the number of project shown in the active portfolio run against the transactional dashboard.  We knew the mismatch was not related to any refresh timing.  Further we could see that the data was actually up to date in the datamart.

We were told by a PV reporting consultant that this is actually a “feature” and the reason for this is due to a portfolio itself needing to be refreshed/rerun.   So if you try to run the dashboard against a portfolio that hasn’t been run recently, it’s like the data will be stale in the dashboard view.    

Have others seen this issue and do you have a workaround?  This is totally unacceptable and it is really tough to explain to end users who want to understand why the data isn’t lining up.

 

​@MGMullen this is definitely a frustrating limitation.  To overcome this limitation we worked with Planview to create a bat file and stored procedure that would kickoff a portfolio refresh for all portfolios.  We have, within one of our daily job streams, a step to run the bat file, which triggers the stored procedure to execute.  We also write a lot of our own custom SQL reports.  Within the reports that are portfolio based it is part of the SQL to initiate that portfolio refresh there also. 

Hope this helps,

Pam Sargent

yes we’ve seen this issue with automated reports. We have to make sure we refresh the portfolio.

Several factors influence data refresh timing and potential discrepancies:

  • Automart Refresh Cadence: The Automart typically refreshes daily, meaning its data may differ from the live transactional database.
  • Power BI Refresh Cadence: If the Work Dashboard in Power BI sources data from the Automart, its refresh schedule should align with Automart refresh cycle to maintain consistency.
  • Portfolio Refresh: When changes occur in the portfolio’s underlying data, a manual refresh (via the application or browser) is required for updates to be reflected in the app.

In conclusion: Power BI data is staged, meaning occasional mismatches between the dashboard and the live application can occur due to different refresh cadences. Understanding these timing differences helps explain any discrepancies you may notice.
Hope this helps!

​@MGMullen if you raise a Professional Services > GRS case on the Customer Support Portal the Global Reporting Services team will look into how they can help you with resolving this issue.

Reply


Terms of UseCookie settings
All Data Subject Access Requests (DSARs), and requests of “Do Not Sell My Personal Information” according to the CCPA, must be submitted through the Planview DSAR portal located here

Planview has appointed a Data Privacy Officer (DPO) to be responsible for overseeing our Privacy Management Program and related privacy compliance measures. DPO can be contacted at privacy@planview.com