Alexander Vanwynsberghe

"There is nothing impossible to him who will try"

How to setup DirSync with Project Online

Last week, the Active Directory team released a new version of a tool called “DirSync”. This is a tool who makes it possible to synchronize Active Directory accounts from your on-prem environment with Office 365. The version they release was a special one. Let me quote:

I’m happy to let you know that we’ve made it dead simple to connect AD to Azure AD, enabling users to log into Office 365, Windows Azure and any other cloud app integrated with Windows Azure AD using their on-premise username and password.  We’ve done this by updating Windows Azure Active Directory Sync Agent (a.k.a. DirSync) adding the ability to sync hashes of users’ on-premise AD passwords into Windows Azure AD.

How cool is that? Well, curious as I am, I decided to give this tool a go and synced my (playground) Active Directory to my Project Online tenant (which is nothing more than a Office 365 subscription). In this post, I’ll explain how you can achieve this.

First things first, you need an Active Directory. If you have an on-prem AD, just skip this step, at it’s just for demo purposes. As I don’t have the required hardware, but I do have an MSDN subscription, I used some Windows Azure VM’s for that part. What I did was first creating a DNS server (Networks -> Virtual Network -> Register a DNS Server). Next, a new virtual network using my DNS Server. Now  you can create your 2 Azure VM’s. I will not explain this in detail, but be sure that you use your Virtual Network when you go trough the Wizard.

03

You need 2 VM’s, one for the Active Directory role and one responsible for the DirSync. I’ll not go into detail about how to setup an AD role and how to join the other machine to this domain. You can find all info here: http://technet.microsoft.com/en-us/library/jj574166.aspx. Once completed, you should have this:

04

Next up, we will ‘enable’ DirSync at our Office 365 subscription. Browse to https://portal.microsoftonline.com/DirSync/DirectorySynchronization.aspx and enable step 3:

11

Next up, we will install the “DirSync” tool. You can download the latest version here (or use the “Download” link on the page you’re currently looking at). Once the file has been downloaded (180 MB), run the installer, and follow the wizard. The installation takes about 10 minutes.

05

Once the installation has been completed, the configuration Wizard will start. Provide your Windows Azure Active Directory Administrator (WAAD) Credentials. This is the account that you used to create your Office 365 subscription. (if you don’t know the credentials, or you want to try, browse to: https://activedirectory.windowsazure.com and test it)

07

At the next step of the wizard, enter your Active Directory Enterprise Administrator Credentials.

08

At the next step, be sure to enable “Enable Password Sync“. That’s this cool new feature!

09

Once the last step has been completed, a first “full sync” will be started:

10

That’s it! Nothing special. Now you have to check the “Users” in your Project Online (office 365) subscription. Browse to “Admin -> Office 365 -> Users“. There you will see the AD users! Great! Now, just “syncing” this users does not mean that they have access to your subscription. They are not assigned to a license. To manage this, click on the user, and select “Activate Synced Users

12

Assign the correct license to this user, and click “Next” to finish. Note that this user will get a temporary password, but you don’t need this as you have DirSync with password sync (joy!).

13

Still one small thing to do. “Share” my site (in this case the Project Web Access) with that new user. Just click on the “Share” button.

14

Now open a new (inprivate) browser window, and login using the username and password from your Active Directory. There you go:

15

There you have it! A sync between your AD and Project Online (Office 365). But it doesn’t stop there for this post. I just wanted to be sure that the password sync does actually work. So I changed the password and the first name of my user in my AD. But then … How can I force a sync? By default, it takes about 3 hours (password changes-only will be instantly, but changing a name for example will take some time).

So, PowerShell to the rescue! Browse  to “C:\Program Files\Windows Azure Active Directory Sync” and double-click on DirSyncConfigShell.psc1. Enter the command “Start-OnlineCoexistenceSync“:

16

If you open the “Event viewer” on your machine, you will see some entries from the AD sync:

17

Enjoy your syncing!

Using Project Online OData with Excel Web App

Project online has some great reporting features. One of the features that I really like is the OData service. This OData service is not only available for Project online, but also for on-premise deployments. To access this feed, all you have to do is browse to the following url: “/pwa/_api/ProjectData”.

One of the tools to “explore” this Odata feed is Excel. You can open one of the existing Project Online reports with Excel. Go to “Reports – English – Project Overview Dashboard” and click on the 3 dots, select “Edit“.

01

The report will open in Excel, and you can now select the ‘DATA‘ tab, and press ‘Refresh All‘. This should load all your data and show you a list of all projects with some additional information. This is pretty cool, but can we also use this within the Excel Web App? Well, let’s try it straight. Go back to the “Reports” folder, and instead of clicking on the 3 dots, just click on the name of the file. Excel Web App should open, and you will see an empty list of projects. Now click on the Data tab and select “Refresh All Connections“.

02

So, that’s not what we were expecting. It looks like Excel Web App cannot access the Odata feed. The explanation is quite simple:

When Excel workbooks are refreshed in Office 365, the BI Azure Service retrieves updated data from Project Online and recalculates the internal workbook model. If the workbook has data connections pointing to Project Online OData feeds, the BI Azure Service must have permission to the SharePoint Online tenant to retrieve that data.

What we have to do is giving the BI Azure service the required permissions to access our Project Online tenant. Browse to your PWA instance, and add “/_layouts/15/appinv.aspx” to the URL. For example “http://yourtenant.sharepoint.com/sites/pwa/_layouts/15/appinv.aspx“. You will now see the application permission screen. In the App ID field, add 00000009-0000-0000-c000-000000000000 and click Lookup. The title and App domain should tell you we’re working with the Azure AnalyisisServices. Copy and paste the following in the Permission Request XML Field

03

Click create and Trust the App.

04

To be sure that the App has been granted with the correct permissions, go to “Admin (on top) – SharePoint – Apps – Permissions“. There you should see the App “Microsoft.Azure.AnalysisServices

05

That’s it. Now we can open the report using Excel Web App, and click on “Data – Refresh All Connections“. Have fun!

06

Note: Be sure that you first refresh and save your report using the Excel (desktop) application. This will update the internal model of the workbook so it is supported by Excel Web App.

Debugging Apps for SharePoint Online on a non-development site collection

In a previous post, I was talking about how you can use Project Server Online data in a SharePoint 2013 App using CSOM. One thing I was talking about was the fact that you cannot debug an application when you’re not using a development site collection. You will see this nice error:

Eli Sheldon (Program Manager at Microsoft) gave me this explanation (Thanks!):

SharePoint added a site collection level feature near RTM that, once enabled, will allow you to F5 deploy from VisualStudio, no matter what type of site collection you are targeting. Until the new bits roll online and this is documented, your best option here is to F5 debug on-prem and publish an app package and use the corporate catalog to test online.

Well, good news, SharePoint (online) is RTM (since a few weeks). Let’s find out how we can debug our SharePoint app on a non-development site. The reason why I really want to this, is because I have a Project Online App which requires a site collection where PWA (Project Web Access) is activated. Development sites cannot be created with an Active PWA.
I was hoping to see an option in the O365 SharePoint admin center where I could activate this ‘feature’. But unfortunately, there isn’t, or at least I couldn’t find it. So, the next thing I did was opening the solution of my previously created app, and hit F5 debug it. Note: be sure to install the latest version of the Office tools for Visual Studio 2012. As a result F5’ing my solution, I had this error:
So that’s a no-go, because “sideloading of apps is not enabled on this site“. After some research on the MSDN forums, I found a PowerShell script allowing you to enable Sideloading.  Because it’s not available in the interface, the only option you have is to run the PowerShell script to enable this feature. (There is not quite much information about this Sideloading thing yet though).
The first thing you have to do is download the SharePoint Online management Shell (link). The PowerShell script you can use is:
All you need to do is enter you site name, your username and your password. You will get:
That’s it. Now you can F5 your App, and it will be deployed and will also be debuggable on a non-development site, or in my case a PWA site collection. A small app that will load all Projects from my Project Site collection. Nothing fancy, just an example. Have fun!

How to use Project Server Online data in a SharePoint 2013 App using CSOM

This week I was attending the 3 day Project Ignite training. This is a technical training offered directly from Microsoft and was presented by Christophe Fiessinger and Jan Kalis at Warsaw (but I followed the training on Lync, which was really cool using the 360-video). I learned lots of new and interesting things about Project Server 2013 and Project Online. Thanks Christophe and Jan!

Of Course, that’s not the topic of this blog post. During the last day of the training, we got some information about the extensibility options for Project Server 2013. One of the topics was about CSOM, which is an abbreviation for Client-Side Object Model, and also about JSOM, which stands for Javascript Object Model. Let me use the slide from Project Ignite explaining what it is all about:

As you can see, an interesting topic to do some deep diving and (as Christophe told us to) doing our homework. I’ll guide you through the process of creating:

  1. A console application, connecting to my local Project Server 2013 lab machine and create a project.
  2. A SharePoint Autohosted app (based on my previous blogpost: Windows Azure auto-provisioned apps for SharePoint 2013), connecting my Project Online PWA instance using OAuth 2.0 and retrieving a list of projects.

1. Local Console Application

To start, I will create a small piece of code to create a project on my local Project Server 2013 lab machine. So no SharePoint app, no authentication, just creating a project using CSOM. To start, open your Visual Studio 2012 and create a new Console Application. The first thing you have to do with this empty console project is referencing 3 DLL’s. If you’re developing on a machine with Project Server 2013 installed, you can add a reference directly, otherwise you need to copy the 3 DLL’s to your development machine (create an ‘Assemblies’ folder in your project) and reference them this way. The 3 DLL’s you need can be found in the folder “%ProgramFiles%\Common Files\Microsoft Shared\Web Server Extensions\15\ISAPI\ “. Copy those items:
  1. Microsoft.ProjectServer.Client.dll
  2. Microsoft.SharePoint.Client.dll
  3. Microsoft.SharePoint.Client.Runtime.dll

Reference them in your project and open ‘Program.cs’. Add the code, listed here, to your application. I’m not going to repeat every piece of code, as it’s explained very well on that link. But what I want to mention is ‘security’. If you run your SharePoint/Project Server 2013 dev environment, and you develop your application on another machine, you need to provide credentials to connect to SharePoint/Project Server, in fact, you need to initialize the ProjectContext with those credentials. The ProjectContext contains the client-side context for development with a Project Web App instance, and contains the enterprise-wide collections of Project Server objects that exist in Project Web App. You can get the ProjectContext using your credentials with the following quick and dirty solution:

If you run the application (after you added the following command to the start-options of your project: -n “Test Project using CSOM 01” -t 20) , you should see:
In general, it’s all about the ProjectContext. Using this context, you can do/get whatever information you want. In this case, a new Project is created using the object ‘ProjectCreationInformation’, this object is added to the ‘projContext.Projects‘ and finally you tell the context to update with this new project. This will create a queue job and will perform the required action. That was easy to do!

 

2. SharePoint Autohosted App

In this part, I will create a SharePoint Autohosted App where I will use the CSOM to retrieve a list of all projects. You can find a step-by-step guide in one of my previous posts. What you will need  is a subscription of Project Online Preview  (of course). If you haven’t got a  subscription yet, you should really try it out (more info can be found in this post). The first step is to create a new “App for SharePoint 2013” project using Visual Studio:
On the next screen, you should enter the URL of development site (note: when you want to debug Apps on SharePoint Online, you need to have a site collection created as ‘Development site’ type. Otherwise, you will receive an error while publishing in debug mode). This option does have an impact when you want to try debug apps for Project Server (using PWA), but more about that later.
No you have an empty SharePoint App. In our case, we want to use this app to get a list of projects stored on our online PWA. If you look at the files in your project, you will see a file called ‘TokenHelper.cs‘. This is a file responsible for the OAuth 2.0 authentication of your application with SharePoint. It includes the code to handle OAuth 2.0 authentication and how to perform callbacks to SharePoint using CSOM. More information about SharePoint 2013 authentication can be found here.
This TokenHelper class is used to get a SharePoint ClientContext, like you can see in the code below. The TokenHelper returns an authenticated instance of the ClientContext, which is the CSOM you can use to create some cool things.
This is great for SharePoint, but we need something different, we need a ProjectContext. This ProjectContext object inherits from ClientContext in SharePoint,  so you can also access the SharePoint CSOM through this ProjectContext object. To get this context, we need to change some small things to the TokenHelper class. Create the following 2 new functions in TokenHelper.cs
Now we have can get our ProjectContext using the “GetProjectContextWithContextToken” function. We can use the following code just to output the list of Projects:
What it basically does is loading the Projects into the ProjectContext and execute the query to get the results. Ok, now that you have the code, you should manage the permissions of the App. Because will we ‘read’ data from Project Server, we will need this permission to be able to actually read the data. The permission configuration settings can be found in the AppManifest.XML. You can find this file in your Solution Explorer. When you open this file, Visual Studio will show you an editor where one of the option is about permissions. Add the permission ‘Projects Read’ to this list and save the file:
Allright, we have the code and the permissions for our App are set. The next thing is, how can we debug this app? Well, remember when you created the project. We’ve added the URL to our Development site on SharePoint online environment. This development site is a seperate Site Collection. The first problem with that is the fact that this Site Collection does not contain a PWA instance. So if we debug our current application, we will never get data. The second problem is about the permissions. When you try to debug the application, it will check the permission settings. Because we created a permission ‘Projects Read’, we will always get an access denied error, simply because there is no PWA there. So, debugging the application on a Development Site Collection will give you:
You could also try to debug it directly on the PWA site (by changing the debug URL), but then you get this error when debugging:
I passed the question about this to Christophe, and he forwared my question to Eli Sheldon (Program Manager at Microsoft). He gave me this explanation (Thanks!):

SharePoint added a site collection level feature near RTM that, once enabled, will allow you to F5 deploy from VisualStudio, no matter what type of site collection you are targeting. Until the new bits roll online and this is documented, your best option here is to F5 debug on-prem and publish an app package and use the corporate catalog to test online.

So as you can see, currently no F5 debug with this release. But the RTM is coming really soon! (Should be there around mid November for MSDN subscribers). So for now, just publish the App and install it on our Project Server Online environment.  Right-click on your project containing the AppManifest file and select ‘Publish‘. You will get this dialog:
Click finish, and the output folder of your .APP file should open. Now we should ‘upload‘ it to our SharePoint Online environment, and make it available for the users. The place where App’s are managed is called the “App Catalog“. This app catalog is a separate Site Collection, and can be created using the SharePoint Administration Center. There you can click on ‘Apps – App Catalog‘. If you haven’t created one yet, it will create one for your, and otherwise, you will be redirected to the App Catalog itself. On your App Catalog site, click on ‘Apps for SharePoint‘ (on the left side). You will see an overview of all installed apps, including an indication of the licenses you still have available. To add your App, click ‘New Item‘ or drag and drop your .app file to the top area of this page.

Now you have your new Application available in the App Catalog. To use it, just go to Project Server Online PWA. Go to ‘Site Contents‘ on the left side, and click on ‘Add an App‘. There you should see the application we’ve just uploaded. Click the App, and you should get a question to confirm the required permissions. In our case, reading Project data. Trust this and continue. When the process is ready, your application is installed on your site, and you’re ready to use it. Click on the App, and you should see:

That’s a list of your projects, retrieved by the ProjectContext (CSOM). Nothing fancy, no HTML, just plain text. Cool! Now it’s up to you to use the CSOM and create some great apps! I’m really excited about this way creating apps, the way CSOM works, the flexibility, the (future) debugging.

 

3. The things we learned 

  1. You can do lots of things with the ProjectContext
  2. Don’t forget to setup your Permissions in the AppManifest file
  3. You can’t debug until RTM

Thanks to my colleague Koen Callens for the fun experience of creating our first App together! Thanks for reading, and enjoy creating your Project Server apps!

Basic ideation with SharePoint and Project Online

One of the exciting things I saw in the “Get Started with Project Online” video of Christophe Fiessinger was the possibility to use a custom ideation list to capture ideas and ‘convert’ this into a project in Project Online. Managing your companies innovation and ideation solutions with SharePoint and Project Online/Server is really an interesting approach. Both products are well-proven and it can give your company a boost to get the most creative ideas out of your employees. In this post, I will show you how to get started and how to create/design a custom list to capture ideas.

1. Create a SharePoint site

First step is to create a SharePoint site. This will be your ‘community’ site, where ideas will be gathered. One thing to note is that the site needs to be a ‘subsite’ of your PWA (Project Web Access). (see additional information at the bottom of this post) To create a new site, go to the Projects section of Office 365. On the left side, click ‘Site Contents’ and then the ‘new subsite‘ button.

On this new screen, provide a title of your subsite, add a description and the URL. Notice that the URL is a child of your PWA (and that’s what we need for our integration later on). As the template of my site, I used a ‘Community site‘, just because I like the way you can use it for discussions etc. But you can select whatever template you want.

When your site has been created, your browser will automatically redirect you to this new site. You will see a new, empty site based on the template that you selected. In my case, it looks like this:

What you can do now is customize your site, make it attractive, change the colors, do whatever you want (although it looks quite sexy already with the out-of-the-box template).

2. Create an ideation list

What we want to do now is create a new ‘Custom list‘ to capture our ideas. On the left side, click on ‘Site Contents’. This will now list you all ‘apps’ that are available on your site. Click on the ‘Add an item‘ button, and select ‘Custom List‘. Enter a new, and click ‘Create‘:

The list has now been created, time to add some ‘columns‘ where our users can add ideas. Basically, we just want a title field, a description field and a date field where users can add a date of when the idea could possibly be integrated. On your list-page, click the ‘Edit‘ link. You’re now working in the SharePoint editing mode. What you can do is adding columns by clicking on the ‘plus‘ sign. This will give you the option to create a new column based on a the type of information that you want to enter:

3. Rating

Now we have a list with some columns. Off course, we need a way to get our ‘best’ ideas. The easiest way to get the top ideas is by using a voting mechanism. We will let users vote for the best ideas. We will not take voting limits into consideration, and will not use any other advanced techniques, just simple voting.

By default, SharePoint has this possibility built-in. We only have to ‘activate’ this in our custom list. To do this, click on the ‘List‘ item in the ribbon. There you have an option ‘List Settings‘ on the right side.

In the ‘General Settings‘ of your list, you have the option ‘Rating Settings‘. Click this link to show the current Rating Settings. We want to enable Rating, so just select ‘Allow items to be rated?: Yes’.  We will also use ‘Star Ratings‘ because it looks nice.

What this will do is automatically add a column to our custom list. Now let’s add an entry in our list, give it a title, a description, a date and give it a rating. It should look like this:

4. Create a project

Now we have the interesting part: ‘upgrading‘ an idea to a Project in Project Online. Assuming that you are still editing the custom list, click on ‘Stop‘ editing this list. Now you have your list with your one idea. Select this idea by clicking on the first column. This will mark your idea as ‘selected’.

When you click on the ‘Items‘ ribbon item on top, you will see all the possible actions that you can perform on your selected item. And look what we see there: an option to ‘Create Projects‘.

You will now see a dialog with 2 options: The field mappings and the Enterprise Project Type. In the field mappings, you can easily map your list ‘column’ with a ‘Project Web App Field’. Like our title is equal to the Project name, the description equals the Project Description and so on. Do this form each column. Because we’re using a really basic custom list, we can map everything to the ‘standard‘ fields from the Project Web App. But off course, it’s also possible to create Enterprise Custom Fields in PWA, and those fields will automatically become available in this dialog.

The second part of the dialog is where you can select which Enterprise Project Type you want to use. You can select (by default) either an Enterprise Project, or use a SharePoint task list. I’ve already made a comparison between the two in a previous post.

All you have to do now is click on ‘Create Project’. This will do all the necessary things in the background. In my case, it will automatically create a new Enterprise Project containing the mapped information (like the title and description). It will also create a SharePoint Project site. Once everything is setup, you will get the following message:

 Great, so my project has been created. Let’s take a look at it. Go back to the PWA Project Center, and you should see your idea in the list of Projects:

Now to be sure that my field mappings were correct, click on the Project Name. On the left side, click on ‘Project Details‘. There you have a basic overview of your Project information. As you can see, everything is mapped correctly. My title, description, date,.. everything is perfectly mapped. Perfect!

Well, that’s it for today. We’ve created a subsite, added a custom SharePoint list, enabled rating and created a project from an idea. That’s an extremely simplified scenario, but it shows you how easy it is to use the built-in component and capture ideas from your employees. Further extensions could be using Infopath forms, adding some kind of a workflow, treat your ideas in different stages/phases, use collaborative intelligence,… Use your creativity!

Thanks for reading.

A note from John Thoni, part of the engineering team: “One thing to note is that the site needs to be a ‘subsite’ of your PWA (Project Web Access).” This is not entirely correct. The list from which you want to promote items to projects can exist anywhere in the Site Collection where the Project Server Service is enabled. If your PWA, http://myserver/pwa, is not also the Site Collection root, but rather the root ishttp://myserver, then the list could be in the parent, sibling or subweb of PWA (or even PWA itself).

Getting started with Project Online, the power of Project Server 2013 on Office 365

Yesterday, as many of you will already know, Microsoft revealed some nice upcoming stuff like Office 2013, SharePoint 2013, Project Server 2013, Office 365 Preview (including all the new products I just mentioned). One particular thing I was really interested in was Project Server 2013. Lately, I did a lot of experimental work and did some research on Project Server 2010 and particularly the integration ALM and EPM. Therefore, Project Server 2013 is also in my ‘focus’ area right know.

That being said, I was really excited when I saw the new Project Server 2013. I was even more excited when I heard the news about Project Online . As Microsoft describes on their site, they position Project Online as:

”The flexible solution for project portfolio management (PPM) and everyday work, delivered through Office 365″

In fact, Project Online is a full blown Project Server 2013 as you can use on-premise, combined with the power and easiness of the Cloud aka Office 365. So no setup, no SharePoint installation (problems) etc.

What I want to show in this post is how to get started and get your first project up and running.

1. Create your account

First thing you have to do is create your account for Project Online. You can visit this link. You will see a new screen where you can enter your personal information. One thing to notice is that you have an overview of ‘what‘ you will get, on the right side of the screen (you also have other preview programs that you can subscribe)

Once your registration is completed, you will receive an email with some guidance. To start, you can point your browser to “https://portal.microsoftonline.com/admin/default.aspx” and sign in with your credentials (name@domain.onmicrosoft.com). You will now be redirected to the administration page of your subscription.

On this area, you can perform any administrative action that you want. This can be creating users, change service settings, change some options,.. But the most important area is the one on the top-right. That’s the place to be for now.

2. Start with Project Online

If you click on the little arrow next to ‘Admin’, you will see the parts where you can perform the administration. By default, we are now on the ‘Office 365 Preview’ administration part. In the blue part, you have the ‘options/products’ available for your subscription. Let’s click on ‘Projects‘ to open our Project Online.

What you see now is the ‘start‘ page of Project Online. Comparing to Project Server 2010, this is definitely way more attractive. The central space is split in two parts, on top some interesting links to get started, and on the bottom some tiles. There you can see for example your tasks, your pending approvals and some quick access tiles.

On the left side, you have your menu, as you also had in Project Server 2010. This first thing I noticed is the small number of menu items. Project Server 2010 has a more than a dozen by default. But as you can see, there is a button/link called ‘EDIT LINKS‘. Use this menu you can easily modify the menu items on the left. One thing that is important for me (as an administrator), a direct access link to the ‘Server Settings‘ and (as a project manager) the Project Portfolio option. So I selected those items to be set by default:

3. Create a new project by using a SharePoint 2013 site

Now that we are all set, let’s create a new Project. On the ‘Home’ of Project Online, click on the green tile with the label “Create or import project“. You will now see a new popup window asking you for a name of your new project. One thing that you really have to know is that creating a Project using this way, will NOT create an enterprise project. What it will actually do is create a SharePoint site with a task list, and show this in your project list. Let’s illustrate this. I created a new project called ‘My great project’:

When you click on the ‘Create‘ button, it will create a SharePoint site linked to PWA (you can see this in the URL). This SharePoint 2013 site will contain a ‘Task List‘, and this task list will be used for tracking the progress of your project. When the Project is created, Project Online will automatically show the SharePoint site with the possibility to add tasks. On the left side, you also have some other options like adding risks, adding notes (using the OneNote web application, which is really awesome btw!). This is how it looks like:

People using Project Server 2010 will know this type as the regular ‘Project Site’. Only, there is no actual ‘Enterprise project’ now. When you go back to the Project Online place (by clicking on ‘Projects’ on top of the page), and then click on ‘Projects‘ on the left side, you will see the Project Center. As you will notice, you project will be available there. If you click on on the project name (as a link), it will open your brand new SharePoint 2013 Project Site where you can add your tasks.

One thing that you might have noticed is that it’s also possible to import existing SharePoint sites to be used for Project Creation. You can see this on the bottom of the dialog when you click on the green tile ‘Create or import project’. Really nice!

4. Create a new project by using an Enterprise Project Type

Another option to create a new Project is by using an Enterprise Project Type like you know in Project Server 2010. You can create your own EPT’s, modify it, add a workflow, add Project Detail Pages, … You can change and manage everything related to Enterprise Project Types in the ‘Server Settings’ section of your Project Online admin panel.

To create a new project based on your EPT, go to the project center (click on the left side ‘Projects’). In your project center, click on the ‘Project Ribbon’ on top of the page, and click on the ‘New’ button. There you will see the possible options to create a Project based on an EPT.

By default, you have 2 options:

1. Enterprise Project: This is actually based on an Enterprise Project Type. By default, there is no workflow attached to it. It’s just a basic starting point.

2. SharePoint Task List: This is the option that I just described. If you create a project by using the link on the Dashboard, it will use this option.

Let’s create a new Enterprise Project by clicking on ‘Enterprise Project‘.

You will see that by default, you have ‘more’ fields to complete that our basis project we just created (well, just Description field, but hey, you can customize the Project Detail Page). On the top left, click on ‘Save’.

As you can see, comparing with the previous project, it’s not opening a SharePoint Project Site, but it uses the Project Web App instead. There you can do everything with your project that you want, and that you used to do with Project Server 2010 PWA. Note that there is also a Project Site available (on the left side). When you open this, it will look quite similar as the previous one. Except there is one extra link on the menu bar: Project Details. When you click that link you return the Project Web App where all information related to your project is stored (split into several Customizable Project Detail Pages).

5. Conclusion

Now you have an overview of how to get started with Project Online and how to create your first project. I showed you the difference between a SharePoint Project site and an Enterprise Project and how you can create both of them.

Have fun! I’m really excited with this new release! Great job Microsoft!

Thanks for reading,
Alexander