Running #ProjectOnline #PowerShell in #Azure using #AzureFunctions #PPM #Cloud #Flow #LogicApp Part1

July 28, 2017 at 4:50 pm | Posted in Add-on, Administration, App, Configuration, Customisation, Fixes, Functionality, Information, PowerShell, Workflow | 4 Comments
Tags: , , , , , ,

Following on from my last post where I published an example solution starter PowerShell script for adding project team users to the Project Site, here I mentioned about running the script in an Azure Function and even running this sync from a Project Online event. The blog post can be seen below if you missed that:

https://pwmather.wordpress.com/2017/07/07/projectonline-project-user-sync-to-project-sites-ppm-o365-powershell-sharepoint/

Whilst I will use that example PowerShell script from my last blog post as an example, the concept will work for any PowerShell script.

I wont cover the details in setting up the Azure Function in part 1 as there is plenty of support out there for this – for this example I created an Http Trigger – PowerShell function.

image

I then uploaded the SharePoint DLLs and copied in the PowerShell script into the editor:

image

The project site user sync script didn’t work as is as I had to make some minor changes to get this to run from the Azure Function. This included change the way the SharePoint CSOM DLLs where loaded in. In the example script I used Add-Type to load the DLLs but in the Azure Function I had to switch this out to use Import-Module:

image

The next change I had to make was to comment out all of the feedback to the console, so all of the write-hosts. I also had to remove the functions within the script so that is was one block. After these changes I could execute the PowerShell script to add the project team members from my example project into the associated project site from the Azure Function. As this was an HTTP Trigger Azure Function, you can get the URL to the function and access that URL to execute the function.

This opens up lots of possibilities to easily execute this Azure Function from other applications that can make the HTTP call. For example you build easily execute this script once the project has been published either using a remote event receiver (RER) or a Microsoft Flow / Azure Logic App. The example script would need to be made generic and pass in a variable into the Azure Function for it to be a workable solution.

In part 2 of this blog post we will look at make a full event driven solution that is fired on project publish then executing the Azure Function and passing in a variable.

#ProjectOnline project user sync to project sites #PPM #O365 #PowerShell #SharePoint

July 7, 2017 at 4:13 pm | Posted in Add-on, Administration, App, Customisation, Functionality, Information, PowerShell, Workarounds | 1 Comment
Tags: , , , ,

This is a supporting blog post for an example solution starter PowerShell script I wrote for Microsoft’s Office 365 PPM tool Project Online. With the great improvement from Microsoft to now support up to 30,000 Projects and Project Sites in one Project Online Project Web App site collection, there are some limitations such as not being able to sync the users to project sites outside of the PWA site collection. For details on this change see the post here:

https://pwmather.wordpress.com/2017/06/14/projectonline-project-site-settings-location-sharepoint-ppm-o365-msproject/

This solution starter script just demonstrates one method to sync the project team members into the associated Project Site-  the concept would also be useful when using the SharePoint permission mode in PWA. The example script is fixed to one example project / project site and only adds the team members to the members SharePoint group on that site. It doesn’t loop through all projects  or remove users from the project sites etc. This could all easily be done but is beyond the scope of the code sample / solution starter.

The code sample / solution starter can be downloaded from here: https://gallery.technet.microsoft.com/Online-User-Sync-to-7a75ef77

To get the script to work, there will need to be some environment variables set and a DLL available, these are detailed below.

To get the script to work you will need to reference the DLL as seen in the image below:

image

This can be installed from the SharePoint Online Client components / management shell. I used the dll from the SharePoint Online Management Shell in this example.

You will then need to update the environment detail placeholders as seen below:

image

Add the Full PWA URL, username and password for an account that is a full admin on the PWA site collection. Select an example project to test with on a non-production PWA project / project site. Use a project that is not syncing the users to the project site automatically – for example a project site outside of the PWA site collection. Copy the Project GUID – it will be similar to this: 4b75dfb8-4051-e711-80c9-00155da85037 and update the script with the project GUID. An easy way to get the Project GUID is from the PWA PDP URL when accessing the project. For the same project, copy the full project site URL and update the script then find the name of the correct SharePoint group to add the users to. For example it could be the members group. The groups can be found from the project site > Settings cog > Site Settings > Site Permissions.

Once these variable placeholders are set, save the script. Run the script using PowerShell and you will see the users added to the specified group on the project site. Fully test this on a non-production PWA instance first. The code should really be updated to production standard code before using on a production PWA instance and handle removing users, adding users to different permissions groups based on role and dynamically getting the projects and project site urls etc.

Below you can see the output from the PowerShell ISE when running against my example project  / project site on my test PWA instance:

image

Looking at the project site you can see the users here:

image

A production version of the PowerShell script could be set to run each day / night etc. as required. The code could also easily be run using an Azure Function and executed from a URL – you could then build is an event driven type user sync – more on that in my next blog post.

The script is provided "As is" with no warranties etc. – this is just a free solution starter so is use at your own risk.

#ProjectOnline – 1 PWA site collection for all or 1 per department? #O365 #PPM #PMOT #Office365 #MSProject

March 20, 2017 at 6:55 pm | Posted in App, Configuration, Customisation, Functionality, Information, Installation | Leave a comment
Tags: , , , , ,

A question I hear a few times from organisations is “We have a new department or business unit coming on-board with Project Online, do we need a new PWA instance for them or can we use the one we already have?” The answer isn’t normally a straightforward yes or no. This post aims to cover most of the questions you need to ask when considering using the existing PWA site collection or creating a new one for a new department / business unit.

The first thing to consider is the Project Online limitations for the data such as number of projects per PWA site, check out the limits here: https://support.office.com/en-us/article/Project-Online-software-boundaries-and-limits-5a09dbce-1e68-4a7b-b099-d5f1b21ba489. Check how many projects you currently have in the PWA site collection and how many more the new business unit expect to add into the PWA site collection – if you are going to be reaching the limits on a PWA site collection then consider a dedicated PWA site collection for the new business unit. The number of PWA site collections in each Office 365 tenant will not be an issue – you can have up to 9,999. Just because you can have lots of PWA site collection doesn’t automatically mean the answer is a new PWA site collection each time!

One PWA site collection will support different PWA configurations for each business unit or department (custom fields , Enterprise Project Types etc.) by making use of the Department functionality to separate those configuration items. So for example, the R&D department only see configuration items relevant to them. So if the new business unit has different custom field / EPT requirements, that shouldn’t be a problem using a single PWA instance.

Whilst talking about configuration items, there are some items that are at the PWA site collection level that can’t be configured / tailored to each business unit or department. These would be some of the Time and Task Management options such as Time Reporting Periods, Timesheet settings and Task settings. Also some settings under the Operational Policies such as Additional Server Settings. If the new business unit has different requirements for time capturing they would need a dedicated PWA instance.

Another important aspect to consider is – will these different business units require access to the same enterprise resources to assign to tasks? Will they need to view the true resource demand / availability for these resources in one place? If this is the case then the easiest option is for the new business unit to use the same PWA site collection.

If there is a requirement to see the data from each business unit together in PWA, for example in a project center view then a single PWA site collection would be required. Similarly, if both business units projects needed to be included in the organisations portfolio strategic analysis for cost and resource requirements, a single PWA site collection will be required.

Reporting is another key factor, if the reports need to show data from all business units / departments then a single PWA instance is easier but it is still possible to generate reports that use data from multiple PWA site collections. With multiple PWA site collections this is something that can be worked around providing there was common metadata between the PWA site collections to enable projects from both PWA site collections to be viewed in the same report.

Then there is the management of the PWA site collection/s. It might be that the organisation has a central PMO function that administers the PWA site collection – adding another PWA site collection will increase their workload.

This is by no means an exhaustive list, here are just a few of the things to consider when deciding on using the existing PWA site collection or a new PWA site collection when a new business unit / department are coming on board.

#Office365 Project Time Reporter mobile app for #iOS released #ProjectOnline #PPM #Timetracking

September 21, 2016 at 10:49 am | Posted in Add-on, Administration, App, Functionality, Information, Mobile | Leave a comment
Tags: , , , , ,

Yesterday saw the release of the Office 365 Project Time Reporter mobile app for Apple’s iOS, see the announcement here: https://blogs.office.com/2016/09/20/announcing-the-availability-of-office-365-project-time-reporter/

This post gives a walkthrough on getting started and using the app on your iOS device. Firstly download the app for your iOS device from the Apple store:

appstore

Once completed locate the Project Time Reporter app:

app icon

On first launch you will be required to enter the Project Online PWA URL:

splashscreen

You will then see the login screen:

login

Enter your Office 365 credentials and click Sign In and you will see the loading screen briefly whilst the data is loaded:

loading

Once completed you will see the Timesheet for this period:

timeesheet

From here you can enter the actuals as needed. Using the green control menu at the bottom of the app you can scroll between timesheet periods using the previous and next buttons, add a row, save the timesheet, send the timesheet or filter the projects. Using the ellipsis in the top right hand corner you can access other timesheet options such as refresh, go to current period, summary, send progress for all tasks or manage timesheets. The app menu in the top left corner enables you to access the app settings, here you can switch to the tasks view or see the app settings. Below you will see screen shots of some of these features.

Firstly the app menu screen, here you can view Timesheet, Tasks or Settings:

app menu

On Settings you can view the PWA URL and username and turn on two options:

app settings

I turned on the planned time in my app:

timesheet with planned work

To enter time just click in the box for the day you want to add time to:

timesheet actuals

You can use the Save button on the green menu at the bottom of the app to save the timesheet or send the timesheet using the send button. If you have many projects on the current timesheet you can using the filter option:

filter projects

If you want to send progress, click the ellipsis in the top right corner:

timesheet options

Here you will also see other options such as Summary:

timesheet summary

Manage Timesheets:

manage timesheets

On the timesheet view you can add rows using the Add button on the green menu:

add row in TS

We have focused on the Timesheet view here but there is also a Tasks view that is accessible from the app menu > Tasks:

tasks

You can change the view by clicking the Current Tasks heading:

task views

You can access the task options to filter and sort the tasks using the ellipsis in the top right hand corner:

task options

Selecting a task will take you to the task details screen:

taskscreen

To edit a task click Edit in the top right hand corner:

edittasks

Make any changes as needed and click Save or Send.

Download it today and see what you think – it will make the timesheet / task update process so easy when you are on the move!

#ProjectOnline / #ProjectServer #Project site provisioning using #Office365 PnP remote provisioning #SharePoint #PowerShell

May 4, 2016 at 4:20 pm | Posted in .Net, Add-on, Administration, App, Configuration, Customisation, Functionality, Information, Installation | 1 Comment
Tags: , , , , , ,

For many years now Project Server deployments have used Project Sites or known as Project Workspaces before Project Server 2010. Typically most deployments have custom requirements for the sites so custom site templates were created from a site created using the default Project Site template. The updated custom site template was then linked to the Enterprise Project Type so that new projects created used the new site template. The biggest issue with this approach was that if you wanted to update the site template later on down the line all of the existing project sites would either need manually updating or writing code to traverse through all the existing sites and make the changes. With the new online world in Office 365 there are other things to think about too. If you create a new custom site template based on the default Project Site template then Microsoft roll out a new feature in the base Project Site template – your new project sites wont get that change either. This is where the PnP remote provisioning engine is great. For a while now – at least a year or 2 I think, the best practise is to stick with the default site templates Microsoft provide, so the Project Site template for example. The Enterprise Project Types should use the default Project Site template so each new project gets a site created using the default site template. But what about my custom lists, or columns or views I hear you ask – deploy the custom artefacts once the site is created from the default site template. In this post I will give you a very quick introduction to the Office 355 PnP Remote Provisioning engine which is part of the PnP core component. PnP, known as Patterns and Practices – details can be seen here: http://dev.office.com/patterns-and-practices. This will enable you to deploy your custom site artefacts.

For this example we will look at the PowerShell variant: https://github.com/OfficeDev/PnP-PowerShell but is also available with managed code. To get started with the PowerShell version follow the steps in the GitHub link to get the components installed. I have created a project / project site using the default Project Site template and added a new list called Change Requests that is linked to a Site Collection Content type in my root PWA site collection:

image

This list has two views:

image

I have also updated the default Risks list to use custom content type and included one new column:

image

I have added my new column to the All Items view:

image

This is the new site template I want to use. Typically this is where you would save as a template but not for this example.

Once the PnP components are installed on your machine, connect to the source project site using this command – update the Url for your site:

Connect-SPOnline –Url <source site URL> 

image

Enter credentials if prompted to do so.

Now use the following command to extract the site:

Get-SPOProvisioningTemplate -Out C:\Temp\PnP\NewTemplate.xml

image

This process will extract the site definition and create an XML file in the specified location:

image

At this point the XML should be modified to remove unneeded properties. For example, as this project site is linked to a project already the property bag will contain certain properties referenced to the source site – I don’t want to overwrite these settings on my target sites so I removed the property bag entries highlighted below.

image

I have also removed properties for configuration I don’t need to update, other lists etc.  See an example below, I have only left the two lists I have added / updated:

image

I don’t cover this here but I used Visual Studio – really one for the devs out there.

Once you are happy with the source XML file you are ready to deploy this to the existing project site/s. In this example I have a test project site created by the default Project Site template that has not been modified:

image

In PowerShell I now connect to the test target site using the command below – update the Url for your site:

Connect-SPOnline –Url <target site URL> 

image

Then run the following command to apply the changes:

Apply-SPOProvisioningTemplate -Path C:\Temp\PnP\NewTemplate.xml

image

Once completed the test target site should be updated, in this example, with a new list and updated risk list. Once you are happy with the test target project site you could repeat the process on other project sites. I have found some settings are not set correctly and some do generate errors in PowerShell but there are usually monthly updates the PnP code so always ensure you regularly update the modules using the Update-Module command.

This is a very simple example using PowerShell, in production you might have a full script that has a list of Project Sites you want to update and get the script to update them all etc. Or better still, go down the manage code route and create an event driven SharePoint provider hosted add-in to do it. Either way, fully test this process on test project sites / projects first before any production projects / project sites!

Getting started with #ProjectOnline development #Office365 #ProjectServer #JavaScript #PowerShell #dotNET

April 26, 2016 at 7:55 am | Posted in .Net, Add-on, Administration, App, Configuration, Customisation, Functionality, Information | Leave a comment
Tags: , ,

Just a quick post to highlight a new code sample that has been added to the Project Online code samples on GitHub found here: https://github.com/OfficeDev/O365-Project-Online-.Net-Samples

The projTool tool has been created / updated to use CSOM instead of the PSI, Brian Smith has a great walkthrough for getting started with this tool on the link below:

https://blogs.msdn.microsoft.com/brismith/2016/04/26/project-development-samples-projtoolv2/

On the GitHub samples you will find other examples for JSOM, CSOM and REST. A great place to start with Project Online development. You will also find some simple code samples / solution starters on the link below for Project Online / Project Server:

https://gallery.technet.microsoft.com/site/search?f%5B0%5D.Type=User&f%5B0%5D.Value=PWMather

#Office365 #Project Portfolio Dashboard add-in for #ProjectOnline #ProjectServer #BI #PPM

April 22, 2016 at 4:33 pm | Posted in Add-on, Administration, App, Customisation, Functionality, Information, Reporting | 2 Comments
Tags: , , , ,

In this post we will look at the recently released Office 365 Project Portfolio Dashboard for Project Online / Project Server 2013 / 2016, see the announcement below:

https://blogs.office.com/2016/04/19/new-office-365-project-portfolio-dashboard-apps-are-live/

A directly link the the SharePoint add-in can be found here: https://store.office.com/en-us/WA104380116.aspx

I have loaded this on to one of our demo instances to take a look:

image

The add-in is accessed from the PWA site contents menu:

image

Worth noting is that the users will need to be a member of one of the following SharePoint groups for the Portfolio Dashboard to work when in the SharePoint permission mode:

Administrators for Project Web App
Portfolio Managers for Project Web App
Portfolio Viewers for Project Web App

When in the Project permission mode the users will need access to “Access Project Server Reporting Service” permission and be added to one of the SharePoint permission groups above.

When the add-in is first loaded it will load the data and cache it – it will tell you it is doing this. Then in the top right corner it will display the details for when the data in that dashboard was last updated / loaded:

image

You can then refresh the data as required and it will update to indicate the refresh has started:

image

Depending on the amount of data this might take some time.

The default dashboard is “This year’s projects”, there are 6 dashboards included by default, these are available in the Dashboard tab on the ribbon:

image

Each show different data. Each dashboard has different sections or pages, for example on This Year’s Projects I can view Projects:

image

Or Tasks:

image

Or Resources:

image

Or Content:

image

Some of the tables in the views have multiple views or sheets, for example the Resources shows Work by default but can view Issues, Risks or Availability:

image

In most pages you can either drill down or click though, for example from the Overview page on the table at the bottom I can click the project name to drill down to more detail for that project:

From:

image

To:

image

Clicking the task name will load the schedule PDP in a different tab.Clicking a risk or issue will load the list item in a different tab.

Notice the left navigation updates to show you where you are with more options. For example I can go from the project dashboard view to an Executive view:

image

I can then go back to the overall dashboard view by using the navigation section.

For each dashboard you can filter the data using the Filter tab:

image

The options tab will give you the ability to change the settings for the dashboard:

image

On the Dashboard tab you also have the ability to create your own dashboard using the create button, that will display a new tab on the ribbon:

image

Firstly give it a name and description.

image

Then select the projects to include:

image

Depending on the field type you will get different options to select, for example selecting a date field will give you this:

image

Then chose the layout for each section and the components on each:

image

Update each section as required then set any filters you want available:

image

Once completed click OK and the new dashboard will be available on the Dashboard menu for all users:

image

Download it today and take a look!

#ProjectOnline CSOM DLL now available in #SharePoint NuGet package

February 5, 2016 at 9:32 am | Posted in .Net, Add-on, Administration, App, Customisation, Functionality, Information | Leave a comment
Tags:

Quick post to highlight that the Project Online CSOM DLL ‘Microsoft.ProjectServer.Client.dll’ is now available via the NuGet package for SharePoint, see the blog post below for details:

http://dev.office.com/blogs/new-sharepoint-csom-version-released-for-Office-365-february-2016

Direct link to the package: https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM

Update multiple #ProjectOnline PWA Instances using c# .Net console app #Office365 #csharpe #PPM #PMOT

December 23, 2015 at 4:12 pm | Posted in .Net, Add-on, Administration, App, Configuration, Customisation, Functionality, Information | Leave a comment
Tags: , , , , ,

Following on from a post I wrote over a month ago regarding checking entities from multiple Project Online PWA instances, this post covers updating multiple Project Online PWA instances. The first post can be found below:

https://pwmather.wordpress.com/2015/11/04/check-entities-from-multiple-projectonline-pwa-instances-using-powershell-and-csom-office365/

In this post I demonstrate a way in which you can manage configuration across multiple PWA instances, for example you might want to create a new custom field on more than one instance. This is a simple example just to show you the idea. As this is very much an example, I haven’t released any code or solution but you can see the core code further on in the post.

For the purpose of this blog post I created a C# .Net console application. Once you have a new visual studio console app project you will need to add the references to the following DLLs:

image

I used the v15 SharePoint and Project Server dlls here.

In the program add these dlls:

image

The first part of the code is to capture the custom field name and description plus the number of PWA instances to update:

image

It then goes into a loop to create the custom field on the specified PWA site:

image

The code below is used to secure the password in the console input:

image

That is it. This example will create a Project level custom field but you could easily update the code to get the user to enter the entity type (task / resource etc.)

To see this in action see below:

Enter the custom field name:

image

Enter the custom field description:

image

Enter the number of PWA instances to update:

image

Enter the first PWA site URL:

image

Enter the username for an account that has access to create custom fields:

image

Enter the password for that account:

image

After pressing enter it will go off and create the custom field on the first PWA instance:

image

Press any key and it will go back to ask for the 2nd PWA instance:

image

It will then prompt for the username and password as before. It will keep looping through depending on how many PWA sites needed to be updated.

On one of those PWA instances we can see the field was created:

image

Nice and easy, saves navigating around multiple PWA site collections for a simple change you might want to roll out across multiple instances.

#ProjectOnline reporting using #PowerBI Part2 #BI #Office365 #Reports #PPM #PMOT

August 7, 2015 at 4:01 pm | Posted in Add-on, Administration, App, Configuration, Customisation, Functionality, Information, Reporting | 2 Comments
Tags: , , , , ,

This is the second post for the Project Online reporting with Power BI intro I created earlier this week. If you missed it, a link to the post can be found below:

https://pwmather.wordpress.com/2015/08/04/projectonline-reporting-using-powerbi-part1-bi-office365-reports-ppm-pmot/

In this post we will look at creating new reports using the Power BI Desktop tool then adding these to Power BI.

Firstly if you haven’t already, download the Power BI Desktop: https://powerbi.microsoft.com/desktop.

Once launched you will see a getting started type page:

image

Close this and you will see a blank canvas:

image

The first thing we need to do is get the data, to do this click the Get Data button on the ribbon then OData feed:

image

In the  next window, paste in your Project Online OData feed, in this example I am using:

https://cpsppmdemo4.sharepoint.com/sites/PWA2PSMODE/_api/ProjectData/Projects

image

Click OK and you will see your data:

image

At this point you can click OK to load the data but I would Edit the data to only select the fields you want. So in this example I will click the Edit button to load the query editor. The Query editor is very similar to the Power Query editor you see in Excel:

image

I only want certain columns so I will select the columns I want then remove the others. To select the columns just click the first one and hold down the Ctrl key then click the rest:

image

Or use the Choose Columns button on the ribbon:

image

Once all selected, click the Remove Columns > Remove Other Columns:

image

Notice in the Query Settings pane you see the Applied Steps, so you can easily undo a step if required:

image 

That is the project data loaded, now I want to load the task data. In the Query Editor click New Source > OData feed:

image

Paste in the URL for the Tasks feed:

image

Click OK to add the new source. I then selected the columns I wanted and named the query:

image

There is also an advanced editor that I used to filter out the summary tasks by modifying the URL:

image

The advanced editor can be used to type the code to manipulate the data but use the UI where possible.

Now we have two individual datasets / queries, we need to merge the queries to create the join, click the Merge Queries button:

image

Chose the columns and table to join then the join type:

image

Click OK.

Once you are happy with the data click Close & Load > Close & Load:

image

This will load the dataset to the report, see the fields pane:

image

Then add your visualisations on, the first one I added is the Treemap:

image

Then drag the fields to the visualisation settings on the pane, in this example I use Project Name for the group property and % complete in the values property:

image

Add the other visualisations you need, the example I created looks like this:

image

I then added another page to visualise some task information:

image

A very basic report but that gives you the idea how easy it is to create visualisations of your Project Online data using the Power BI Desktop.

The next stage is to add this to Power BI. To do this I can either publish the report using the Publish button or from the Power BI site, upload the file. For this example I clicked the Publish button:

image

The report will then be available in Power BI. The manual way from the Power BI portal site is to click the Get Data button:

image

Then chose the type of data, for this example I will use Files:

image

Then click local file:

image

Locate the Power BI file (or can be Excel etc. but this was a Power BI file) and add the file:

image

Once loaded, Power BI will create the dataset, the report and create a dashboard with a link to the report (note, I removed everything from my Power BI portal so that is was clean for the screen shots :))

image

Clicking the link under the Reports heading will load my report:

image

Clicking on an element from a visualisation will filter the data in the other visualisations:

image

The first thing to do is set up the dataset to refresh, to do this click the ellipsis next to the dataset then click Schedule Refresh button on the fly out menu:

image

Expand Manage Data Sources:

image

Enter the credentials for both sources, click the Edit Credentials link, select the oAuth2 for the Authentication Method and click Sign in:

image

Enter the credentials for the Project Online tenant and click sign in. Repeat for the other data source.

Now expand the Schedule Refresh section and turn on the “Keep your data up-to-date”:

image

Click Apply. The data sources will update Daily now but you can also update it on demand using the Refresh Now option:

image

When the data is refreshing you will see a spinning icon next to the dataset:

image

Now lets look at the dashboard. I will create a new Dashboard called “Dashboard Example” using the + button next to the Dashboards heading:

image

Once created you will see a blank canvas:

image

Now I can pin visualisations to this dashboard. To start with access the report previous loaded, hover over a visualisation and click the pin icon:

image

Navigate back to the dashboard and you will see the visualisation:

image

Repeat this process until you have the dashboard you need, for example:

image

You can also create new visualisations from the dashboard using the natural language query “Ask a question…” field, start typing a question about the data, for example “show project work” will create a visualisation for the total project work in the dashboard:

image

This visualisation can then be pined using the pin too. You can also change the default visualisation for the data returned using the visualisation pane, see the example below for a different query:

image

Once finished, the visualisations can be been seen on the dashboard:

image

The properties of the tiles can be edited using the pencil icon:

image

This loads the Tile detail pane:

image

Clicking on a visualisation that was added from a report will navigate you to that report directly.

You can then share your dashboard out to other people in your organisation using the Share Dashboard option, this loads the following window:

image

Enter the email addresses and click Share.

This is just touching the surface of what you can do with Power BI, take a look today – it will be your favourite reporting tool!

Next Page »

Blog at WordPress.com.
Entries and comments feeds.