Skip to main content

Order Enterprice Project Types (EPT) in Project Server 2013

In Project Server 2013 I experienced a strange problem today. When trying to order the Enterprise Project Types (EPT) by choosing a new value in the "Choose the type before which the current type should be positioned" dropdown nothing happened in Project Center. The EPT's were just visible in the order they were created in.



This is an error in the current version of Project Server 2013 (SP1, CU1). I could not find any workaround except to delete all the EPT's and create them in the correct order, this would just have been alot of work as we have more than 10 EPT's.
I have never experienced this problem in Project Server 2010, so it must have been introduced in the new version.

To solve the issue i found tracked down the stored procedure which loads the EPT's. By adding a order statement to this stored procedure the list got sorted correctly.
This solution is not supported by Microsoft and might be overwritten in a future hotfix/CU/SP of Project Server.

To install the solution log on to the SQL server where the ProjectWebApp database resides.
Start SQL Server Management Studio and create a new query.
Copy-paste the below script and execute it by pressing F5.
If the ProjectWebApp database has a different name then the standard name replace the "use ProjectWebApp" with the name of the database.

------------------------------------------------------------------------------------------------------------
USE [ProjectWebApp]
GO
/****** Object:  StoredProcedure [pub].[MSP_WORKFLOW_ReadEnterpriseProjectTypes]    Script Date: 5/30/2014 6:53:33 PM ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
ALTER PROCEDURE [pub].[MSP_WORKFLOW_ReadEnterpriseProjectTypes]
   @layoutsFolder nvarchar (15)
AS
BEGIN

   SELECT
      ept.ENTERPRISE_PROJECT_TYPE_UID,
      ept.ENTERPRISE_PROJECT_TYPE_NAME,
      ept.ENTERPRISE_PROJECT_TYPE_DESCRIPTION,
      ept.WORKFLOW_ASSOCIATION_UID,
      ept.WORKFLOW_ASSOCIATION_NAME,
      ept.IS_DEFAULT_PROJECT_TYPE,
      ept.ENTERPRISE_PROJECT_PLAN_TEMPLATE_UID,
      ept.ENTERPRISE_PROJECT_WORKSPACE_TEMPLATE_NAME,
      ept.ENTERPRISE_PROJECT_TYPE_ORDER,
      ept.IS_MANAGED_PROJECT,
      Replace(ept.ENTERPRISE_PROJECT_TYPE_IMAGE_URL, '$LAYOUTS', @layoutsFolder) as ENTERPRISE_PROJECT_TYPE_IMAGE_URL
   FROM
      pub.MSP_ENTERPRISE_PROJECT_TYPES ept
   ORDER BY ENTERPRISE_PROJECT_TYPE_ORDER

   SELECT
      eptd.ENTERPRISE_PROJECT_TYPE_UID,
      eptd.DEPARTMENT_UID
   FROM
      pub.MSP_ENTERPRISE_PROJECT_TYPE_DEPARTMENTS eptd

   SELECT
      eptp.ENTERPRISE_PROJECT_TYPE_UID,
      eptp.PDP_UID,
      eptp.PDP_ID,
      eptp.PDP_NAME,
      eptp.IS_CREATE_PDP,
      eptp.PDP_POSITION
   FROM
      pub.MSP_ENTERPRISE_PROJECT_TYPE_PDPS eptp

END

Comments

Post a Comment

Popular posts from this blog

Azure DevOps - Gantt Chart

It's been a while since my last post - in the past couple of weeks I have played around with some videos of topics I find interesting. One of these topics are a very cool way of displaying a Gantt Chart upon your Azure DevOps board's. Check it out here!

Project Server - Change field name on PDP for standard fields (like the Owner field)

Project Server - Change owner field name on PDP The field names on the PDPs (Project Detail Pages) has been preselected on the standard fields for a project. If you want to change the Owner to something else it is quite difficult. In the following i will explain how we can change this field through the Content Editor webpart. To change the owner field add a Content Editor webpart to the PDP page where the field is inserted. Select the webpart and from the ribbon select HTML->Edit HTML Source. Copy/Paste the following code into the Content Editor webpart. < script type ="text/javascript">     var old_name = "Owner" ;     var new_name = "Ansvarlig" ;     var ttnA = document.getElementsByTagName( "div" );     for ( var j = 0; j < ttnA.length; j++) {         var orig = ttnA[j].innerHTML;         var stripped = orig.replace( /^\s*/ , "" ).replace( /\s*$/ , &quo

PowerShell results size unlimited/truncated - $FormatEnumerationLimit/Width

Ever experienced the problem where you run a Powershell command and you cannot see the whole result because the result is truncated. Problem: If you for example run the Test-SPsite command you might see something like the following: Site : SPSite Url=http://atlas/pwa Results : { SPSiteHealthResult Status=Passed RuleName="Conflicting Content Types" RuleId=befe203b-a8c0-48c2-b5f0-27c10f9e1622, SPSiteHealthResult Status=FailedWarning RuleName="Customized Files" RuleId=cd839b0d-9707-4950-8fac-f306cb920f6c, SPSiteHealthResult Status=Passed RuleName="Missing Galleries" RuleId=ee967197-ccbe-4c00-88e4-e6fab81145e1, SPSiteHealthResult Status=Passed RuleName="Missing Parent Content Types" RuleId=a9a6769f-7289-4b9f-ae7f-5db4b997d284, SPSiteHealthResult Status=FailedError RuleName="Missing Site Templates" RuleId=5258ccf5-e7d6-4df7-b8ae-12fcc0513ebd,