For your reporting needs, you may want to display values from a Lookup Table exactly in the order they are saved in PWA.
Within PWA, this setting is controlled using “Display order for lookup table” option on Edit Lookup Table Page.
However, this sort order is not available in Reporting Database. Following query uses Published (and reporting) schema to get this information. This is tested on Project Server 2013 on premises.
Short answer: Restart the “Service Bus Gateway” and “Service Bus Message Broker” Service on the server where Workflow Manager is installed. The detailed description is below.
This has happened to me and a colleague so i thought that the solution is worth sharing.
On Project Server 2013 On premises instance, all my projects were stuck in “Project Workflow Check-in” queue job and that job was failing after about 45 minutes. The queue error message was,
One of the victims of Project Server 2013 utilising SharePoint platform is the navigation (in)consistency.
Here is a description of one of the associated issue (or feature by design, who knows?)
If you
i) Open a Project from Project Centre (Projects Page),
ii) Move between PDPs
iii) Press Close button on Ribbon
You’ll return on Projects page.
But if you,
I was giving Resource plan feature demo to a customer and out of curiosity, customer asked if I can assign 1,000 days of work to a resource on a single day. It turned out we couldn’t. When you press Save after assigning 1,000 days of work the system gave the following error.
“Your updates were not saved because of the following reasons: General error: Work value used is invalid. (Use this error information along with other errors to find out the cause of the problem.)”
The behaviour was same for generic resources. And this raised the inevitable question from customer. “How much can I over allocate a resource on a given day in the resource plan?”
Here is a very brief summary of how Department field is commonly used in Project Online, Project Server 2013 and Project Server 2010. You need to have some values in “Department” lookup table to get any advantage from it.
Assign a department to a Project level Custom field, then create a new project and assign the same department value to Project Departments field. The custom field will only appear in your newly created Project.
Assign a department to a Resource level Custom field, then create a new resource and assign the same department value to Resource Departments field. The custom field will only appear for your newly created Resource
Assign a department to an EPT. Assign same department value to a Resource in Resource Departments field. Only that resource will see the EPT as an available option to create the new project from.
Department fields are also utilised to filter OLAP cube data, Portfolio Analysis business drivers and driver prioritisations. If you really want to learn more about department field, check out this article by Treb Gatte.
http://blogs.technet.com/b/projectadministration/archive/2010/03/17/departmental-custom-fields.aspx
Did you read this blog in in less than 3 minutes? Let me know in comments and I’ll update the blog title :)
By default, Actual Cost column is locked down in Project professional both at Task and assignment level. Actual cost is calculated from Actual Work and Fixed Cost values. This way, the relationship with Work done and cost accrued remain consistent.
Ground realities are many times more complex and actual costs involve Journaling, currency conversions and other adjustments. This is typically handled in ERP systems and all PM wants to do is to manually enter the actual cost value in Project so that she can track the remaining cost.
To enter the actual costs manually, you need to change the following setting in Project Professional.
I recently got a chance to work on an SSIS Package in Windows Azure environment which periodically retrieved the Project online data via OData connector and stored over an Azure SQL Database for SSRS based reporting.
Here are some of my takeaways from this exercise.
View Hammad Arif's LinkedIn profile
