Microsoft 365 Community SharePoint Monthly, 10 Jul 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: SharePoint Developer Monthly Community Call - July 2018

Description

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

Demos - Using Microsoft Graph custom extensions from SharePoint Framework client-side web part. Building extending footer for communication sites.

Detailed agenda an links to specific sections available from http://dev.office.com/blogs

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

A

Welcome everybody: this is SharePoint and developer ecosystem airship and developer community called also known as SharePoint PMP community call. This is the July 2018 edition, so it's July 10th it's summertime, at least in the northern hemisphere of the of the club, which means that a lot of people are actually enjoying their vacation times and all the time in past we. Actually, this is the first time ever. We actually have a monthly community recall in July for SharePoint PMP and we've been running this now for four years or so.

A

We typically always cancel to July, because people are always away so but then again the depending on. Where are you located in the club? It might be actually that winter time, so it's not like everybody is on on vacation right now. Now, let's get concentrate on today's topic anyway. So it's not about telling and what's the weather out there, it's about concentrating on the SharePoint developer topics and let me actually enable my clicker, which is out of batteries and it actually click in keyboard. That's I'm gonna fix this.

A

One I was while I'm talking if I can actually change the slides. Yes, again cool, so today we have some SharePoint developer news. So some let's say some news related on engineering work. What we're doing there are some updates on the roadmap, so some of this I I already actually explained last week in the last week, Thursday's call, which was the community special interest rate for around SharePoint framework. So we talked about the SharePoint 2019, but there will be there's an updated slide on that one in today's call as well.

A

Seven 2019 is gonna, go for preview relatively soon, so I cannot well I, do not remember even to exact date by myself, but it's happening relatively soon. So you'll see an update on down, but in this code we're gonna talk about what is the Deaf platform support ability within the SharePoint 2019? Then we also have two cool demos coming up today, one for Lewis Manus, which is around using Microsoft craft customs, schema extensions with SharePoint framework, really cool capability, as it's actually accessing the craft and accessing the customs definitions there and showing stuff.

A

So who is gonna start and then we kind of have a demo around to share one starter kit. The expanding footer, which we have on the shipment starter kit from Powell of the LRC and that's really around explaining how you can actually extend our the communication sites as well, because the modern experiences do support customizations and most likely, hopefully, let's see I will have some time for Q&A today as well, I'm trying to actually watch a time window as we move along.

A

But let's see if we can follow up on, what's actually happening on from a questions perspective now quickly explaining how the SharePoint developer community actually works. So we do have different layers of SharePoint developer community engagement, so you can only engage using a social media. You can go, for example, the ship on developer crew or space in the Microsoft Tech community, a kms SB, BMP, community or SP dev community, and that's going to be the location to have a discussion as questions.

A

You can see the engineering people like me and if I have time every now and then I don't have time. Unfortunately, we were able to denounce with those questions there. So, but it's more like a forum to ask have questions and discussions. Then we have pi weekly SharePoint framework community call, which is around the SharePoint framework and client-side development. So you can actually see cool demos and hear about the latest on SharePoint framework, and we also talk about office.

A

365 CLI, reusable SPF, X controls in those course and how they are moving along because those are open source initiatives. Then we have also biweekly special interest group called around shape and general dev, and this is isn't really that precisely defined what it is, but it's everything else other than SharePoint framework, and but nowadays we also include here the Microsoft flow and the power apps capabilities.

A

So every every one of these calls have also a demo around Microsoft crafts and power apps in the context of SharePoint, because those are getting a lot of love internally for an engineering side, and we want to show you how things are evolving, but there's also an additional stuff like what's new in season. What's new in p.m. via PowerShell and architectural designs, and then we have this monthly community core.

A

So if you don't have any any time to follow up on what's happening in the share and developer community jump on this monthly community course and we'll do a quick summary, what has happened in the past? Who's contributed who's done. What and then, after you call demos in this as well. Now a few numbers from June 2018 and just to show you that there are other people who are interested on what's happening on the ship on developer community. So in YouTube we actually did a all-time record.

A

In YouTube we had a 185 thousand watch ten minutes with 31,000 views in the in the SharePoint developer, YouTube channel, so critical numbers we're hitting roughly 1.8 million minutes watch time in a year, which is already a pretty decent number. It's kind of a period that we can't really sell ads on these videos and that would kind of be not accessed acceptable, so completely understandable in Kitsap.

A

The unique visitor numbers are growing quite fast as well, so it's cool to see that people are finding the github and they're able to access the information in github, because there's a lot of a lot of ready to use samples scripts tooling available for you to take advantage. So we had a 40 mm or 43 thousand unique visitors with two hundred and two thousand views in ignite in the docs. We had eight hundred and sixty thousand views.

A

So that's slightly down from me, but that is as expected as well as we move along and to spring and summertime in the northern hemisphere and then on the BNP, reusable components with today all-time records on the unique talents. It's thirteen thousand three hundred tenants. In a month we were using BMP, partial OPM pas, encore or BMP jeaious functionalities, and they generated more than 10 billion HTTP requests within the tune.

A

So that's the first time ever we actually break the 10 billion limit, which is really cool for the team to see that the adaption and approval of open source in the SharePoint contrary context is growing. All the time and most use capabilities is absolutely the remote provisioning capabilities in SharePoint tooling, because they are super powerful for you to automate provisioning of stuff automate configuration of existing sites or governance on the existing sites as well. Now what about SharePoint framework?

A

Like typically, we are not giving any exact numbers, because we don't have the a mission yet phone chef deeper, and we quite rarely actually give exact numbers on exact things and office traces if I have in general. But this gives you an expected from last September to day, that's actually until Sunday. So two days before today, the Crofts I'd, the use its bird user and then on the right side. The use its per tenants and it's interesting to say that we're seeing a even deeper growth on the use.

A

It's pertinent, which seems to be and based on our data, showed that more and more developers are actually using SharePoint framework into developer tenants and that will then generate more uses on the left side, so basically introduce or use its slightly later on when they actually start to implement when they actually start deploying their customizations on the production. Tenants, but really cool to say to adoption growing so fast and SharePoint framework is already by far the most widely used customization model in office 365.

A

So it's by far the most widely adapted and widely used customization model and office 365. So super cool designer now reminders on the guidance. It's a kms s, PDF dogs or dogs that make stuff comes last SharePoint. That's where the SharePoint documentation is nowadays. Msdn has been already shut down.

A

If, unless I'm mistaken, there might be in some sections which haven't been yet shut down, but they misty and will be completely shut down pretty soon and everything is transformed the detox platform so from here you can find all of the relevant coid hands around the shipment framework ship and add in solution guidance, gamma definitions. If you're still doing on-premises, which is completely acceptable as well ferry feature, framework guidance is available here as well, so all of the old stuff and the new stuff is found from a one centralized location.

A

The second thing which we're falling slightly behind do our engineering resourcing challenges is that you can always open up a issue and report to both us using the MSSP the issue list. This is the SB dead dogs repository and the issue list over there. If you find a generic issue around shape and development- and this is mainly because our yep and online support does not have expertise to actually help you. If you have a developer oriented question, so that's why they cannot really help you on that.

A

So we're trying to help you directly from engineering sign, but we're slightly struggling and do the high demand of the and amount of questions. Now, if you have interest and time and availability- and you want to help us on this journey and helping others in a community. Please go to this issue list and, if you find out in question which you can actually help, we which you know how to answer that question and help us by commenting on the on the actual issues and that will be highly appreciated by our team as well.

A

Moving on are things quickly, quick on plate on user voice, there's no actual updates in the top ten list of these user words, except the votes are slightly armed and the number one item is absolutely still the the managed metadata term store operations using the REST, API and taxonomy API, and something what I told actually last week. Also I think I mentioned this last week in the SPF X, as community call we're now looking into making this happen. Now, when that's a different discussion, I can't promise me a date.

A

I can't promise you a timeline but we're actively looking into making taxonomy taxonomy REST API available, because we also need it by ourselves now. The reason one of the key reasons when this has been slightly delayed is that it's just a matter of resources as well, now that our baseline meaning krupa, so sarah team sites and modern team sites and communication sites are already in a decent experience. We can start realigning our resources to this.

A

The document management operations and ECM operations so easy and document management operations will be the next big thing where we are concentrating and improving in the future, so looks to be really promising, and that will get this one. But I can't give you an exact date like mission. I will try to keep you up to date on on the hunch, but I can't really want to speculate, because immediately if I speculate too much, I will get burned internally in our engineering as well, because we can't promise your date until we actually have a date.

A

Second item in this list, which is gaining internally and also interest, and it's gaining a lot of votes. It's the dotnet core version of season and we can, for example, move to dotnet sorry power, core version of SharePoint Online PowerShell. Until we have actually done this, so we are highly aware of that requirement. We know that it's a number three in the list and it's again waiting for resources to make that happen whenever we get the ship on 2019, okay, anyway. So SharePoint framework library packages was the last thing.

A

What I, what I've noticed and before I got thrown out so library packages we're working on that one again, the same guys, we're working on that one are needed in there in a more critical things right now, but we're looking into making that happen relatively soon and many other items in this user watch list as well. Now, let's go to the next slide quickly: July 2018, summary.

A

Obviously, there's a we released a new version of SharePoint 25 shipment framework 1.5 point: one is the latest version, there's new client-side web parts and extension samples which one came out. We're gonna see some of those today or one of them Louis and then then other ones well, older version. All the sample act from a shipment starter kit from then from Apollo, numerous updates on the existing samples moving them from previous versions.

A

The latest ones and updated documentation and guidance and BMP component sites, there's a new version on the BMP JS library and a reminder on that one. So the classic BMP JavaScript core library is now deprecated. The BMP jeaious library is the run one which you should be using. So if you're looking into using the BMP chase or some PHAs capabilities, please use the BMP chase library, because that is now the preference.

A

If you go to our monthly summary, you'll find all of the needed links all of the guidance of making the transition to happen over there versions of the BMP reusable she opened framework controls for property buying and content and plenty of other updates, so the shipments target being one of them as an example.

A

The documentation is getting better and better based on the contribution, what we get from the community and what we're able to do ourselves as well now on the list of people, who've assisted this getting the the names are getting smaller and smaller, because we're kidding it's gonna, be a hard time pretty soon to fit this in a one single slide. I'm not gonna mention all of these people who are on the slides, but thank you. Thank you. So much for your help on this assistance.

A

Assisting us on keeping up on to date on the demand of the open source, community and demand of the of the samples and guidance and and changes within the existing projects and the SharePoint community is one of the strongest technology communities out there, mainly because we're willing to share we're willing to help we're willing to spend time on assisting others, because we actually get back the others will help us back sooner or later as well, and and it's it's mind-blowing to see how much people are helping each other and it's mind-blowing to see what kind of customizations and contributions people are giving us back with a super variable.

A

So thank you. Thank you. Thank you for your time. These are the the number of companies and all of the companies which we have a permission to share in this course and in their slides. So thank you for these companies for chelating their employees to spend some time on the open source and contributing back for others in the community and super valuable for everybody out there. So thank you. Thank you. Thank you now.

A

If your name was on the previous slide, but your company is not here and you would like to have the company here, please contact me Burt or Patrick, and and give us a permission to get your link, and a company name mentioned here so next time when you will have a contribution, we're able to share your company name in this list as well, good and Microsoft side, obviously to build a list of people, there's some new people here, some old people are already left, but there's this too broad set of people basically contributing on the Microsoft side.

A

We do have a pretty strong community internally, actively participating on these things as well. A lot of these people are engineering company from organizations, and a lot of them are actually also from MCs or internal consulting side of the game as well, and our technical writers and so on. Now are the reminder on the PM based on target and the modern experience is just a ring minder on this one, we're not going to now today to really detailed Emma on the starter kit, but Apollo is going to demonstrate some of the capabilities in this one.

A

This is a crate, crate, crate, starter kit for you to understand, what's possible in SharePoint Online in the modern experiences it is already right now. Those web parts which are in the starter kit are the most widely used web parts globally in SharePoint Online, which is pretty cool.

A

So if people are clearly using the starter kit, they're getting excited on the starter kit and making a lot of valuable feedback on this one as well we're looking into on this PMP starter kit, we're looking into making this more easily approachable and and for you as well so buy ignite.

A

There will be a website where you can sign in as a tenant administrator, and you can basically click a button and select what kind of content you want to provision, and then this will be automatic process to actually get the starter kit installed to any tenant in the future right now. This requires the PowerShell execution skills.

A

So you need to execute a one powershell script as a tenant administrator, and it's gonna then configure everything for you, but it's really meant to demonstrate from an end user perspective, what is possible in the modern experiences and also how to implement those things as a developer, so but it's definitely not just for developers. It's also for business, analysts and consultants and end-users to understand what's possible in here now. Moving on. Are things quick update on the roadmap high-level update on the roadmap.

A

So one point six of SharePoint framework ETA is still end of July, we're looking into having one of the SharePoint framework releases before ignite, so it might be channel I. It might be early August we're running slightly out of time, which is pretty typical to be honest, but we want to make sure that we we will get a one release between now and ignite.

A

So that's gonna be one point: six and one point seminars and a baton in ignite in one point: six we're looking into having dialogue framework GA we're looking into having native craft access from SharePoint framework as at ghe I'm internal availability.

A

So it means that it can be used in because everybody's asking for this capabilities when trying to make that happen, I'm supporting react, 16 preview of socket IO, which is something what we demonstrated in some of the community calls, and also having a native yeoman supports for SharePoint 2019 I'm, going to talk about 719 in the following slide as well. So don't don't be scared if might be delayed for one point. Seven one point: seven is scheduled now for ignite, so that's gonna happen, end of September and then by ignite.

A

We should have some of these teams capabilities to preview for you, but that's now scheduled for the ignite release show up on 2019 on that one. Let's talk about that one after well! This is basically a repeat from the previous slide. So sorry for that I'm gonna jump on the following slide, so 2019 on sharepoint 2019. It just be super clear on this, and this is still preliminary plan, so it is subject to change, but the changes will be pretty minimal for preview release. So preview will happen summer, 2018 so relatively soon.

A

I cannot give you a date, but it's gonna happen relatively soon, regardless it's gonna use, SharePoint frameworks 1.4. So anything what is in SharePoint framework 1.4 from a client-side perspective will work, but it doesn't mean that everything in the server side will work as such, so the in SharePoint 2019. It will support modern pages. So modern experience is modern lists and everything like that, and it will have a modern theme site.

A

It will not be a Krupa, so static theme site because of hysteresis threat groups are in online, so it will be a modern theme site. Without the crude capabilities it will have a where's, the SharePoint group, but it's not the office straightest fat group capabilities and obviously will support communication sites as well, and we will support chip on framework extensions, so list.

A

Few common sets have field customizers and application customizers in the morning basis and modern lists, as well with hooks supported as it packaging's reported so you're able to deploy your SB pkt for us in that catalog and everything will be hosted for you automatically. So you don't have to worry about the actual hosting of those assets. The no CDN on the yes section means that there's no office 365 CDN because again we're in on-premises. So we can't really host stuff for you in office.

A

Traitors survive because we're in on-premises, : formatting will be supported in the in the modern Western libraries. So that's pretty cool tenon scope, deployment and ALM api's are still unclear. We're looking into potentially making them happen. It might be that we were missing the preview, but there will be an RT M, but we'll need to clarify that one are still in the engineering. The staff woods will not be in SharePoint. 2019 is site designs, hub sites will not be there site. Collection of catalog will not be there and then on properties.

A

This tenant properties is the the SPF X. Well, it's not technically an SPF X thing, but tenon property is where you can store key value pairs in a tenant level and then use a POS to read them. The site. Collection of catalog channel properties will not be there in 2019, but this should clarify you kind of what will be there and what will not be there. They are able to start thinking and what's the implication of certain things, good question include clarification from Louis. So does this mean that no sharp Ontarians in 2019?

A

No, no, no sharpened aliens will be there they're not taking anything away. So definitely everything what's in 2016 will be in 2019 as well. Classic experience will be their shipment. Add-Ins will be their farm. Solutions will be their sandbox solution will be actually their code behind sample solution will be deprecated, but it will be their deprecation means that it's still supported, but we're not investing anymore on the functionality. So don't get fooled.

A

I concentrated here on the modern capabilities, but obviously all of the classic things will be there still and nothing is taken away from you and you, as an admin administrator, can control what kind of sites you are actually creating. Are you creating a modern team sign, or are you creating a classic team site, so you can absolutely use keyboard, use and classic and a farm solutions in them? If that is your preference, don't get confused on that? That's a good comment, though Louis we need to be more specific and remember.

A

They explicitly call those things out. Orchid orchid in general, SharePoint aliens is 100% supported in SharePoint Online and we have no plans of deprecating SharePoint Allen's. We vice-versa be looking into investing on the a dental and the the ideology of add-ins in the future as well shape on 2019. As you can see, SharePoint 2019 is based on what we have in SharePoint Online.

A

The reasons for that one is that Shepparton r19 is exactly the same codebase a shipment on line from April 2018, so we've taken to April 2018 internal version from SharePoint Online, and then we ripped off all the functionalities which cannot work in our premises and then we're packaging that as share 1 2019. It is a good reminder that is cloud. First, all of the latest and greatest capabilities go always to cloud, so you will not see anything like mind-blowing Oh from a UI perspective which it's not in cloud.

A

It's always cloud first and then on-premises and this again code is asking and do I have a web page. That points all of this information and what is and what will be deprecated would be nice to be able to share and that with our customers. Absolutely agree on that.

A

I haven't had a time to write that bit yet so it's just matter of timing and resources as I'm looking into getting that out relatively soon- and this is still speculative and that's really the challenge in here, because and that's why we can openly say it in a community call the challenges that really we shouldn't have a speculative page too much in the introductory facial documentation, but fair point I can actually.

A

Let me put my carrot, create myself a note, post-it note where I'm gonna add a note to myself that create a page for 2019 and their platform, good input, because that helps on then communicating what's will be there and what will not be there and they will say the clearly has been some confusing than this also feel free to take a screenshot of this one and share it in Twitter doesn't pretty matter. This is not an NDA stuff everything. What we have in this course are 100% open to be shared. That's really.

A

The whole point of this community calls now, let's actually move on away from there I'm going to answer any questions than the iron window. While Luis is starting his demo, but we really need to also go to demo section, so we will have plenty of time for those as well, so Luis you'll be going first and okay, an.

B

B

A

Okay, we can hear you okay,.

B

A

And on Louis's demo, around much of craft custom, stem extension use its own shape. Remember one thing to remember is that more and more in the future, we as a Microsoft we keep on pushing pushing the Microsoft graph as the de facto APR structure now right now, currently in 1.5 version of SharePoint framework and the graph API is are not yet officially supported in production, but they will be in the future and we're looking into making this this better and better in the future.

A

So the crafting the creation of graph API are super important part of the shipment development, but at least we can see a screen so take it away. Good.

B

Thank you missed a good point, so yeah in this sample, I'm gonna show you how we can extend the Microsoft graph to store our custom data using word is called the graphic, schema extensions and wait an update from an SPF X webparts, so well sooner or later, I'll eat your colony first or your custom data in English entities.

B

Possible business scenario can be to extend User Profile, with data coming from an HR system like adding the employee, ID or data related with payroll processes or whatever or like in this sample extending groups and that are being used to working for instant beef projects with information like business, you need estimate, budget or closed date or something like that. Information related the bid so before diving into the code. Let's have a quick look to the two different options we have to still graph.

B

Actually everything is pretty well documented in this link on here also know that not all the resources are super with a custom extension. So, as you can see in this table, these are the resources that we can extend using graph extension, but pretty much the more common entity such as far as I, can see. So you have users, you have group messages, events and so on.

B

There's a couple of options in order to extend the graph with your custom data. One of them is open extensions and also we have X key. My extensions open extension are more a more likely withstand date and is easiest of each Inari. We give you a key value purse. While the scheme extensions are a more type way to extend data, it's pretty similar, like creating a class with specific properties in encode, for instance.

B

So with a scheme extensions, we can also say that the data in the in distance units are filled through citizen and you're gonna be able to select that feel, filter, invite that feel and and so on, which is not possible with open extensions. So I'm gonna show you.

B

Regarding the scheme, extensions also know that there's a lifecycle of this tension, as you can see here so when you create the extension it can be in these three stages in development available and they're protected, and the main different is that only the owner up and we'll take a look to what that means. In a in a minute, he's gonna be able to add the extension in the in development or any owner up is gonna, be available, an extension here for any other.

B

Also when you create the extension, you're gonna define the properties for with a specific type, and these are the basic styles that you can use more or less the same basic typing in CSR strain, integral and so on, and the good thing is that if you try to date, a value with an embodied by Lee in the in the property. So if you try a string in an endeavour, property you're gonna get on the road directly from there from the graph API. So it's much more type using a schema, estima extensions.

B

So, in order to create an ik schema extension, I can show you here using the graph is plural, and this is a great tool for working with with the graph API and to create an iced-tea.

B

My extension is not possible vehicle from the SPF X because of the permissions that you have when you are using the graph HTTP client, the we'll talk a bit more regarding permissions in in a minute, so in this case I'm using the graph Explorer, but basically in order to create the extension, is just a create opposed to the ischemic extensions endpoint and provides some information in the in the body as a JSON object. So you can create.

B

You have to define an ID and there's two different ways to create that ID, and this is also documented on here. It's a bit we're in my opinion, but you have a couple of options.

B

You can use your verified, don't mind and do something like the mine underscore and whatever that you want to introduce, or you can just set any other name and graph will generate the prefix auto-generated and- and it's gonna sign to the to the extension, keep in mind that in order to get data from that distinction, you're gonna have to use this ID. So I think it's much more. You see if you can't provide your mind, understand worry about that. How to generate in a prefix. Also you have to provide a description.

B

Is any any description that you want to apply to the extension and also their owner. This is the client ID of any ID, your ID application that is registered in the rad, your Active Directory- and this is important because without providing the owner does not gonna work, so you have to specify module ID up client ID over here. This is one of my absolute have registering in agile activity.

C

3 then, the.

B

Target types, so the extension is gonna, be applying in this case two groups: this is the Sun arise. We can specify all the different entities that we can Astaire's or group users or or whatever, and then the list of the of the different properties with the name of the type in the sample. We are having this three strain: integrand defined properties to so something in the in the demo. I'm not gonna, run the query because I already created the extension.

B

So once this step position is created, we can get the information to ingest I get in this same endpoint and we can using the ID to filter. So you can see here my extension with the specific ID yet type and the different information, and also the status that by default, is set to in them.

B

Okay, also when you want to get information from a from a specific entity. So, for instance, here we are querying a specific group in the graph API and, as you can see here, I'm getting the ID and display fields that are out-of-the-box fields from the from the group, but also I'm getting my custom extension. So you can see here the the wrestle with a different properties in the in the customer stencil, and also the good thing as I said before, is that, with the scheme extension you can use these fields later to filter data.

B

So we can do things like. Okay, give me all the groups in graph API with the idea display name an extension but filtering that was that the business unit in my custom extensions is equals to manufacturing in this case, so we are getting a couple of groups and obviously, which is that that's not gonna work and it's not written in any any group. So it's a very powerful way to extend information and custom data in there in the graph entities. So, regarding the the permission, well, let's take a look to the web.

B

This is the web part from the from the sample is already and in github, and what we are doing here is running locally in the SharePoint whirlwind. So when we reference the page yeah just get in the custom extension from the graph API and just rendering that information in the in the screen- and obviously we have the updated option. So we can say like now.

B

The business unit is with tail and let's increase the estimate budget and let's change the perspective close date and let's update so well I'm, not updating the UI from the demo, but in the console you can see they template is successfully and if we refresh the page, we're gonna get the new the new badness in there in the group and also if we run the query and.

B

We see finding the right group is that one yeah this is the new emulator, retail and estimated budget and so on. So this is how it work and in the network, if we take a look to the way that we are doing to get the information there's, we are using the HTTP graph client. So there's a specific.

B

We were in token that you can see down here and if we get that value and because they token I already did that with an on with an old token, you can see how this is. This is the ideal active directory that is registering you know in our tenant in order to use the HTTP graphic Ryan.

B

So, as you can see here in the scope section- and these are the permissions that you have in order to produce graph- and in this case at least at some point- the only permissions allow is the read and write all groups, reports and user read. For this reason, we can't create a specific customer stanchion deity from the from the SPF thanks. However, what we can do is get the value and update the value in a specific group, as we have to read and write all permissions in there in the application.

B

Ok, so jumping into the code. This is just an SPF X web part. The web part is pretty simple, because it's just loneliness specific we have component and set in the context to this component, so every automatic is actually happening. The happening, the react component, so when we have some own things fancier, this is just updating the the react component estate with the different values when you type in in the test box and so on, corners with heart fear in there in the UI. So this is just updating the state of here and also here.

B

This is this is not working as I said. We can't create a schema extension, but I they call them. Vehicles can be can be useful for for future in case that you can create it from from SP FX, or at least you can see how it looks in order to to create and use group Explorer or any other custom app that you want to use and same.

B

If you want to update the user entity, that's not gonna work either cause the permissions are only for for groups, but in this case we are. We are the same groups. So if we take a look to the render method, this is there are some tax payers with with the specific UI that you've already seen in the in the web power and a bottom to to update the data. So when the component is more when what everything starts, we are calling these get. Customer station and updating the reactive stayed with the value still get.

B

Custom extension is just using the HTTP. We are planning provided by SPF X in the in the context and giving the group ID also from the context and just run in the decade requests and getting the information in a specific interface. That's the winter face and just updating the D estates in order to update is pretty similar. You can see here the a function. So again we are getting the group ID from this is the group that is, we hide the specific site, insert point that we are using. So we come back here.

B

We have this more than with inside. So, as you can see, here is the modern, thin side and the specific ID. So we are using the offices to fight group behind this SharePoint site and we just need to do a partial request in this case specifying the custom extension properties with the value using this JSON format and prevents the query to the specific group. Id and everything is just updating and well then functionality that you've already seen in the in the web part. So that's pretty much everything we can really.

B

We can update customer station in in groups at this point using the HTTP they are flying and I think it's really powerful way to to provide custom information to to graph, in this case, to our groups in it officers defined. So any question feel free to.

B

A

Actually so Paulo you can take over the screen sharing, but while you're doing that, just to kind of reiterate some things here so obviously the toughest resist by extending office 365 group is an awesome example of a schema extension usage because there's no such object in SharePoint, so in SharePoint you could actually use stuff like User Profile, to get additional properties for the User Profile property or the individual user. On the other hand, that's only for SharePoint and what's good about the office. 365 group and schema extensions.

A

Is that the same extensions then available for other applications as well, so it's not only for SharePoint User, Profile properties as an example for user only for ship one, none of the other applications will know nothing about that one.

A

So there was a cute comment: I think it was I, can't remember, which one put it adding a custom schema extensions on the users in Azure ad is a one way of getting around of the limitation of the User Profile property, less pretty string limitation, which is 3,600 characters and I can't remember who actually bought it yeah it was Leah. Thank you. So that's that's one way of thinking the thinking and aligning potentially well sooner or later.

A

We need to do something as an engineering for the SharePoint user profile right now, there's a lot of capabilities in SharePoint which are dependent on now. If your solution is already using my soft graph and already has two right scopes, adding your custom properties that the actual user object in Azure ad is more profitable option than doing the same stuff in the user profile. One of the reasons for that is that you can actually automate the azure ad modifications by using an API user profile.

A

You would have to do one by one within a a tenant level, because there's no API is that use custom properties for a user profile, probably what's hopefully made sense. We're talking a lot. Sorry for that, so Luis. Thank you. A great demo absolutely create demo. The sample link has been added on the online window, we'll put it in the video notes as well, when the video notes will be in the released in the walk-in as a blog post, but Paulo get there.

C

Okay, thank you, hello, everybody, and let's talk a little bit about the extensions and specifically about one extension that we have in the SP starter kit. Here you can see the github repo for the starter kit and just brought in the chat area. The link for your reference, the SP starter kit, which already said, is a solution open source solution sample that we provide based on community forth and full of sample web part and sample extension. You will have source code fuller of these components.

C

Then today we will talk about one specific component, which is the footer extension for communication sites. We call it portal footer this extension. First of all, let me show you it from an end user perspective and then we will see how we implemented it in the source code. It's a footer in a modern page, the end users can click on it and there is a nice moving menu item which will pop up on the screen providing a bunch of useful links to the end users, including a section called my links, which is made of you.

C

Custom link said that an end user can customize for himself or herself and in fact, by clicking on the edit button in the UI of the portal footer you can see. There is a dialog window that you can use to edit any of the existing links or to add a new link. For example, I can add a search engine and I can provide the address for being.com. Just make an example. I can add it this list of links if I click on the Save button will be stored in the User Profile Service.

C

We just talked about it, and maybe this that we can think about using the graph extension for doing that, as well as just as an example. But right now we use the user profile service in order to share those personal links across multiple site collections within the same tenant from a SharePoint Online perspective and, as you can see now, I have my search engine available in the my links section of my footer.

C

So now, let's see how we can implement such kind of extension using SharePoint framework, and so let me move to the visual studio code editor. This is the main source code file of the portal footer application customizer. You can find it under the solution, folder of the SP starter kit and in the source folder. There is the extensions subfolder in which you find the portal footer. Well, the portal footer application customizer is a SharePoint framework application customizer, which allows us to provide a few settings when we configure it on the target site.

C

We have the title of a list that we use to store all of the link items that we have in the footer here. So applications internal models and news are all items that we have in a custom list and I will explain you where this custom list is stored in a matter of few seconds from now.

C

Moreover, we have a couple of texts for the copyright message and for the support message, and then we have the name of the property of the custom property that we use in the User Profile Service to store the my links of the currently connected user.

C

Once we have the extension configure with those properties in the on init method of the extension, we first of all retrieve the URL of this side of the root side of the hub site in which we are. In fact, we make an assumption. We assume that this extension will be a mainly used in the context of a hub side. Actually, we support also this extension in a communication side which is not related to an OP side, but our prefer.

C

The usage context is the one in the hub side and that's why we have a function inside the code of this extension, which will get the hub site URL. Let me show you what we do inside this function, using the SharePoint REST API, so we connect to the current site, URL plus the well-known underscore API the website, and we get at the hub site data information using this URL. We will get back a response. We take and show you how it is presented.

C

This is a request that I made using telluric fiddler, and here you can see we get packages, an object which will have a value property which inside is made of an inner JSON object. I already got the JSON and using any of the JSON viewer that you have on the web. Here you can see what's inside that have that value property. As you can see, we have the hub side, the name we have the URL of the main site for the hub.

C

We have the navigation items so that we can see what are the navigation elements for the navigation shared across the sides, but in the same hub and so on and so forth. What I am interested in right now is the URL of this side and in that the information I use to get the URL of the main site for my hub site. Why am I doing that?

C

Because in that side, I am storing the list with all of the links so that we can share all of the links across all of the sides in my hub site? That's the basic idea. We had to share that information across all of the site in the hub.

C

Then we set up the TMP JS library and we do that using the setup method and providing the base URL for SharePoint targeting the upside URL, so that when we will use the PMP JS library in order to get a reference to the list with all of the custom links, the PP J's library will target the hub site URL that we just retrieve the using the REST API of SharePoint. Moreover, we collect some useful settings from the properties.

C

We double check to have all of the required properties and we render the placeholder and that's the interesting part in the render placeholders function. We simply retrieve a reference to the bottom placeholder of the page, so the footer basically, and if we have the footer, we load all of the links from the SharePoint list in the up side and we render a portal footer controller which will be made of all of the groups of links based on the links we just retrieved from the list from the configuration list.

C

If I dig into the load links method, you can see here we use p.m. PJs. In fact, we do SP dot web dot lists. We get the specific lists we are using to store the links we get just the properties we need and we retrieve the top 100 items which should be enough for a footer I think so at least we order them by grouping by title and we use caching, which is a really killer feature of p.m.

C

PJs, because we have out-of-the-box caching through DPM PJs library, without the need to implement our own caching logic. We also use the synchronous pattern close to the c-sharp one, because I'm and I was originally sous-chef developer, so I really love to do a sink and a waiter. Then then, then then, but that's my choice and once I've got the items from the list, I can simply map them to an array which will be made of all of the items with their group with their title and with the target URL for every single item.

C

Moreover, because I have my custom links, optionally I could have my custom list links in the user profile service I also use an SP User Profile Service, which is another type you find in the common folder of this project, and there we have a get user profile, property method which will retrieve from the user profile of the currently connected user.

C

It's doing property which will be a JSON, the Jesus realization, of an array of links which will be de my link items and that's what we do to get the thingy all of the custom links to be fair.

C

If we don't have, at the user profile level a custom property to store the link items, we can continue on running the extension and we will simply skip the my links section once we have done that, we are ready to render the the portal footer control, which is a react component which will do the rendering of all of the items group by group and, moreover, we also have the action button for the for handling.

C

The expansion of my footer here, as you can see, I, can expand or close this menu using this default button, which will handle the toggling of my item and inside this component. I have another react element which will do the rendering every single group of links that's from a market textural perspective and from a controls anarchical per spec. They were thinking about what we do with the react. Moreover, whenever the end user want to edit their own links there, they are my links.

C

We have an edit links function, which is based on a custom dialog ax. So inside we use the SharePoint framework dialog framework. This dialog is shared across multiple extensions that we have in the starter kit. We use this dialog in the portal footer, as well as in the collab footer, which is another footer that we have in this solution and that you can see in action in the HR team side, for example, and as long as the god of network will be with me, I will show you how it behaves come on.

A

Loading will get there well.

C

A

Actually, loading, let me let me explain one question what we do paid upon a long time in the in the team who was implementing this is that, where do we store those personalized links and we decided to go with the user profile, SharePoint user profile and not, for example, schema extensions in the me object in craft, which technically you could have actually saved some information in the me site as well.

A

The reason for that one is that, then it's not requiring any craft scopes, but just as well, you could implement that kind of an option and get that implementation or the the personalized links stored inside of the of the craft object as well. Yeah.

C

I'm waiting for the footer, let me try to refresh oh no. Was there too late? No sorry about that. A fast yeah I'm too fast. So this is the collab footer and, as you can see here, I still have the my links and I still have the links that I had in the other side, because they are shared across multiple site collection within determine because they are stored in my user profile properties.

C

So back to the source code that my links, dialog, is a dialog component built using the dialog framework of SharePoint framework in the air. I simply have a dialog content control. Let me scroll up here: oops, faster okay. This is my dialog. The content, which is a react component and inside the content.

C

I simply render, but all of the stuff I need to provide the editing panel to edit a single link item so to add or update a single link item, as you can see here, based on the show detail panel flag or on the other side, I can show the full list of link items with a common bar on the top and the detail list to show the full list of items these settings of the detailed list.

C

For example, the columns I want to show are defined here with a constant variable which defines that I want to show the title and the URL column of every single link whenever I save so I hit the Save button of my custom. Dialog I will simply update the collection of links that will be returned to the consumer.

C

Application, which would be my extension and I, will be able to store them back in the user profile as a string, as you can see, and as a jesting with students, ID array of the items and, of course they refresh the list of links and that's it from a development perspective and, as you can see, using a sharpen framework using react, p.m. PJs and all of the services provided by sharepoint online. You can build a pretty nice solutions which really fit in the UI and in the user.

C

Experience of the modern UI of sharepoint online now.

A

C

A

Before we go to the slides and we're running out of time, so we need to close up, but can you actually scroll the footer? Can you scroll down? So this is one of the things which people need to be at the moment still aware, so the footer is kind of a floating. The footer is on top of the content, and this is something which we are currently working on in the engineering.

A

So as part of the matching of the capabilities, what you can do between the communication side and classic purposing, we will absolutely get you also a non floating header and man loaded floating a food or meaning kind of a footer which is inside of the content. So it's not on top of the content. So all of that is now under development. Again, I can give a timeline exit timeline, but it is under development and should be coming the sooner or later.

A

So it is something which we note that it's a gap because right now, the if you scroll down hi to the the extending one, but you can clearly see the challenge of the of the footer. The reason why this one is extended is basically that it's, it can have kind of a make a folder capability, and you can always ask it to show additional information and then hide it. It was just my design of trying to figure out how we can do classical publishing site experiences and inner communication sign.

A

Now, like noted on on the previous URLs, the start gate is available in a github, so say no to Megas and in the github you can actually start using the code. You can pull down the code. You can use to reuse the code. You can read back its code, you can do whatever you want with all of this assets. It is all free, MIT license. You don't need to worry about I using anything out of that and you get just as well. You can use it in your own implementations. Now.

A

Can any of the PMP starter kit be deployed on Chevonne 2016, and the answer is unfortunately note because to limit this to SharePoint framework 1.1, like you general know that we're looking into we, we just was talking about the fact that we will actually split SharePoint starter kit to multiple packages in future. One of the packages will be then targeted for SharePoint 2019, so you can have some of the vectors in SharePoint 2019, even though some of the webparts are using the latest and greatest and preview capabilities.

A

So potentially we might actually have three different solution packages, one for preview capabilities, so target release, tenants, one which is for sharepoint online, which is not working in on-prem and one which is containing the stuff which is working in on prim plus shipment or not. That is adding additional complexity on the deployment, but we'll probably make that happen. So you can really easily reuse those web parts which are available inside of to this package, computers asking a lot supported in 2082, which was a twitter discussion from last week.

A

Yes, I think I disclosed that there will be 2082, luckily actually check deeper, confirmed that as well. So that was a good discussion anyway. Have a look on this happen. Starter kit will keep on evolving that give us feedback we'll keep on evolving the documentation on that and please keep on using github social media user voice.

A

All of these channels to let us know, what's working, what's not working if you're interested in doing demos in any of these calls by yourself, just let us know and let's stay in touch but Thank You, Luis, Thank, You Paulo for crate demos, AKMs SP PMP, the one URL to remember for additional information around the sharepoint developer community. Thank you, everybody. The recording will be available within 24 hours in the typical youtube channel. Thank you very much.