Category Archives: SharePoint

PowerApps – Build a Simple List View from SharePoint Data (part 1)

PowerApps has a number of integration points with SharePoint. For starters, you can use a template create an app from SharePoint list data. Right now, the template is limited to an app targeted at the phone form factor. Cool, but not what I want in this case.

image

What if you want to do the same thing from scratch?
What if you’d like to create an app that connects to SharePoint list data for a tablet? (or maybe what could be an app eventually embedded into SharePoint)

As with many things in PowerApps, it’s not too difficult (once you know what you’re doing with a little clicking around Smile ).

Build it

Open PowerApps studio. On the ‘New’ page, select the blank app with a Tablet layout. PowerApps will create a single form sized for a tablet. Let’s get building.

image

Start with the content. Select the ‘Content’ menu item and ‘Data Sources’.

image

In the right side property pane, select ‘Add data source’.

image

I already have a connection set up to SharePoint. So I can use that connection. If you don’t already have a connection you can set one up from here. I’m selecting the SharePoint connection.

image

Enter the URL of the SharePoint site:
 image

PowerApps will get a list of lists on the site you entered. Select the list you want – I’m using ‘Requests’ – and click ‘Connect’. 

image

Now, I’ve got a data source from my SharePoint list: Requests.

image 

So, now what? We add a Gallery to our screen. In the menu, select ‘Insert’ and then ‘Gallery’. For this example I’m selecting a Vertical Text gallery.

image

The Gallery control is then dropped on the screen. 

image

Resize and move the control around to fit your needs. I’m filling up the bottom part of the screen an leaving room at the top for a header/title thing later and maybe a few navigational controls. Control size and location are easily changed later as needed. 

image

Now, what’s cool here is that the gallery control has a bunch of features baked into it already. It can be tied to a data source and has additional controls baked into the gallery. This particular example has 3 fields available as shown below. The data for the default fields are kind of nonsense – we’ll fix that in a few minutes. 

image

We need to start by connecting the gallery to the data source. And it’s really easy. While the gallery as a whole is selected (see above), select ‘Advanced’ in the right pane.

image

Selecting the Items field, start typing the name of your data source – in this case ‘Requests’. It should show up as an option in the dropdown.

image

As soon as you select the data source, the screen preview updates with actual data from the data source. When you switch back to the ‘Options’ in the right pane, you’ll find that the controls have already tied to the data source. When you select the fields, they show all the fields in your list that PowerApps can recognize.

image image

So, you can quickly set the initial 3 fields to data in your list. If you don’t have enough sample data – go ahead and add some. Then refresh your data source and the screen preview should also update. Now you’re off and running.

image

That was a very simple run through of connecting to SharePoint data and getting it on a screen. We skipped over a LOT of details that you can dig into but will get into those at another time.

Next up: Layouts, sorting, filtering, etc…

References

JS Link in SharePoint – Choose your Path Forward

Times they are a changin’…

Microsoft continues to roll out the new ‘modern’ interfaces within the SharePoint platform. This is happening initially with SharePoint Online, but is also coming to on-premises deployments with SharePoint 2016 and Feature Packs. While this is a good thing for end-users overall, it does come with a price when it comes to customization options and JS Link. The new interface – the new approach – locks down client-side customizations and unmanaged code in a bid to increase the stability of the platform.

I should clarify that the JS Link approach I’m talking about is the one I’ve been working with and sharing the past few years: Using the JS Link web part property in the web interface and uploading JavaScript files via the browser. This is different from the JS Link approach used by ‘real’ SharePoint developers accessing JS Link via managed and deployed solutions. 

Classic Mode

The JS Link approach we’ve been using is still available through ‘Classic Mode’. Microsoft has stated that Classic Mode isn’t going away any time soon.

image

This means we can continue to develop solutions and customizations using JS Link and Client Side Rendering (CSR) for the foreseeable future.

Downsides of continuing to use JS Link in Classic Mode are: While the ‘modern’ and ‘classic’ interfaces work just fine together they aren’t visually consistent – so it’s a bit of a shift switching from one to the other during day-to-day usage. There also aren’t any migration paths from JS Link solutions to PowerApps or new custom solutions.

The future for power users, however, is really in PowerApps.

PowerApps

Get on the bandwagon now. PowerApps is the future and is a tool not just for SharePoint users – though it does bring new capabilities to SharePoint with forms and mobile accessibility. Between Power BI, Flow and PowerApps, the Business Application Platforms tools are the new area for power users to work in.

Currently, the integration between SharePoint and PowerApps is just scratching the surface, but there is more to come and in all likelihood those changes are going to be coming pretty quickly. Today you can create a PowerApp from SharePoint Online lists and the app will show up in the list view dropdown. Selecting a PowerApp today launches the PowerApps interface. While it’s not live yet, Microsoft has already demoed and shown functionality (in screenshots) of PowerApps embedded right IN a SharePoint page. Once this is possible, the user experience will be dramatically better and solutions (apps) built in PowerApps will start to replace what we previously built with separate SharePoint pages, views, and forms.

With the tools available today, PowerApps can create an app from a SharePoint list – either in O365 or on-premises if using a Gateway – and will create a form-based solution. What I hope to see is an additional template/wizard type of project that looks more like a traditional SharePoint view –hopefully even based on an existing view in more of a grid-focused solution rather than forms on a mobile-device-sized screen. We’ll see what we get. 

SharePoint Framework (SPFx)

When it comes to real customizations, the grey-area we’ve been operating in with JS Link is going away. *Real* customizations are intended to go through developers using the new SharePoint Framework (SPFx). This is managed and deployed code. Where with the current JS Link approach we could have a single JavaScript file, you now need a new stack of open source tools, projects with hundreds of files totaling over 100MB, customization of just the right files, and then deliver the finished package to an IT Pro to deploy in your environment. While this is better for the stability of the platform (again, which is good…), it is now significantly out of the reach of power users.

There’s a lot of information out there about the SharePoint Framework, but it is also new. So, we’ll be seeing changes and additions to it as it gets closer to mainstream. Bottom line is if you’re a developer in the SharePoint space, you’ll want to add SPFx to your list of things to ramp up on sooner rather than later. 

Future ‘Modern’ Interface Updates (?)

Disclaimer: This is *not* real. These concepts are a figment of my imagination and wishful thinking. There has been no word from Microsoft on any new features here.

Some of the things we’ve been doing with JS Link and CSR are relatively simple things, like column/field formatting and conditional formatting. It would be really cool if some of these ‘simple’ additions could be added to the web interface so we don’t even need to do customizations or PowerApps solutions.

What I’m thinking of is updates to how the SharePoint View is defined within the web interface. Today we have the list of columns/fields available in the list. We select the fields we want displayed in the list and set the order that the fields are displayed in.

image

A nice addition here would be to add formatting options for each column. Simplest would be simple HTML/text formatting. Next level of complexity would be conditional formatting. Next level up from that would be more along the lines of a calculated field, but combining HTML and field data like item ID. The first two at least seem reasonable to request. Smile Conditional formatting alone would likely meet the majority of requests by power users.

You certainly wouldn’t be able to do *all* the things we were doing with JS Link field and item overrides, but there are a few things that seem within reach if the SharePoint Team had them high enough on the priority list. 

Conclusion

So, choose your path. And yes, it (still) depends. Winking smile 

If you’re in an on-premises 2013 environment, you can continue using and building JS Link solutions. However, you’ll need to rebuild those solutions when you move to SharePoint 2016 or SharePoint Online. I haven’t tested migration from 2013 to 2016, but I suspect JS Link customizations would come forward as ‘Classic mode’ customizations.

If you’re in an on-premises 2016 environment, you can continue using JS Link solutions, but I would start looking at PowerApps here as well. Even with PowerApps living in the cloud, you have the ability to reach on-premises environments using Gateways. The integration likely won’t be quite as seamless as it will be in SharePoint Online, but Feature Packs may continue to improve this.

If you’re using SharePoint Online (O365), send your power users down the PowerApps path and your developers down the SharePoint Framework path. In the meantime, continue using JS Link and the pages in Classic Mode until you’re ready for the new stuff.

Previous Posts and References

JSLink – Filter on a Lookup Column with CSR

Lookup columns are both useful and a little odd in how they’re implemented in SharePoint list views. I wrote a bit about this in a previous post and showed one example on how to deal with Lookup column content. This post shows an alternative – and possibly more useful approach.

We’ll change the default link in the lookup field to a link that filters the current list by the lookup field value.  Yes, users can also use the filter built into the column header – this is just another way to implement it. I also think this is a bit more intuitive for users.

At the end of the day, this is just another example of custom link ‘building’ with CSR.
Sample File: CSR_LookupSelfFilter.js

Key lines:
image

With ‘Theme’ being the internal name of the Lookup field that we’re filtering on. Fairly straightforward.

The full list:
image

After clicking ‘Technics’:
image

Now we also need to add a ‘reset’ link to the web part so that users can get back to the default view. Otherwise, they could get stuck in a dead end after selecting a filter value. There are all kinds of ways to implement this, for simplicity’s sake we just updated the title text and link. 
Before:

image

After:
image

Obviously you don’t *actually* have to change the text of the web part header – just the URL. Smile But again, it seems like better UX.

Hope this is useful.

References:
JS Link and CSR Page

SharePoint Fest–Seattle 2016

The SPFest folks once again put on a wonderful show last week in Seattle. Big thanks to everyone involved!

Just a quick follow-up with session links to slide decks:

DEV103 – Client-Side Rendering for SharePoint: From Intro to Practical Application

  • SPFest Link
  • You can find lots of JS Link and CSR links on this page.
  • My Link
  • New post with updated script for Lookup link to filtered views (Updated: Link)

PWR202 – Designing and Building User-Friendly vs. SharePoint-User-Friendly Solutions
(previously listed as ‘DEV202’)

  • SPFest Link
  • Did you attend this session? Do you have an idea for a better title for the session?
  • My Link – Added a slide with screenshot on hiding lists with SharePoint Designer
  • Keep an eye out for new posts on PowerApps extensions to the scenario (I will add links)

I love hearing feedback so feel free to email or use the comment section. Thanks!

See you in Chicago!

Getting Started with PowerApps (Preview) for SharePoint Users

Notes and Setting Context

PowerApps is a new product/service offering from Microsoft for building business solutions that connect data from a variety of services and locations – including SharePoint Online. It is targeted at ‘power users’ – which is a somewhat broad and undefined group of users. It’s safe to say that not all SharePoint users will be able to build solutions in PowerApps intuitively as it does require a different skill set – but it is not coding.

  • PowerApps are available through an Office 365 account for users within your organization. Apps are not public-facing. You’re not creating a stand-alone app that anyone can download and run. It will only work for your tenant. The app owner determines who has access to the app: it could be a list of individuals or the whole organization.
  • PowerApps is not a replacement for InfoPath… yet. It certainly has potential. Yes, it has forms – but it’s not going to be on par with what InfoPath had to offer in terms of complexity for now.
  • PowerApps was not developed exclusively for SharePoint – so don’t expect a SharePoint-only kind of focus from the product. It integrates with a LOT more platforms and services. SharePoint is one of them and it already does do some cool stuff for the SharePoint platform.
  • PowerApps is targeted at the mobile platform – specifically phone and tablet devices, but it will be surfaced in the browser as well. The mobile client lists out apps that the user has access to. Apps can also be pinned to the desktop of your device rather than having to open the PowerApps app first.
  • Within SharePoint, PowerApps will soon have a presence within the new ‘modern’ SharePoint lists and libraries – more to come on that soon.
  • PowerApps is built on Azure. So it’s cloud-based. PowerApps Studio is a local tool, but connects to PowerApps Portal – which is a cloud service and relies on the cloud for Connections.
  • Connections’ and ‘Gateways’ are how you get access to services and data. Which ones are available will be determined by licensing… which is still TBD. While currently in Preview mode, we have access to all available connectors.
  • PowerApps is part of a broader effort targeting power users – so check out the other tools and capabilities as well.
    Start here: https://businessplatform.microsoft.com
    And here: https://powerusers.microsoft.com/
  • If you are or were an Excel or Access ‘guru’ building complex formulas, spreadsheets, and/or Access solutions, you’ll probably be pretty confortable digging into PowerApps (and Flow).
  • The documentation is fantastic for this point in a new product release. Seriously I can’t give enough kudos to the team putting this stuff together.
    https://powerapps.microsoft.com/en-us/tutorials

Where To Start

  1. Check out the tutorial found here:
    https://powerapps.microsoft.com/en-us/tutorials/getting-started/ 
  2. Go to https://powerapps.microsoft.com and log in with an account you use with Office 365.

Where To Go Next

Honestly, just dig in. It’s pretty easy. There definitely is a learning curve the deeper you get. But you’ll see a bunch of cool capabilities just by clicking around. You can have a mobile powerapp running on a SharePoint Online list going in minutes.

I’m putting my links and resources here: http://www.idubbs.com/blog/powerapps-and-flows/
So, without repeating all those links in this post, just check it out. Smile

PowerApps Preview – SharePoint Field Work-Arounds

*Disclaimer* – This post based on Preview version of PowerApps. I’ll make every effort to update with any changes and verify when PowerApps is released.

The following is a discrepancy happening in the Preview mode that will likely be resolved in the release version. Until then, something to mention so others don’t get frustrated when working with PowerApps during the Preview stage.

When looking at the columns in my SharePoint list, I have the following:

Figure1
Figure 1

Now, I create a PowerApp based on the same list. BrowseScreen gives me four controls/fields on my card by default.

image.png
Figure 2

When using the dropdown values for the controls, I get the following:

image.png
Figure 3

Which is *not* the same as my list of fields. It looks like I’m missing:

  • ReqType (choice)
  • AssignedTo (Person)
  • CreatedBy (Person)
  • ModifiedBy (Person)
  • Status (choice)
  • Priority (choice)
  • Dept (Lookup)
  • Dept:ID (Lookup – additional field)

The missing fields are Choice, People, and Lookup fields. All of these fields are a bit more complicated behind the scenes. Thankfully we can still get to the data but we need to be a little more deliberate about it.

Note: ID comes as a bonus and IS available for selection. While ID is not shown in SharePoint’s List Settings we know we can get access to it in views. It’s a column that’s just behind the scenes sometimes in SharePoint.

As shown in Figure 2 above, PowerApps provides an easy way to select a control on the card and select which field it should represent. You can also use the Text property directly – either in the top property control or on the Advanced panel (select the View tab, then click on ‘Advanced’).

image.png
Figure 4

In the formula box for the property, delete the field name (‘Comments’). With the cursor after the period, the dropdown suggestion should now show all available fields – including our missing fields.

Notes:

  • SharePoint’s CreatedBy is shown as ‘Author’.
  • SharePoint’s ModifiedBy is shown as ‘Editor’.

Note:

‘ThisItem’ is not needed in this example. You can type the field name directly. However, if you want to see a list of the fields available, you can use ‘ThisItem.’ in the formula.

Select ‘Editor’. Your formula now shows ‘ThisItem.Editor’, but the field is showing an error.

image.png
Figure 5 – ‘Attention needed’ in the Advanced panel

image.png
Figure 6 – ‘Attention needed’ in the form designer

As the message indicates, we need a text value to display, rather than what is essentially a person object. After ‘ThisItem.Editor’ add another period to see additional options – and select DisplayName. This provides what we’re likely looking for.

image.png
Figure 7

DispName
Figure 8

Choice fields work with:
ThisItem.[fieldname].Value

Lookup fields work with:
ThisItem.[fieldname].Value

If additional fields are selected for display (a field setting in SharePoint), they may show up as:
ThisItem.[fieldname]:[columnname].Value
Ex. ThisItem.Dept:ID.Value

Note:
Currently seeing what should be Dept:ID showing up as:
Dept_x003a_ID – I’m guessing this will be updated before release as well.

People fields have a list of values available:

  • Department
  • DisplayName
  • Email
  • JobTitle
  • Picture

All in all, this issue doesn’t stop us from building what we’re trying to build, but it is an inconsistency in the UX and can be confusing or frustrating to folks during the learning curve.

Please – Let me know if you see something different so we can keep this info current.

Enjoy!

MNSPUG July 2016 – PowerApps and Flow

Raymond and I did a presentation at the July 13th Minnesota SharePoint User Group a few weeks ago: Microsoft PowerApps and Flow: Overview and Integration Points with SharePoint. We had a nice crowd of 70-80 folks between the people in the room and folks that participated online.

Links to the presentation slides and recording (TBD) can be found on the MNSPUG site.

NOTE: In our slides we mention the connector for Office 365 Video. Right now there is an issue with that connector working with the current version of PowerApps. This is a known issue and Microsoft is working to resolve it.

Microsoft is generating a LOT of interest in these two new technologies – both still in Preview (now, and when the presentation was given). With the Ignite conference coming up this Fall, I’d be surprised if there isn’t more to see by conference time – between polishing the release version, adding new features, and potentially releasing one or both of the products. Stay tuned.

*Disclaimer* – This post based on Preview version of PowerApps. I’ll make every effort to update with any changes and verify when PowerApps is released.

May the 4th – The Future of SharePoint summary

Big day in the SharePoint world today as Microsoft announces lots of updates coming to Office 365, SharePoint Online, and coming in SharePoint 2016.

First up – ‘SharePoint’ is back. It seems like small thing, but when you’re in Office365 and click on the ‘waffle’ menu in the upper right – instead of ‘SharePoint’, we’ve had ‘Sites’. Not a huge deal to some, but it diminished the brand a bit. With the latest updates we’re returning to ‘SharePoint’.

Next, lots of updates: big and small. Topics include:

  • SharePoint mobile app – sorry, I just can’t say ‘your intranet in your pocket…’
  • SharePoint home (web/O365)
  • Team Sites + Office 365 Groups – better together…
  • Modern library and lists experiences (more on what this means for CSR…)
  • PowerApps integration
  • Microsoft Flow integration
  • Modern pages experience
  • Improved site activity tracking
  • SharePoint Server 2016
  • OneDrive for Business and O365 file sharing updates
  • The SharePoint Framework – open and connected
  • Security updates
  • Feature packs for on-prem

You can find links to the key announcements and sites here:

Microsoft blog posts:

Event recap, recordings, and deep dives:

Other references and links:

There will be more updates in the coming days. I’ll try to update here with relevant links, etc. as they develop.

The Future of SharePoint – Without(?) CSR and JS Link

Microsoft recently announced a new document library experience. Today as part of the May the 4th ‘Future of SharePoint’ event a similar new experience for lists was announced. Ultimately, good moves in the broader effort to improve user experience within SharePoint and an evolution forward. But what, if anything, does this mean for JS Link and Client-Side Rendering (CSR)?

Let’s take a look… I’m not going to give a deep tour of the new interface – that’s for another day. Just focusing on the CSR implications right now.

So, the new list and library interface is locked down. The default page still uses the default chosen view and you can quickly and easily switch views. The page, however, has no editing options. We can’t get to the edit page and edit web part interface. So no-go for CSR. Still, not terrible – while you *could* edit the default page, it wasn’t generally a good practice. (of course, there were some relevant use cases out there…)

Now, if you’re creating pages and adding web parts of these lists and libraries to the page – we’re still in the game. This hasn’t changed… yet. We can still build out pages, add CSR via JS Link and build out our solutions.

So, the short story is that CSR and JS Link still works in 2013, 2016, and O365. There are a few fuzzy spots on the radar for O365 and 2016 though. The new page experience and the new SharePoint Framework are likely to creep into the CSR space. What the roadmap details and timeline are remain to be determined.

Note: If you still need to edit the main library and list pages, you can switch back to ‘classic’ mode. This can be done at the library, site, or site collection levels. Links available below.

References and related materials:

JSLink – Using the Lookup Column with CSR

This post covers another column type for use with CSR overrides. Lookup columns have what I consider an irritating default display characteristic in that they are displayed as a hyperlink to the lookup list item.

image

Where the link goes to:

image

The majority of the times I’ve seen a Lookup used, they are simply a list of items to select in a dropdown or radio buttons – like a category. In this case the hyperlink and displaying the form are useless (to me). Every so often the lookup list has a few other fields, like Description, etc. in that case the link can be a bit more useful, but it still seems to be more of a distraction from a user experience (UX) perspective.

What I’d like to see is the Lookup value – the same text – displayed without the hyperlink. I can get this value using the following:

ctx.CurrentItem.Theme[0].lookupValue

Or, more generically:

ctx.CurrentItem.[internalName][0].lookupValue

You can also access two other properties of the item. The properties are: isSecretFieldValue, lookupId, and lookupValue. And no, right now I have no idea what the heck ‘isSecretFieldValue’ is other than a Boolean value. Smile 

Note: OK. I looked it up. There’s one post under ‘isSecretFieldValue’ here – and if set to ‘True’ it apparently hides the values of the Created By and Modified By values in the form. Huh.

Back to our Lookup column.

As with several other column types, the Lookup column can contain more than one item and is stored as an array. As with those other column types you can also check how many items are contained in the column value by checking the length of the array:

ctx.CurrentItem.[internalName].length

Once an override is put into place using this approach, the list view now looks something like this:

image

Definitely cleaner.

Sample code for this example can be found here.