Skip to main content

Project Server Read Only Custom Fields

There are multiple ways to create read only custom fields in Project Server 2007/2010/2013. The most common way is through Javascript and a Content Editor Web part
(see: http://technicaltrix.blogspot.dk/2014/10/project-server-read-only-custom-fields.html).

Another more simple way is to use the build in custom fields in Project Server. The downside in this solution is that it is not as flexible as the javascript solution, however it can easily solve the most common scenarios.

Read only custom field - through standard functionality

Assume we have a custom field "Project SAP Number", this field is maintained by the PMO and we do not want the project managers to change it.
We would then create a new calculated custom field.
Go to the PWA and navigate to Server Settings->Enterprise Custom Fields and Lookup Tables.
Click on New Field.
Name the new field "Project SAP Number (Read Only)" and select "Project" in Entity, "Text" in Type and "Formula" in Custom Attributes (see below).
In the Enter formula type the name of the custom field you want to be read only, surrounded by brackets. In our case it's [Project SAP Number].
Click Save.

Now navigate to the PDP where you want the read only field to be displayed. Edit the PDP and modify the Project Fields web part.
Add the "Project SAP Number (Read Only)" field.
Click OK, OK and Stoop Editing.
The field is now read only on the selected PDP.

Note: If you like you can have a PDP only viewable for the PMO with the actual "Project SAP Number" field, this way the PMO can view and edit the field and project managers can only view the field.
The trick is simply to limit the SharePoint permissions so only the PMO can see this PDP.




Comments

Popular posts from this blog

Install DLL in GAC - Windows 2008/2012 (Using Powershell, No GacUtil.exe)

If you want to install a DLL in the GAC and do not have the GACUtil.exe available. Powershell is properly the easiest way to procede.

Before Powershell you would properly just drag the DLL file into the C:\Windows\Assembly but this option is usually not available anymore.

Powershell - Add DLL to GAC So to install a DLL file in the GAC simply execute the below Powershell script. Remember you migth want to run the Powershell prompt as an administrator.
[System.Reflection.Assembly]::Load("System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")$publish=New-ObjectSystem.EnterpriseServices.Internal.Publish$publish.GacInstall("c:\temp\MyDllFile.dll")iisreset
The first line adds a reference to the assembly we need to be able to mange the GAC.
The second and third lines retrives the GAC object and publish a new DLL file to it.
The last line resets the Internet Information Services. This is only needed if your DLL file is used in a websi…

Error occurred in deployment step 'Add Solution': Attempted to perform an unauthorized operation.

Received this error today when trying to create a SharePoint solution against a newly created site.


My first problem was the site was configured to use a port which was already used by another web site. Therefore the site could not start at all.

In my case both Default Web Site and SharePoint - 2000 was both using port 2000. Changing the port of Default Web Site and I was able to start the site.

However now I still received the same error message. When browsing the site I realized I did not have access to the site.

Giving access to my user and I was able to deploy the solution.

To sum up this post:
 - Check the site can start
 - Check the site can be browsed
 - Check your user have access to the site

SharePoint 2013 : Cannot connect to the targeted site.

On my Contoso environment I was trying to create a sandboxed solution. I have already configured my app domain and app management services. But when I tried to validate the site I got the following error message.
Error

Cannot connect to the targeted site. This error can occur if the specified site is not hosted on the local system. SharePoint solutions work only with locally-installed versions of SharePoint Foundation or SharePoint Server. Remote development is supported only for apps for SharePoint 2013.
If you search around the internet you will find many people suggesting to change your host file from 127.0.0.1 to the actual IP.

Solution However the solution, at least on a Contoso environment, is to type in the actual IP address in the host file.
(the IP 192.168.150.1 is the special IP for Contoso, I have 2 network adapters)
And do not forget to clear/flush the DNS cache. Now the solution can be created and validates.