Microsoft 365 Community SharePoint Monthly, 14 Aug 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: SharePoint Developer Monthly Community Call - August 2018

Description

SharePoint Developer (SP PnP) Community call recording from 14th of August 2018. Summary of the activities happened in the past month around SharePoint development guidance, roadmap updates, future plans for the SharePoint Framework.

Demo - Site Designs and Site Script - Summer 2018 release
Demo - Preview SharePoint Framework 1.6 - tenant wide deployment in practice

Detailed agenda an links to specific sections available from https://developer.microsoft.com/en-us/sharepoint/blogs/

You can download recurrent invite for the monthly SharePoint community calls from http://aka.ms/spdev-call.

A

Welcome everybody: this is Shep on developer ecosystem or BMP community call. So this is basically Shep on development, monthly, community call and Shawn. You should keep yourself muted, well, I'm. Actually talking never get so. This is the mantra community all around the chip on developer topic, so we're gonna walk through slightly.

A

What's the latest on the on the ship on development, from an engineering perspective, we have two different demos today as well, so let's actually jump in right in the agenda, so we're going to talk about certain updates related on user voice, updates monthly summary at the leader. So what has happened within the last month? This kind of walked through what has happened within the last month.

A

Then we're gonna have a look on the SharePoint roadmap, so what's actually happening within the short timeframe right now, we're not predicting anything after ignite, so they ignite or right after ignite. Is our prediction endpoint for the time being? But let's come. Let's talk about that one when we get to that section, we'll have also two different demos, so Sean squares is going to start around the site, designs and side scripts.

A

So there was a Summer 2018 release around that one new capabilities, new actions available shown, so it's gonna do a real live demo and that one and feel obviously give us feedback on those capabilities as well and then in the end, I'm gonna do a quick preview on the SharePoint framework version 1.6, which is estimated to go out in a matter of days or weeks.

A

So pretty soon, if we wait before ignite and then buy ignite, we'll have another version, but I'm gonna walk through the main, the most important changes in the 2060s re in the Chapman framework. If we have time Q&A most likely, knowing shown allowing me just gonna, we kind of fill up the whole hour and we do apologize and now in practice, because always the monthly community calls we run out of time and that's one of the key reasons why we actually have this special interest group cause.

A

So we do have two different bi-weekly special interest group calls. One is for SharePoint framework. We have live demos and SharePoint framework. We talk about openly entire window around, what's happening, the latest improvements and whatever documentation changes. The next call on the SharePoint framework is on 26s or a 16th of August, so it is this week on Thursday we actually have two community demos and Patrick has promised to do a pretty cool demo on while minimizing bundles for SharePoint framework.

A

So if you're into the SharePoint framework, you actually want to be there on next Thursday now. The second part we click community call is the the SP general div.

A

This is the original special interest group call or office hours, while back, and then we've been renaming this quite a few times, but basically this is everything else except the client, heart development, so provisioning season, PMP, Microsoft graph power, apps much the flow in the context of SharePoint gonna talk about those things in those bi-weekly calls, and now, if you're interested on doing any live demos on this, you are more than welcome to do so. So please reach out to me Patrick checks or whoever in the team and will get you a spot to do.

A

A live demo in the community calls all of the community calls are getting recorded, like this call is, will have its recording live in our YouTube channel within 24 hours after the call has been finished. The monthly community calls this one.

A

Is this one and obviously the next is September 2nd Tuesday of September, which is 11th of September, now they're from Dennis's question, there are two six one: six for SharePoint framework, one sake for shipment general dev and then the monthly community call the whole point of this cost has to quickly clarify that one there's so many calls I can't keep up and that's what the whole point of this course is that you can join based on your interest based on our availability on this course and still ask questions from the other people in the community from the engineering and we'll help you as much as we can in the journey, and also this monthly community course, and mainly for us, walk through what has happened within the past month, which means that which means that there isn't that much time for interactivity.

A

Unfortunately, so that's why we have two different: stick or special interest groups or specific bi-weekly and most likely. This is absolutely the maximum limit where the costs are going, because we can we there's no way of having more now and obviously you can watch all of this recordings in the YouTube channel as well. Quick numbers from the July 2018 and this most likely isn't super interesting for the community. But it's also interesting probably to understand that there's quite a few other people actually working in the SharePoint community, so the SharePoint development community is actually thriving.

A

It's. It is crowing, there's a clear interest once again on the SharePoint developer community, do the SharePoint 2019 release and SharePoint framework and all of the cool capabilities what's happening. So people are again highly interested on what's happening in the space in YouTube we had 170,000 minutes in July, 2018 and 30,000 views, so you can count how much a single view on average was based on that we had thirty, nine thousand forty nine thousand unique visitors and get off, which is great, so people can actually find our open source initiatives, our samples.

A

So that's really cool and there was quite a lot of views in the github as well at the doorstep. Microsoft that come to show the SharePoint dev Docs is crowing all the time, we'll probably hit them 1 million. In this autumn will we will be releasing new material here all the time, for example, the Microsoft flow and power apps. Let's say the makers documentation is going to be released there pretty soon and that's going to increase the views.

A

Definitely when the PMP reusable components usage, which we started back in well technically five years ago, already building this now at the time last month they generated sixteen point: two billion HTTP requests they in SharePoint Online and they were used in more than 14,000 tenants. So this is the BMP PowerShell and also to BMPs, encore and then the most-used capability. Obviously, once again was the provisioning engine. Now what about SharePoint framework so for shippin framework we haven't actually provided any. We haven't actually provided any specific numbers and we are not allowed to do so still.

A

But this gives you the chart, or let's say in let's say it- shows you how the numbers have been crowing as since last July, so this is one year on the usage of SharePoint at a chevron framework for third party. So this is not the first party first bottoming meaning out of the box capabilities. This is custom.

A

Implementations used in SharePoint, Online SharePoint framework is by far the most fastest-growing customization ever in the history and Office 365, and it's by far the biggest and most widely used customization model in shipment shape one well in office 365 in general, so the usage is growing out of this world.

A

To be honest and it's way beyond what we were thinking, which is great, because it proves that the technology is what customers and partners were looking for and right now we're looking into extending usage of SharePoint framework to be the de facto way of creating a Microsoft team step, so you'll actually use SharePoint framework for creating Microsoft in tabs and custom experiences in Microsoft teams and we're also looking into extending that usage and other areas of office 365 now other things.

A

Other things related on kind of a quick news before we go to the actual demos, obviously classic slides up from us to use this in every single slide probably been doing that already almost a year already a game, SSP dev dogs and doctor Doc's ship on developer documentation from here, you can find all the relevant documentation around SharePoint development now, with certain exceptions, so the API documentation is in a separate location to the structure of the doors at microsoft.com, but in a way all of the guidance and around shape and adding development form development framework development.

A

Extensions even show up on 2019 has actually a few pages already in this location and scale. My development feature xml definitions. All of those are available in this one single location, so MSDN is in the journey of getting shut down and we're moving all of the documentation away from there. There are certain API documentation which are still in progress because to be full transparency, the people who are responsible of getting the API documentation didn't quite realize how big a SharePoint API is, so they were assuming a really small set of API.

A

Some small set of talks and when I showed them how much we have see some API sand service like the API, is between 2013 and 2016 20 1990 I went online, they freaked out so there's going to take a while on the journey, but we'll get there eventually. Now on the on the other thing so running into issues on SharePoint. Please please, please let us know this is the issue list in the SP dev Doc's repository is your friend for reporting anything in the def area.

A

So if you call the sharepoint online support and say that, well, this api isn't working they're, actually going to tell you back that. Well, we don't support development topics or customizations, because they can't they don't have expertise to do so. So we in engineering we are trying to help you by giving you a place where you can actually report these issues and will then triage them, and then we actually assign them to our engineers to getting fixed.

A

Now we are way behind of the curve of updating some of this stuff and way behind off the curve of triage in this and we're trying to find the right ways in the future to handle all of the incoming questions and potential issues and using this issue list.

A

But please please keep on doing that, because that helps us on letting us know if there are any critical issues in SharePoint Online now other areas quickly reminder might have seen this already shipment developer clock has moved to an improved platform which still needs to be improved, but it's already better than the previous one, so now we're in WordPress.

A

So this is already a big improvement for us writing the documents, but there are certain styling issues and challenges which we still need to fix and the current the new platform, which is good, it is still waiting for RSS feeds and all of that stuff which are coming up relatively soon now, one of the things what we actually haven't talked about before today is that we're looking into opening up this blog post also for community posting.

A

You will see announcements around that one sooner or later, but the whole point is that we want actually other people to have an opportunity to clock in the official SharePoint developer blog as well. So if you're an MVP or you're you, you want to contribute here. As a community member, you can absolutely soon in the future, submit your articles in the SharePoint developer blog as well, will absolutely review them and make sure that they actually work and their ballot, and then we approve them, and then we push them out using the official channel.

A

So more news on that, one sooner or later now few news on the use of voice, so not that much actually development here. So not that much movement in here we do apologize and done mainly because we're waiting for announcements in ignite 2018. So there will be a lot of changes in some of these areas or announcements and some of these areas, especially in SharePoint framework topics. There will be announcements or overlaps with some of these requests.

A

So as an example, the capability is related on using SharePoint framework as a development tool for my Microsoft themes. Tab will tackle some of these things as well and we're looking into enabling some of these issues or some of these requests by actually implementing them available to be fair. There are certain, also certain capabilities which are requested in here, which will no longer really looking into investing like allowing publishing of quantity and content type up content types using a season.

A

The reality is that, for example, the content type hum is something which we really are not looking in the investing in the future, which means that we're not looking into having this kind of a season and enable because we need to prioritize those resources in a different area. So but, for example, the managed metadata term store operations and REST API. That is something what we need also out of the books, so we're looking into having that one, hopefully by ignite potentially slightly later than that, so I can promise exactly today for that one.

A

But all maturity of this are getting worked on all the time. Now.

A

August 2018 release a summary I'm, not gonna, actually even explain. All of this I want to save some time, but if you go to our deaf clocks, the the ship on developer clocks there's a long summary on what has happened within the August 2018. There's a lot of new samples. Thank you which the community contributed.

A

So thank you, Magnus Leon, those there's a lot of contributions, also on the document side and also in our open source initiatives and those are extremely useful because we rather see us as an engineer working together with you and building open source initiatives, building open source tooling, rather than having a multiple, different, isolated projects built by different people, so working together on a specific tools and reusable tooling, is really what we're going to do inside of the inside of the SharePoint engineering as well not going to go through all of these.

A

They are mentioned in the blog post, which went live earlier today, but the key point: what I wanted to spend some time is to really provide appreciation or make sure that people understand that we really really appreciate your contribution, so we once again had a really big list of people contributing within the last month in our open source initiatives in the github or in the in the community channel suite, and we thank you humongously on doing so also in future, hopefully, but a lot of the people there's new people here.

A

A lot of people here are also familiar from the past, the blood of tomorrow mfps or people who want to be an MVP in the future and contributing in the community channel system, one way of getting also that envy based amp or keeping them latest and so really really great to see so many people contributing now. This is the list of companies which we have a permission to show the logo from the previous list of people.

A

So these companies are basically promoting the community work and promoting their people to contribute on the on the community and open source efforts and what we're running as a Microsoft. So thank you for those companies for giving their employees the opportunity for contributing and working with open source initiatives. Now, if your company, if you contribute it and your company, is not here, please send us an email or miss it using link at social media tech, community, whatever channels and let us know and give your permission and the logo.

A

So we can use that in the future. In this announcement now on, the Microsoft side was a quick list of people. Here. I probably missed some people here, but the Microsoft side of people consist from our technical writers from our engineers from our actually Microsoft internal community members. So thank you very much for your contributions as well. Now, quick, look on the roadmap before we go to the side, designs, the side, scripts and then, after that, we'll come back on the SharePoint frameworks.

A

I'm gonna, not deep dive on the SharePoint framework roadmap in here, but 1.6 for SharePoint framework is the next bigger release which is gonna happen, end of August so but before end of August. So we'll look cooking talking about now days or week or so or so something around that when we get the SharePoint framework. One point six down and really the biggest big things here are the native Microsoft crafts access from SharePoint framework and GA of that one.

A

So you can actually start using that in production and also the global deployment of SharePoint framework and I'm going to explain what the global deployment of SharePoint framework will actually mean in practice in the demo, when you get to the demo section on my side over and then we're looking into having support for react, 16, potentially preview of socket IO and SharePoint 2019 yeoman support I'm, going to talk about those one slightly more detailed after Sean's session ocean style, SharePoint framework 1.6 is now estimated to happen right after ignite.

A

So we kind of demo that and ignite. We, where we going to demonstrate marks of team's development using SharePoint framework and also exposing, is based solutions from Microsoft themes in SharePoint, so doing SharePoint web parts in meetings as a tab, but also the ISVs which are in the teams.

A

They can actually expose their customizations in SharePoint, so it doesn't really matter either targeting teams or SharePoint you customization will work in both, which is a great great solution and obviously SharePoint framework in is supported in shape and 2019 preview started on SharePoint 2019 on 24th of July, so you can already download to SharePoint 2019, install that and play around with that one. So, ok, now at this point, let's actually move to Sean Sean squirts is on the call and Sean is going to talk about SharePoint, site, designs and side scripts.

A

I'm gonna, be your lovely assistant, clicking up lights and.

B

A

I can sleep on your screen when the screen sharing is needed, but I'm gonna go to our following slide, so you can actually text talking.

B

Good morning, everybody yeah, let's I, just have a couple of quick slides, then we'll jump over to my screen and I can show you guys a bunch of demos so good morning. So a couple things without we want to share with you this morning around site designs, one this first one site designs for hubs. This is one that we actually announced at the beginning of summer at the SharePoint conference in Vegas and demoed. It we're getting it ready for ship.

B

They should start to go out to targeted release by the end of the month, so we're trying to get this out before we sort of put the lockdown prior to ignite the exciting thing about this is.

B

As for those of you who aren't familiar with this site designs, as you know, right now are largely intended to be applied through the self site creation flow or to existing sites using PowerShell, and what we wanted to do was sort of continue to build on the power and flexibility of hubs by providing the ability that targeted to essentially set a site designed to be applied to any site that joins a hub.

B

So imagine if you've got a bunch of sites when they're joining a hub, you want to make sure that a certain user group gets added to the owner role of that joined site, or you want to apply a certain library or configuration to that joined site. You can do that now with the site design for hubs.

B

What this allows you to do is we have to really have a UX that allows you to specify a site design and then, when sites join, they can be executed. We've also made an amendment to the to the said: Espio hub site, powershell, commandlets and Sison, so that you can actually set the site design association through powershell as well. Let's see what else notice that second bullet these designs are published globally and can be used on one or more hubs.

B

So let me explain that for a second, because this is sort of part, one of where we're going with this right now. What we've done is effectively exposed the set of site designs that you're publishing for the tenant, okay, and so what you can do is you can publish that site design and then associate it with to a hub.

B

One of the things you hope you will have to do is: if you want to make sure that that site design is only used for that hub, you will have to use the scoping feature to effectively hide it from the self site provisioning flow. Now we understand that that's not optimal, that our plan is. This is really just the first step. We wanted to get this capability out there.

B

Our next plan is to really start to distribute the storage of site design, so imagine being able to publish a site design to the HR hub, and then it's just available for use there. It's not exposed to the rest of the tenant, so you can really start to create local hub specific site designs. So that's that.

A

B

A

B

Also have a lot more in store for this feature space, but just wanted to introduce that and I'll demo this real quickly when we jump over to my screen, let's quickly jump through the other things I want to cover with you guys, that's the next slide.

A

Absolutely now there was a one good question, though, from David, which was any Treecko when site is disconnected from a hub, that's good feedback for the future. So oh.

B

Yeah, that is good feedback. I'm. Sorry I missed that sorry, guys I'm. Let me try to make sure that is a great question right now, as you can see there, we are only were more an additive. So when you join a hub site design, one will be applied if you were to disassociate or unjoined from that hub and then join hub to that had a different site, design that site design would be applied.

B

But at no time are we on site, designing your site or are we applying a site design when you enjoin, but that's good feedback.

A

That's a crate term on site, designing.

B

Okay, I hope this makes. This is a good, so I hope this one makes everybody happy because I've gotten some great feedback like hey Sean, is a super good site. Designs are available for modern team and calm, but I have a whole bunch of existing classic sites. How can I use site designs there well I'm happy to say that we have enabled it for these additional templates for a couple reasons, one because you asked and we see the value there, but also this will actually help the feature I just talked about.

B

We know that there are a lot of sites that will be joining hubs that are classic sites or even as we roll out right now, the new group less modern team site that STS pound 3. We want to make sure that we were providing a mechanism for those to be available and could have site designs applied to them. So these are the three templates that we have made available.

B

Let's see real quickly, I'm going to show you an example of this, because guess what you can also apply this the sub sites as well, so I will show you how to use the example of using the invoke SPO site design come in to to apply to these templates as well. Let's see real quickly. Questions are these only for hub site designs; no, these are for all of them for the for all three of those, regardless of whether they're a site collection, a sub site or a hub site.

B

Okay, let's see oh.

A

It's messing up your flow. There was a good question around the modern subsides from a Cal answer. A CSS subsidies is available. Is it the wind, oh yeah? So let me talk about that.

B

Real quickly, just because that's a very germane to this conversation, so, as you guys, probably saw mark and I just published about a week ago, two weeks ago, a blog post to the tech community about a whole bunch of self site creation updates. These are starting to roll out. Now they can be summarized as four major updates. The first is to self site creation. What we've done is we've amended the admin experience to effectively modernize it if you, if your tenant, does not allow for group creation.

B

So if you're familiar with the self site creation experience today, if your tenant, if you've disabled group creation, we essentially and you have site sub site creation on, we effectively fought you failover to classic site creation, only not an optimal experience, and it also prevents you from making common sites which have nothing to do with groups. So we want to fix that and I'm happy to say that we have so now. What you can do is even if you have a tenant where sub site creation is enabled, but group creation is disabled.

B

You can now make a modern team site and a Tom site. Okay, that modern team site is, as I say, on the slide they're effectively, just a group, less modern team site. It really is very similar to our group pound zero template, just without all the group's stuff attached to it.

B

The other piece that's related to this is we've obviously done the logic updates to the sub site, provisioning UX, so that what will happen is that experience will respond based on your admin settings and which is really cool, because now it gives a more consistent indexing and leaning towards modern experience for your users when you have sub site creation enabled also, in that form, we've added default language support. So now, instead of being stuck with whatever the tenants admin setting is, you can go ahead and specify an alternate language at the time of creation.

B

And finally, the fourth piece is subsonic creation. We've expended the subside creation options because we're really trying to push people more towards using that. That's the wrong word: we're trying to guide people more towards using out sites, and we wanted to make sure that in doing so, we made it easier for admins to be able to turn off or restrict where sub-site creation is enabled. So you can actually turn it off through the UI for all site templates or just for your modern ones. So those are new options. Those are rolling out now and then.

B

Finally, the STS pound 3 that new group list modern team site for those who do enable sub-site creation. We wanted to add it to the sub site creation menu so that you can, if you're, making modern site collections, you can now make modern sub sites. You think get all the questions. Yeah yeah.

A

B

Yeah I want to make sure watching the clock here, because I think this business says yes, you know you're very talkative.

A

You don't want to sit on our meeting, someone of their timing, all.

B

Right last slide: new script actions. Yes, so just real quickly, a couple days out went out earlier, but some have gone out more recently. These are the three main ones. Add principle to group fairly. Self-Explanatory I'll illustrate that, but that works for licensed users, security groups and office 365 groups, the removed nabli that was really intended to just sort of since you're, applying a site design to one of our templates. That already has like a default set of sitemap links.

B

We wanted to give the ability to edit those I mean to remove those I have heard the feedback. So if you're interested I know that there's a lot of interest in having more control over the configuration of the nav like being able to make a post I'm sorry I don't have like a sub link of a parent, and that is absolutely in the backlog. I can't promise I'll have that for you by ignite, but it's definitely something that we plan to get to as soon as we can.

B

The creates I call an XML in the ad SP lookup, a couple things, one that was intended so that you can now use site. They call them X to the I'm sorry field, XML, to create site columns, which is super awesome, because then you can start adding it to content types and things like that, and this also enabled us to do the lookup. So we can now, actually you can actually configure a list and then make it a lookup list and reference it from another list all through the site.

B

Script and I'll give you an example of that in just a minute and you'll see there, there's a link there to samples. Thank you. That's the best I got back from vacation. This was one of the first things. I threw out a mistake. That's I got a bunch of samples, I need your help, and so he got those published earlier this week or last week. I believe so. Thank you and go check. Those out and I want to illustrate a couple of those this morning. Use.

A

It to really start to start learning key top as well. So I don't need to do that for you, but anyway.

A

So let's go to your demo, so let's see some of those in practice cross my fingers that screen sharing works for you. So that's you.

B

B

Let's see if it makes it gives me an option to do the window primary monitor. It did not give me an option to specify which monitor so. Hopefully, let's see what happens, let's.

A

Say where we land in the floating tree dance I can see myself. Oh.

B

That's not the one I want hold on of.

A

B

It's there: why is there no option to change okay? This might be interesting. I can't.

B

Content, what is this Lora.

A

Managing yet yeah.

B

Trying to see if this, no oh, this is gonna- be fun. Okay, I got everything backwards. Guys excuse me for one. Second, we're gonna have to switch all this around I. Don't know why it's not giving me an option to switch monitors. Best am I missing.

A

Something meeting app, not sky for business I. Think that's the problem now. Alright,.

B

Alright, that's gonna be fun because that's my much smaller monitor.

A

So which companies actually implemented the Skype thing? Why isn't it always having these problems? I don't get it.

B

What do you guys see? You know you seen.

B

A lot of spoons here so, let's get started: okay, hi, so the first one I want to show you actually. Let me make sure that I've got my demo stuff together, so I'm not completely crazy. Alright, here we go okay, let's do the first one now site designs for hubs. So, as I mentioned, you can take a published site, design and associated with a hub, and so one of the things that we can do here is I, am on this environment. I've got a travel guide hub, you'll, see that I've got the site ID here.

B

So that's why that's my hub and then I've also got a site design here called the SPC travel guide that has already been created. It's already got a site script and you'll see there if there's its ID there.

B

So what I can view is I can go ahead and use the the set s PL hub site, command, lit and I can pass in the ID of the hub and I can also pass in the ID of the site design and what this is the site, design ideas, a new parameter that allows us to do that Association, so just to show you what I'm doing here here is the hub in the UX and you'll see that under the hub site settings there is a new option here, site design applied to associate inside our joy.

B

This is empty right now, but what it's doing is it's actually doing a lookup against all the site, designs that are on this tenant. Okay, so I'm going to go ahead and run this command here and I. Think it just did it let's build. Let's make sure it did I'm going to go back here.

B

Oops and you'll see that that SP travel guide has now been associated with this hub. Okay, so just to show you that you can actually do this either through the UX or you can do it from PowerShell. Okay. So now that we've got a site design associated with this hub, what that means is when a list could be fun there we go if I have a site that I've want to join that hub. A couple things are going to happen.

B

The typical joining actions are going to happen so that I get the hub site nav and things like that, but also that site design is going to be executed as well. So if we look real quickly, I have what that site. Script is doing just to show you kind of what's happening here. Let's it's this guy right here.

B

What I'm doing is I'm just creating a couple of site: columns, okay and then once I have those site, columns, I'm, creating a content type and then once I have that content type I'm, creating a new list, called travel journals and I'm, adding that content type, adding a couple of other fields and then setting some formatting and apply to view so essentially I'm, just creating a new list that gets applied to the site when it joins.

B

So if I go to one of these sites and go into the site, information screen and I want to go and find that hub and boy. This is gonna, be fun with my smaller screen. Let's get down to the Travel Guide hub, I'm gonna go ahead and join that and.

B

What's happening today, the web was being updated. Oh, what did I do.

B

Mind if I time this thing out.

B

Hey here we go okay, so a couple things just happen. Let me point them out to you so I said I just took this Travel Guide Thailand, modern comm site joined it to the Travel Guide hub. Obviously it's got the hub site map. That's been added but check it out, there's also a script that was run and that travel journals link was added to the site cool meds. That okay.

B

The small screen all right there we go hi everybody. What are we doing? Next? Let's see, let's see, let's see, oh apply site designs to other site templates. Yes, let's do that. Okay, let's go back to this guy here.

B

All right, so what I want to illustrate here is that I can take a published site. Design and I can apply it not only to an existing site but better, yet I'm going to apply it to a sub site. Okay, so what I have here is. Let me go to my environment, real quick here. We go. Apologies for all those mad windows scrolling here, okay, so you'll see here that I have a site on them on my tenant, called appropriately enough STS pound three demo. This is using the new modern site, template team site template.

B

So there is no group associated with the site, I've even gone so far as to create a couple of sub webs that are also using the new modern template. So I've got this one here and this one here and this one is actually called STS pound three sub web B. So what I'm going to do is if we go ahead and go to sub web B, which I believe no I, don't have it here? Okay, so let's go ahead and go to sub web beat so you'll see that this is just a another site.

B

There's a sub site: that's living under this guy I'm, going to go ahead and apply a site design to this. So what I'm gonna do is I'm going to take this site design. The ID is a one button. If not, it's gonna go in create some lookup columns in a list. So what I'm gonna do is I'm going to go ahead and use my invoke command and I'm going to apply this site design to this web URL and specifically I want to apply it to the sub-site. Okay.

B

Okay, I will give that just a second. It should be fresh. Hopefully, I didn't tie myself out.

B

Maybe I did what did I do here.

B

Sorry, let's try this again.

B

Okay, it's not liking that, let's.

B

Let's see if I just go ahead, it must not like something I'm doing here.

B

So first I'm going to go ahead and grab the identity and then the web URL I'm going to grab is going to be this guy here.

B

Maybe that was the problem. All right! Apologies for that typo user error.

B

A

B

Just happened so I just used the invoke command and I just it's actually executed that site design against that sub web, which is an STS pound, 3 site, template and you'll see that essentially what I did was I created a bunch of cycles, content I created a list. I actually created two lists because I wanted to create the contoso project list and this project tracker, which is going to be doing the lookup stuff. So now, if I jump back to this site and refresh it and go to the site contents.

B

Yeah we'll see that there's a couple new lists there and since we're here, let me just quickly illustrate this is actually using the new lookup command. I'm. Sorry, some of the new lookup script actions.

B

Let me jump to those real quick, so essentially the script that I just ran you'll see that we've got this new, create site, column, XML action which allows me to use field XML to create, if I column, which is awesome, because then I can go ahead and take that and add those to a content type and then notice of what I'm doing here is I'm. Creating a couple lists, the first one I'm creating is this contoso project list and what I'm doing here is.

B

This is God the content type that I just defined up above, but then I'm also using the field XML at SPG of XML action to add a couple of additional fields and customize the view and then I'm also creating another list called the project tracker list, okay, so the first one was the project list. Sorry about that for the second one's the project, tracker list. But what's super cool about this?

B

One is I can now actually reference right here, add SP lookup field XML, so this new action I can actually look up a field that lives in the first list that I created so now I can actually use the lookup columns and declare them in my site scripts when I execute these guys. So if we go and take a look at that super quick, let's see if I go to my contoso project list,.

B

And let's see if I just create something real quickly here, let's see there's a in progress: let's go ahead and change this to in review or change it to engineering oops, give it a title.

B

Alright, so now that I've actually added something to that list, you'll see if I now go to the project tracker list and create a new item here.

B

You'll see that those items are now available as options here: cool alright.

A

Really cool, ok,.

B

Let's see what else do I have up. So, let's see, we've got with a hot site. Design we've gone through applying site designs to other templates started to show you some of the script actions. Let's go! Look at a couple more of the script actions. Super quick I've got two more for you. How we doing on time. That's it! Thank you.

A

A

B

All right I failed to do this in six minutes. Let's see where am I am I on the right environment, I think so, yes, okay! So let's see the other one that we did was. There is a new, a new script action to add principles to SP groups and essentially what this one is doing is, let's see I think I have kept the script of. Let's see if I did I might not have added that one.

B

Let's see we can get rid of this guy, no I do not have that one. Let me show you what this one looks like real, quick.

B

So this one's pretty straightforward, actually what this one is doing is it's just illustrating adding different types of principles to the group. This could be super powerful, in fact, one of the things that was really motivating this was when we were seeing the power of applying site designs to hubs.

B

Obviously, a really cool thing to do would be to say: hey when the psych has created or when a site joins a hub, let's make sure that certain users or user groups like admins or support, get added to that site with the right role so that they can go ahead and troubleshoot or support should that be needed. So what this is illustrating is just here's the different type of principles. You can add security groups, mail, enabled security groups, Oh 365 groups and even users, and so what this one does is, let's see principles.

B

And I don't know why I made this a team side, because now we're going to make the group I think I did it because I want to make sure that certain groups to be added as well but fortunately site creation is so fast and.

B

Let's see what this script is doing here, so you see it's adding I just for reference sake. I went ahead and added the link to the user group to the site nav, but I'm, adding a prob. This principle: TS FSG, that's just a security group that I created on my environment, to the owners group, then I'm, adding a particular. Let's see a mail enable security group to the members group and then finally, I am adding, looks like I, add a Joe user to the owners group as well and then also a modern team.

B

That's another oath, 365 group to the visitors group. So if we go ahead and refresh this you'll see, there's that user group link and just real quickly you'll see if you look at like something like the owners, there's Joe users, that's been added, so super useful. Hopefully you find value in that action. I pickup down to two minutes, I've got one more for you guys. Let's see my last one was all removing site links, let's go ahead and do that one real, quick.

B

Okay, so well, there is remove sight lanes. Oh that's also a teen sight, sorry trying to infer where I put some of these demos. Okay, here we go, remove default sight Lakes. This one is good because it just illustrates on a group connected team site, all the things that we can remove. This is super useful. If you want to really control that experience, we've gotten great feedback from everybody saying hey great, adding links is perfect, but there's certain default links that I don't want on my sites when they get created.

B

Can you give me a way to remove them? Yes, we have a new action that does that now so you'll see what this one is intended to do is really just to illustrate removing everything. So as soon as I update this voila, the site map effectively disappears and then you're, probably asking me gee char. That's a neat demo. How do I get my links back?

B

Well, you're gonna have to go into the into a classic page in this example and go ahead and add something back since I've effectively removed everything, but there it is just showing the power of removing the links.

B

So in conclusion, lots of cool fun new things either for you guys is be back. If you would like to see work get some working samples of this we've got a bunch of new sample supposed to the github repo and ignite right around the corner. A couple questions that came up while beste was doing the overview around action limits and the managed metadata field so real quickly. We will have more information to share with you next month at ignite around action limits.

B

We realize we keep giving you all these great, powerful actions that xxx limit is starting to become a real hassle. So we've got some things that we'll be sharing with you on how to work around that and start running, larger and larger scripts. So I'm excited to share that news in a few weeks and then, finally, with the managed metadata field, we are working as quickly as we can to make something work there.

B

It's really a partnership with our publishing team to make sure that we get the right, API updates there, so that we can make something that's easier to configure. That's a complex data type, but we also get that it's a widely used one and we want to make sure that we have a way or so.

A

And maybe one thing to actually notice during the your presentation, there was a question around how could I modify the Welcome page of the site and for time being, there's no native support from a JSON scripting perspective, so you'd have to call a flow which caused an unnatural function or something like that. That would then use this BMP provisioning for welcome page, but in the long run, we're looking into I. Get that happen right.

B

Absolutely yeah exactly what that's the set I mean. We you take advantage of the flow and using all the greatness that is available in the PNP provisioning model.

B

The the challenge they are just candidly is: we need a better modern, Pages API, then a lot of the script actions that we provide. You guys that's all really built on api's, and so we need something. That's a little bit more robust there.

B

That allows us to work with the modern page, canvas and obviously with a lot of new web parts, so that we can give you the means in the script to properly reference them, and then you know, do those applications but I honestly, that's like the the top scenario for me that I would you know I I can tell you now we're not going to have that at ignite, but we should have an update and we're looking to you know, get something to everyone soon, cuz. We know that.

B

That's a huge scenario that will unblock a lot of adoption here, but.

A

Now, Shawn, why isn't all of these things ready by a snap of her fingers? What do you mean? You don't have infinite resources.

A

Let's quickly have a look on the SharePoint framework, 1.6 I'm gonna pinpoint certain things what's going to happen here around the 1.6 I'm gonna do a kind of an ugly live demo of the globally attend on wide deployment of SharePoint framework extensions, so just explaining what it is and what's going to happen so one point six. There was actually a mistake in the previous slide around 1.6. Third, the react, 16 transition doesn't happen in 1.6. It will most likely happen in 1.7 and we do apologize.

A

If doesn't that's something, what we waiting for again, it's a using challenge like sean, has resourcing chances of making something stuff done and there's a regional thing challenges in our team responsible of SharePoint framework for making all of the things what we want to do available now. This is currently the list.

A

What we are targeted on, releasing certain on wide deployment of SharePoint framework extensions, so you're able to push extensions to specific site types or specific sites from the ad catalog and I'm going to show that one in practice today, GA has meaning production-ready craft and third-party web api calls from ship on framework. So that's going to be available in 1 point 6 g of dialog framework. This is more to be fair. This is leftovers.

A

We forgot to get rid of the beta markers of those API, so dollar Tremec is going to be 10, GA, afters, 21.6 preview of socket IO, so we're looking into doing easier.

A

Let's say you you're able to subscribe events from a list super easily, so your web part can then react when somebody is uploading, a file to the site or a document library or a list, and you can easily do stuff. And yes thank you, entry for that question. That's that's a similar kind of a leftover that well. We should have just marked that to be a GA, so there's the beta Marcus and SB HTTP client bench and that's going to be removed in this release.

A

That's such a small thing, but anyway and SharePoint 2019 support is gonna, be in the 1.6, so there will be three choices when you target an environment. You're able to say is this web part or an extension targeted for sharepoint online, which is the latest or Chevron 2019 forward, or share one 2016 forward and based on your selection. We then create the package.json with the matching versions of the NPM packages, which will then work properly, which is obviously use, and there will be other things and issues what we will be fixing.

A

So that's what that's going to be helpful as well.

A

Boo-Boo so Genesis asking so SB 2019 will support an unreleased version of to ship on to SPF X 27 sticks to now. Shipment 19 will support ship one framework. One point four point: one technically now right now doing development for sharepoint online and chapman 2019 in a single setup, it's difficult for you, because you need to install one point four point: one technically: to make your solutions to work with one point: six, we will give you the option that you can as a developer run.

A

One point six and based on the the yeoman selection will give you the right version in the package.json. So that's how it will work so in practice, but let's I do not have that many minutes, but I want to quickly show the dead unwind deployment in practice. So let me jump into my one of the talents. So this is a dock, so this is super. Super super super led not compiled eight hours ago. So this is really really latest code, so hopefully I'm not saying anything which I shouldn't be showing you now.

A

When we do development, we can actually do that first. So let me go to this us to their code. This is a solution which I already scaffold, so this basically is a 1.6 pre version. So I'm going to show you that here it's a 1.6 step 8. So this is our internal release versions, which we're using for testing and verifying that everything is fine. Now because we are looking into releasing releasing the tenant wide deployment. That means that we actually as part of extension and creation.

A

If you choose an extension, we give you a new, completely new file, which is called client side instance dot XML, and what this one actually dances that this by default. If you package this solution, it will point AFOL to light up this extension in those locations where you actually want just by adding this baby cave SP pkt file to the ad catalog. So let me show you that one in practice and then we can actually figure out what it means and let me actually, let's close those and let me actually open up- did it I?

A

B

A

Why am I I'm still in the integrated terminal there? It is I'm learning a completely new keyboard layout, so bear with me. So so let me do a bundle and ship I'm moving away from finished keyboard layer to do numerous reasons to you and II and us-international.

A

It's a longer story. I'm, not gonna, explain that from here so I'm going to package the solution and can do called package solution and that's the ship, so we can actually use the asset packaging, so javascript files are inside of the solution or inside of the of the packet and then I'm gonna do Explorer and let's open up the Explorer and let me actually get rid of the navigation pane. So there's nothing to confidential information is shown there. So this might call demo.

A

So now, if I open up my tenant, which has been enabled to describe bilities I, can actually track and dark. This solution inside of my app catalog and in this case, because it contains that specific JavaScript file- sorry XML file, it's gonna actually say that a new message: these packets contains an extension which will be automatically enabled across sites. You can control the setting using globally deployed components list at the App Catalog site collection, so my default because that XML file exists in the SB pkg phone.

A

We can actually line up this extension across the whole tenant. If you don't want to do this and us a 10 on the administrator need to understand what this message actually means in your you can go to the developer and say well: I, don't want to actually do that I'm going to target this target the functionality to a for example, communication sites or only group associated team sites, not to all of the sites. Now in this case, I can actually enable this in all of the sites and that's fine and there we go.

A

It is actually saying that the deployment failed which society Falls, but this is Annie dog, so this super super early environments are done for about that. Now, in my case, I actually then deployed an extension. I think it was a relatively ugly application, customizer which actually pops up and message in a dialog so now anywhere in my tenant, because we actually added that entry automatically do the application catalog global edit point list. That extension is getting lighter. So now, if I need to control this behavior I can actually go to the app catalog.

A

I can go to the site content and we can actually see a tenant wide extensions list. We're going to actually modify this behavior and I can see that I have currently three different application: extensions lighting up in my antenna, one of them is lighting up on every single web template. One of them is lighting up in sts-3, and one of them is lighting up completely imaginary SDS, for so it doesn't actually light up anywhere. So in this case, I actually want to get rid of this I can actually I can delete the item.

A

I can do a filtering of the extension to another location or another template if needed. Depending on my settings. Basically, you have a one centralized location where you can control how your sharepoint extensions are working and behaving across your tenant and that's really pretty cool, and that gives you a flexibility right now. This not require understanding of what these things actually mean. So in my case and if I'm gonna do a stairs for here, it's gonna basically mean that this extensions not going to be executed anywhere because there is no such side SSDs for so.

A

If I'm in the publishing side, you can say that the purpose in the extension isn't actually any marketing lighting up now I'm going to take a few more minutes on extra time, so I'm going to add a new entry on my tenant wide extensions. As an example I'm going to target my extension only to be executed, one of the extensions only to be executed in publishing sites. So let's actually do that. So I have an extension with a unique ID.

A

Let's call this extension and demo, and this particular extension has a configurations of top and bottom button properties. So this is relatively technical stuff for the developers to actually define I want to target that for communication site. So I'm able to say a web template should be a site.

A

Page publishing has one sorry has three, which is the communication size which is getting created, and then I need to define the location, and in this case, because it's a placeholder based customization, it actually means that I'm, enabling that in the location called client-side extension dot application customize there now one thing to maybe notice here there is a list template option here as well, so go so. This works for list view command sets.

A

We were able to push buttons and all of those functionalities in the list level as well, using the tenant, wide cost and tenant wide deployment option. So let me add that entry in and there we go. Where is that standard? That's different? There is a footer for comes. It is that kind of a component ID.

A

Now, if I go to my communication side, if I do a refresh, we can actually see that that particular extension super super ugly and just using two different placeholders is lighting up automatically in every single communication side, the ones which already exists or the ones which I'm actually going to create because it's a runtime configuration of the site. So now, if I create a site, so let's create a communication site, because this doesn't take that long.

A

So, let's call that comes to 1 2 3, 4, 5 Sean has done an awesome job creating on the site, creation creation. There we go and there's my no communication site and my extensions are lighting up. So you can easily gonna figure these things and obviously you can disable things in the same way. So if needed, I can absolutely go here or I can go and say: I can reconfigure.

A

Community call I can reconfigure. My extension click Save. If I go to my communication site sit here, that's food or for comes and let's refresh now it's actually going to say, communicate community call, so it actually updated that value updated. The behavior of the extension based on my configuration on the sites and and likes it, this absolutely works on the existing sites, new site. It doesn't really matter it's a rundown resolution, so that works in a way right way and you're able to target the configuration on the list.

A

Now we do acknowledge that this is relatively, let's say rough way of configuring. This and so in a long run, we're looking into having potentially and central admin or admin UI where any user can or administrator can go. He can, from a drop-down, select whit's extension with civil web templates without understanding what is an SDS has three or cyclops in zero, and he can select that well.

A

This works in a as a placeholder or application customizer, and you can easily do that, but as a starting point, this is already enabling the same scenario where you're able to push your extensions available without any additional magic from one centralized location from your app catalog across the whole tenant in any way one, and that is absolutely great and and completely understandable, request what the customers have been having cool. So one point six is coming out in the focused original plan was actually come out in the end of july. There were certain timings and challenges.

A

What we were we needed to delay the release so right now end of August is deadline and we're looking into actually keeping up on that one. That deadline right now, so no known delays at this point, so this functionality will be lighting up when the SharePoint framework 1.6 comes out technically the server side, it is a server-side functionality. You wouldn't actually need to have a change this on client side, but we're releasing that at the same time as the SharePoint framework 1.6.

A

So whenever you see the announcements in the posts in the social media, you will know that that functionality is available and you don't have to do any additional tricks to enable your scenarios cool five minutes over the time. We do apologize, it's it's! If it's me and Shawn talking ad. This is what actually always happens, relax that if we have one two one switch shown, we typically talk 25 minutes of nonsense than 25 minutes business. That's what happens, but please give us feedback. Thank you for joining on this call.

A

The recording will be available in the YouTube channel within 24 hours, and I will do a blog post in the SharePoint Deathlok to follow up on things on that now, if you have any questions, if you have any issues, challenges which we were unable to address today, please join on our other community called the bi-weekly community calls and we'll try to figure out at right timing for addressing your questions or use the tech, community, Chevonne dev groups for asking assistance or cut the issue list which was mentioned in the earlier on in this call and record an issue and we'll try to find time to support in your question.

A

But thank you, everybody. Thank you, Shawn for your input. Thank you, everybody for joining. Thank you for a great interactive discussion in our window. I really love saying that, and he has we need some ultra music. Thank you Mark and thank you for for super valuable important on the internal on the functionalities. See you later, the bar everybody preciate.