For whatever reasons, in some on-premise and online environments, the Oslo design isn’t displayed correctly within the project center:by
In the first blog post about reporting with OData, we discovered how to get project data with the standard projectdata feed. We used an URL like https://contoso.sharepoint.com/sites/pwa/_api/projectdata/[en-us] to receive all enterprise custom fields without any filtering. It is a very simple approach to build a list or some graphics, but the performance isn’t good enough for productive environments, especially with time phased data. For this reason some adjustments are necessary, to request just the respective data that you really need in your report. We’ll check out how to do that in this article.by
Within a Project Site on the project server we do have a place to collaborate, file documents, manage tasks/meetings, risks, issues, deliverables and to use the integrated One Note to manage ideas. I faced an issue with the notebook after I customized the project site heavily. After I generated the new solution and made it accessible to the projects, there was the error message “Sorry, something went wrong”. Let’s have a look on the normal process, how you generate a customized project site: Continue reading →by
In this blog series I’ll show you the steps how to create an OData report for your multi-project landscape in Project Online/Project Server. You get a basic idea about the security concept, the process to design reports and how to achieve an adequate performance during data refresh.by
There are two different adjusting screws to administer the project web app:
1) Within the respective instance you can change the site settings and pwa settings for a single site or site collection (if the prerequisites in Office 365 are done).
2) In the SharePoint Admin Center you can not only create and delete site collections, several PWA options in Project Online are also transferred to Office 365. Sounds a little bit like it was done in the Central Administration with an on-premise system, right? However, among other things in the SharePoint Admin Center you can change the permission mode, define quotas and control who’s able to see and edit the site collection settings in the PWA.
At first I thought it is a bug, but I was wrong with that: Since recently, 9999 PWA instances are available for each Project Online tenant. Admins will no longer start to sweat with an annoying limit of 7 PWA instances in the back. Definitely this extends possible scenarios in a lot of areas, e.g. security, trainings and testing.by