Microsoft 365 Community Development, 14 Jun 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: General SharePoint Dev Special Interest Group (SIG) - June 14th 2018

Description

Recording of the SIG from June 14th. Latest SharePoint Development news from engineering. SharePoint Developer news and cool community demos.

Microsoft Flow and PowerApps news. PowerApps tips and tricks and advance site provisioning techniques with PnP Provisioning engine.

Detailed agenda and covered topics are available via the Microsoft Tech Community (http://aka.ms/spdev-community).

Download recurrent invite from http://aka.ms/spdev-sig-call.

A

Welcome everybody, this is to share preparation. Practices by weekly community call around the generalship on development, and this basically the whole call is all about the everything else, except the sharepoint framework and the javascript and client-side development topics. So we basically cover into in solution designs. Provisioning is a big thing.

A

Obviously, in SharePoint automation, API is flow and power apps, it's a relatively new thing into here, but people want to have those covered in this course, so we will cover them in this course as well, and now that I, please, please, please remember to meet yourself when you are in the school, so we are won't. Have that much background noise. Thank you. Thank you. Thank you. So I'm using a few people from here and there we go.

A

Doot, so so in this callback set, we talked about all of the other stuff and SharePoint framework and provisioning, big thing: PNP, PowerShell p.m. a site, score seasoned and all of those things. Big thing. Microsoft flow is a crowing theme here as well and the power amp. So we will have typically from this moment forward or starting from the spring might at least the one demo or within this course around the Mike's of flow and power apps as well, in the context of sharepoint or in the context of office.

A

Tre testified because there is a clearly a demand for that, and people are highly interested on those things as well. Now, if you are interested on participating on this community, you are absolutely welcome to join on this course and do a demo or show a technical pattern related on season. Rest powershell use, it's a sure usage such a function flow or whatever. We actually have a pretty nice queue. Already.

A

People queued up on this and doing this demos in the community call, but if you're interested on joining to ping me or checks or Earvin or anybody from the core team doesn't really matter and we'll figure out what is the suitable time for you to do the dinner?

A

You can absolutely also contribute in the sharepoint github organization or the BMV github organization, and towards our open source projects which are available for you to get your contributions in and obviously when you contribute, you will get acknowledged in our monthly communications and in our monthly recurring monthly community calls so you're getting your name mentioned, and potentially our company mentioned as well now, and you can absolutely also provide a feedback using the social media and other channels as well, and that is absolutely more than welcome, because we in there shape on the engineering we need to understand what's wrong.

A

If you don't like something, if something is wrong or something is missing at please, please, please let us know so we are able to address that within the sharepoint online or in on-premises.

A

Now a few things around today, as I will have only short few slides, which I wanted to go through before we go to the actual demo section, so some general announcements, the typical slides, which I always have here and few other ones and then we're gonna- have two demos: today's forum, so from a Kel around the ship on power, apps tips and tricks, so he's gonna show some cool stuff over there and then a urban one Hoonah is going to talk about the admins provisioning scenarios in the shipment starter kits earlier today we finally got the blog post out around the ship, one starter kit, which is a crate.

A

Let's say reference solution: how to extend out-of-the-box, modern experiences so building client-side web parse building extensions and all of that so really cool stuff. We should have time for Q&A, so I've tried to be fast on my section, so we will have enough time for the demos and we'll have enough time for Q&A as well. Cool now documentation guidance, I promise to keep this one in here until the 8th, January, so basically aka, MSSP, dip docks or dosed at microsoft.com. Slash sharepoint and you can find the developer documentation in here.

A

Msdn will be actually shut down within two weeks by end of this month, and we are currently still in the progress of my creating, for example, API documentation, server-side API, documentation, documentation and some other stuff too deductive platform dog stop microsoft.com platform, but all of the relevant stuff. All of the new stuff is already in the dost of my software comm platform, we're also looking into moving out or actually creating the relevant documentation related on Microsoft flow, Microsoft and power apps in the context of SharePoint inside of this location.

A

So you'll find additional content here as well. That's something which we create earlier this week with checks, and we have a pretty nice plan on making sure that you can find what's relevant within those topics for you as well, using this one single location now. The second thing kind of related, partly related partly not related, is the the issue list, and this is something let me be again super clear on this one. So the SharePoint Online support, if you call and I used the tenant support in from your office.

A

365 tenant UIs and then you open up a case which is related on API or development. They are not actually supporting you on those questions or those reports because they do not have the skills to do that, so they basically have all say that. Well, we can support you, because we don't know how to do that, and and for that reason we have then open up this issue list where we in engineering be twice a week at least twice a week.

A

We will do a triage on this list and then we decide if there are birds and critical things to jump in or if they are something which are our engineers will process as we move along on on those topics. So we prioritize this issues at least twice a week, we're still slightly behind of catching up the situation from me, but we should get it up to date relatively soon.

A

Now one of the things which we announced earlier today on the world we've been announcing this and demonstrating this for a while already, but there was a new blog post in depth of home, slash blocks related on the details and the thinking behind of the SharePoint start again, and the shippin starter kit is something which is available in the github as a open source project where you can at what you can use to learn how to make development on the modern experiences.

A

So, ok, miss SP, dev, starter kit is a redirection directly to the kit on. There is also a blog post in the depth of stud. Comes last blocks around this one and there's actually a new video as well, which is showing what is actually the SharePoint starter kit all about. So how does it actually work how to get started? How does that behave? The DeHoff color of this one is orange and I do apologize for some reason. That seems to be a big thing for some people, everybody.

A

It's like why orange well orange is my favorite color, which apparently is a weird thing for people as well, but you can absolutely flip the color on the on the experience out on the resolution really easily using office racist five feeling, like you, can see from the pictures over there like mention quickly. We've shown this quite a few times as well, and there is more than 15 wet points inside of this package. There's seven extensions, their site, design, side, scripts, taxonomy, based implementation, User Profile, based implementation, a lot of other stuff here as well and.

B

Sorry to disappoint to disappoint. You also maybe photos to interrupt. You me me, including and many other people just see the title slide of your deck and I actually restarted Skype already twice.

A

Okay, so this is that's a city, so okay I think pretty far so good.

A

So that's ten minutes of read every starting from scratch. Cool now.

B

Would know it's moving now it's moving, but.

A

Somebody else is actually now moving that that's now the weird thing so I'm trying to now take an ownership of the presentation. I was.

B

A

So now, I'm, actually how it cool so yeah a documentation. Akms s/pdif Doc's, like mentioned issue, lists a gamer's SP dev issues as well. So that should be clear clear for everybody and the ship wants target a chemist, s/pdif starter kits, and here we can see actually the pictures. What I was referring to so the green one blue one and the black one, just the fleet of the different themes which are available in office traces to five themes.

A

So the orange one is the default one, but basically we're just showing how to deploy a custom theme to the office 365 tenant. So it's just demonstrating how things can be done and you can then changed changed everything and in in a way of what you want. But this is really our Browns showing how to build an end-to-end solution and how to extend out of the box communication sites or out of the box team. Sorry office, 365, crew, passers, edit team sites, so modern team science.

A

There is more than 15 web parts, 7 extension site, design, side, scripts, custom, VM deployment, it's the least actually relatively complex provisioning script as well. But it's super cool because it is actually creating multiple site collections and configuring. The tenant, end-to-end and erm is going to explain how that script actually works later today, I said within his demo supercool automation, stuff here- and this is an open source community driven development. What also right now there are certain, for example, limitations on this one.

A

This only works for target release tenants, so you have to use the first release or targeted release, then on option, and it has to be an English tenant, and we do know that that's a nasty limitation, but for now inside of the scripts, there are dependencies around the blue library, names or document library names, so looking into having all of that resolved in the future.

A

If you want to help with a pull request on fixing some of this stuff, that is absolutely more than welcome because we're doing this as an open source initiative as well, so we're spending our own time on evenings and weekends on fixing some of this stuff. So it's not like this is our day job as such, but really cool, stuff, really cool solution. You can easily set up this to any tenant.

A

We do recommend that you would use a testament or developer tenant because it just deploy stuff in the tenant scope, so in other users would see the side, scripts and side designs, the taxonomy options and all of those available. So it is better. It actually tested in a different Center. Now, if you only want to have some of those sweatpants like the tile spec part, which is quite widely actually already adopted, and the TAS web part is part of the SP pkt for the solution package.

A

You're able to you don't have to use the provisioning script you're able to just download this PDF while the web part file on the solution and install that search and Anthony were able to start using, for example, the tiles of web part, which is visible in the picture over there now cool one thing. What I wanted to also talk about here- and this is an interesting topic. Luckily, there's 138 participants on the call, so we can assume that there's some people who are using our seasoned NuGet packages here now the the seasoned client-side object model.

A

Nuget packages for sharepoint, 2013 and Chevonne 2016 haven't been actually updated for a long long time and which is also and has been giving us the baseline for the capabilities. What the BMV provisioning engine as an example is capable of using so as an example shipment within the SharePoint 2013, the baseline has been April. 2015, see you, so if you have to use that CU level or a newer one and the BMP provisioning engine should be working without any issues or obviously, there's always bugs.

A

But it's designed to work with the death or a newer version now for SharePoint 2016, the baseline is actually our TM version of SharePoint 2016. So right now we we started with this thinking. First on the hey.

A

Well, we should probably bump up to versions, because there are certainly properties and capabilities on the newer versions of season and we were thinking on potentially doing a new baseline for both SharePoint 2013 and SharePoint, when assisting on the September 2017 see you and what this means is that I'm highly curious on on the fact that is this new version for the community. If that is the minimum requirement to be able to use BMP a season or BMP provisioning engine, because that will be then the baseline and highly curious.

A

If, if somebody has any any input on that one or then nobody monstax should I think about this thing's on 2019 as 2019 season 2019 comes to preview on summer. We do not have an exact date yet obvious. We do have a target date available internally, because we do not have an exact date which we can share, but it is coming to preview relatively soon and there will be over.

A

This is some new cat version on the SharePoint 2019 we're looking working all so with Visual Studio updates, with visual studio team on making sure that there's a support for that, at least in our rtm timeframe of the shipment 2019.

A

A lot of the people are working on to do yeah, so, basically on Philips command. This would actually mean that PMP provisioning would require that the baseline will be September, 2017 CEO, because then, if you use an older version, then we might hit a property which is not there and enabled on the server side. And this is really the challenge. We're trying to now figure out what would be the right baselines and which we are asking people to upgrade their on-premises deployment and as a minimum requirement to be able to use these things.

A

September 2017 and there is there's a service back one for Chevron 2013, but that's already collect five years old or four years old.

A

So that's not a right baseline either, but we want to pump up the version we just needed to somehow come up with a a baseline, so September 2017 see you for Chevron 29th 2013, he's selected right now, as they tend to the one, because that would be then online which sharepoint 2016 feature back to, because obviously, if you are in chevron 2016, you should absolutely use feedback to as a minimum baseline for your deployment. And there is someone additional notice on the slide which I added there.

A

As they final thing, I know that I might be confusing some people and some people might not be able to follow up on what am I even talking, but in the in the May 20 18 see you. We are finally fixing a zone ID, which is a property which was missing from the web part definition in Chevron 2016, even though that property does exist in SharePoint 2013, which is kind of insane, but that's on us and us in as Indian SharePoint engineering. We can't do a baseline yet to the mate.

A

When is 18, see you so we need to do a baseline. We were thinking of doing base lining on the feeds back to there at least there's nobody in there I on Windows, saying no. You can't do that, so we might be doing that right now and then, if there's a massive backlash, people having issues, then we might fall back slightly under versions. This would be something, but we want to do so.

A

You both get additional capabilities available in the engine and in the baseline, ok, cool nobody's yelling, like enormous leap, so that's fine, oh yeah, excellent I will move forward with that high level plan. What could go? Paso plays wrong. Indeed,.

A

It's one thing also just a reminder: before we go to the demos, so we will renew our meeting in white sand next week. You will see communications and social media around us and also the SB AKMs SP PNP links will be renewed at that time. Today is actually the last recurrent a meeting for this particular pipe weekly, a special interest group meeting, so that the invite will have to be renewed and that's why we need to actually do this.

A

We will do some structural changes in the invites as well and so that we are able to maintain and update the links and invites and everything else more efficiently in the future. If we would, for example, flip to let's say themes, podcasting capability or something else in the future which might or might not be there was it good.

A

The renewed in whites will be available within a within um next week, so it's it is not yet available because I haven't created the invites. So it's a timing issue.

A

So that's on me, because I haven't actually done that yet now, moving on on things, quick road, mint update, I didn't want to spend too much time on this one, because we definitely want to go the demos, the the next, let's say, a beaker kind of a functionality release we'll pay ship on framework 1.6, which is which has an ETA an estimated time of arrival, end of July. It might be slightly delayed or it might be in that one. But there is some interesting capabilities inside of that.

A

One, like the globally deployed sharepoint framework extensions, which will be available in there and a few additional things which will be included in that release. 1.7 of the sharepoint framework is now planned to go live than in ignite 2018 from a timing perspective, and we have not yet looked down what will be in that version, but you can kind of an assumed what will be there based on? What's not thickening shipping on 21.6, but what of course, stuff coming and obviously will keep on releasing a new version of the season.

A

New versions of the other AP is and documentation among among the way and also newer versions of power. Apps and flow are moving along on their journey as well. Now, let's actually move into the demo topics and demo section, and so the first one and first person on the on the line is a Cal who is already a presenter, hello, hello, everyone yep.

C

A

Good, okay, let me show you.

D

C

So, let's uh I thought I will give one public service announcement or research.

A

C

Update but I need to share my screen. Just show that I show something so.

A

Let's, let's, let's do that then. First sorry, a Cal. Let's check.

C

On channel we missed.

A

We missed the synchronization with checks on this. One I should have probably have a slight waiting for checks to yes, I'd, like customer.

C

Un's and and hackathon days and back in office, so it's been very excuses.

C

A

Why and it's it is there. Yes, we can see your screen so.

C

One of the feedback: we always get sharing flows to SharePoint users, especially if you have a flow attached to a list. You know how do my list users get access to the flow, whether it's owning the flows are running the flows. If you have flows created for the selected item, so one update that we worked with flow team, this is kind of the first part of the update is to make it easier for customers to share flows with your SharePoint users.

C

So if you have a flow that is using a SharePoint trigger like this interview, feedback updated and you click on the owners and users group, you will actually now see a new tab called SharePoint. So previously you can come here and you would have to enter everybody's name and that will basically give access to those people. But now you can go to the SharePoint tab and that will filter the sites that you're, using especially the trigger and other actions.

C

The SharePoint actions that the flow uses in this case is using the site, Human Resources and the list that I use from this site in this flow. So, for example, interview feedback and interview prep, so I know that, based on the flow creator, because I created this flow, that all the people in the interview, feedback should have access to the owners. So that means that the owners of the list, not the members, but the owners of the list who can manage lists- will automatically get owner success and they will have access to this flow.

C

So if somebody else leaves in the owners group, you know and be in the list of manage owners group, you can still get access to others coming in and basically doing obtaining the list. Similarly, there is also, if I can show a.

C

Randomly uses so randomly users are the folks that don't own the flows, but they can run the flows. So here we have owners. Similarly, you can go to the run, only users and there we also have the same thing. So you can say from the customer feedback side the site biggest library, everyone within that access, whoever has access to Cypress library can now run the flow. So if we select the item, they would be able to see this flow and run this flow.

C

So there's something the first piece, the second piece we're going to be integrating this right into the SharePoint UX. When you create the flow we automatically will give permissions to manage these two, your expected users. So that's something we released two weeks ago: I, don't know how many people have seen this yet, but so let's try it out, and let me know if you have any feedback chuck's.

A

Actually, on that one time can ask a question, because nobody else is asking that and I am. How would I? Is there an API to actually make this happen automatically if I want to? Because there's so many, let's say partners who manage hundreds of tenants, so they need to be able to push their flows available and then do this kind of stuff using an idea. Yes, so right.

C

Now the API landscape is very, very negligible. We don't have the right api's from flow to do these things. Hopefully, when we do factoring the way how we you can come through sharepoint, maybe we can have something. So basically, this comes down to how we want to do from SharePoint site. We haven't yet thoughts.

C

We have ideas, maybe there's a sitting that says whenever somebody creates a flow automatically share these things to users and stuff like that, and if there is something then we can do some API on SharePoint side that goes and for that list. If there are flows it may find and do the smart things it needs to do from the.

A

Flows so checks and that's not actually really the scenario scenario with me. That's we would need to have an API to be able to push the flow in and then associate the flow to their specific list or library, because if you have a, if you are managing hundreds of tenants, you.

C

A

Want to go one by one and click. That's.

C

A different scenario: this is a this- is about permissions who has access to the flow, which means the flow is already set up with a SharePoint trigger when I say SharePoint triggered. You will have a trigger that says for a selected item or for this particular library whenever new items are created, updated. The scenario that you're talking about is basically how do I deploy a flow, so that I can then ask.

C

For example, I can export this flow and apply this flow and then change all the connections to whatever the new SharePoint list in the destination, where I'm inputting this flow, so that one today it's a tedious process. I will demo that in the next call, that will basically take more time, but we are looking into those scenarios, and one thing you saw in the keynote is to be able to export import the these flows along with lists and libraries, and and at that time we may get much better functionality to do that.

C

Actually, right now, it's a bit tedious process, but I can show that in another call, yeah.

A

And the whole point is not like pinpointing that there's a camp, but we need to understand everybody in the community to understand what's possible and what's not and when it's potentially coming I think that's always fair point as well. Yeah.

C

A

A

Cool anything else from your side checks or some.

C

Job yeah I think that's.

A

Really cool stuff with.

C

A

D

Okay, great okay,.

D

Let me know if you see my screen well, my browser.

A

Not yet not yet not yet. Okay, let's see now it's loading.

A

And got it yep: okay,.

D

Great great well, first things, first, a in any case. If anyone wants to ask me some questions afterwards or want to know more more, a kind of more information of what I'm going to show you that's my Twitter handle, so you can ask me from from there or I'm actively in the powerups community. So you can ask questions there too. So I was going to show a PowerPoint presentation, but I thought the community site is better to to show you all the things that I've learned from working with power-ups in the sharpen least forms okay.

D

So one of the questions that I've been seen on and all the things I fir I have learned working with a with these kinds of power-ups is when to use them a you. You always get the the simple, for example, the simple list that you can have in a SharePoint list that you can see all the information from the the fields that you create and everything and all this stuff, and this list are very powerful because you you can have this kind of controls.

D

You can have combo box dropdowns a you, can put a numbers and attachments and whatever, but it depends on the work that you're doing because, for example, this is a simple list of the SharePoint, but in the power in the power list that you can see here is the same list that I'll show you before, but using power apps, and this type of a list I showed you this the same information.

D

You can see the same structure and the same controls that you could see on the normal list, but it depends on whatever you're doing if the works that you're doing is just a getting some information from, for example, expenses that you need to set for fields in the in your application. There's no really not used to use power-ups.

D

But if you need to join several list to display very large information for the user, or do you need to have a proper controls or go beyond what what's the normal is chirpin list gives you, for example, you want to use an auto seer scanner or bars a bar chart or whatever it you can go with power-ups, because it's very powerful, okay, another thing that I was going to show you is the the three kinds of power-ups in the SharePoint list. Power-Ups.

D

As you know, power-ups in the SharePoint list are, and a special kind of power-ups are not they not a useful power-ups that you've been working with, for example, I'm going to show you in this list that I have here.

D

If it goes there, the three main power-ups that you can see is the integrated one that they use, that you just show you just before the normal power up that you can build in in the power-ups studio, where you can have a connection with a with a sharpened list and deploy your your power, perhaps a to mobile devices or to or to just to shoot your to share that power up. Wind, your organization and and the other one is the full-screen version where you can see here. We have for this list.

D

This powerup integrated with the list that, when it change the data, when you select the items in the in your list, there's also you can see that here. This is the list that you can. This is the powerup that you built if you click on customize forms, but if you click on create app, you will get a I even list in your view, in your list. That shows you this it's kind of like a full-screen powerup or a normal power up.

D

But if he's showing, you is hiding the list and showing you only the power up in it depends on the case that you are working with a maybe you will want to have a powerup for your organization, because everyone has an iPad and is gathering all the information from from those devices. You can create this app from the list and and deploy it your to your power-ups, a to your power-ups organizations.

D

Okay, so a that way- and you don't have to let them go and to have your users go to the SharePoint, what to go to SharePoint to to access the power app. They can go through all the power-ups in application, for example, in the Google store on the EEOC store. Ok, ok, the big difference here, for example, you have the full screen power up that I just show you and the standalone power ups. That is the one that you create from power ups exactly and from Proverbs itself.

D

Okay, when you go to, there are two main difference between these two power. Ups, the.

D

Open the full screen power up as I call it a has the same interface as a normal power up that you create from power ups to do, but it has some difference in here. For example, if you go to app settings in your power up, you have all these in sizes.

D

For your for your power up, you can set the size of your power up to all this and even a custom size, but that's sorry, that's for the standalone, a power up, but bar for the full screen. You can only have in the screen size these two choices.

D

Okay, so if you want to work with a powerup that that has some accent extensibility in in regarding the size of you of your of your powerup, you should go for the standalone or just create an integrated, a powerup and then change the size accordingly. Okay, where else I was going to show you, for example, when you work with with power ups a once, you know which kind of power ups you want to build.

D

You can have, for example, a you need to know, and you need to take take into account some things before you work a one of the things, for example, that I've learned is that, for example, when you create a deck of the custom fields for your for your list, I'm going to show you an example of this that has these kinds of name, title text, spaced data validation with parentheses and even a Spanish song. Does that mean song that is cancion and all these fields that are very large?

D

It might seem, okay, when you work with this power with this a with this list with these names, but when you create the power up for this list, this is what you get when you go through the power ups. You can see here the title says title: the text data is being renamed to this: a special and encode, a field that, for so power-ups, can understand and can communicate with this list. This is not ideal. If you want to work with these kinds of fields, maybe you don't want to work with the shape on forms.

D

Maybe you need to work with a with the patch solutions and if you try to rename these kinds of fields, it's very difficult, especially this kind. These two, for example, that are almost the same name at the first at the beginning, but it's impossible to know which one is the one. Do you want the journey to work?

D

So a my recommendation when you work with with power ups, you can create the same fields but try to use a normal with without special characters, for example 6-day that without space validation without the parentheses and even the work can see on without the without the central. Ok, you can go to the list settings. You can even create a icon for your list, for example, a received type without the spaces it will create the field there's a particular property for each field. There is this called internal name.

D

This is a one that a powerups uses to communicate with a list and to put the information inside this field. So when you create a field for the first time or the column for the first time it receives this name in the internal field, then you can change the name of this field to wherever you want, but powers will a communicate with this field would is with the internal name, so it won't be an issue a afterwards.

D

You will know that received type it's received type without having to work with those special characters that powerups uses to to to work to overcome the issues with with these characters, for example, this is a good naming list. If I refresh the data source for this list, you will see that now, I can see the received type with the space. I can add it to my form, but it will regain the it will have the same name that I created at the first time.

D

So this is the kinds of things that you might want to take into account when you create this list, because, let's say, for example, you use this list and with a powerup to build to gather information force from several sources and then connect that power bi to model all this disinformation into graphics.

D

When you create a when you connecting power in power bi in this data source for the power bi solution in the power power bi online, you will see the this the wrong names, these names in power bi, so it's better to have proper naming for each field. So it's not a headache. After afterwards, when you're working power, bi, okay and after this I wanted to show you an another thing. That is a trick that I knew that I learned when creating a apps in power-ups.

D

When you have many fields, let's say, for example, I have this this field here, okay, let's say.

C

D

Have this field here, let's say: I- want to create a powerup from this list. This list, for example, has a 15 or or 18 fields that I created. Sorry, if my computer is kind of slow but as I'm presenting the it's not responding very well.

A

See if it will be.

D

Okay, now, okay, if I, create a powerup from this list power of itself, it will connect to this. The source M I will try to create a form with all the fields that my list has. Okay, a there are some times where that's okay, but if you have many fields, it will kind of be an issue when you try to build the URI for your app. In this case, a I have all these fields and I have to scroll down to see all the information, and it's not very suitable to to work with this.

D

So one of the things that I do: okay, it's changed to landscape mode. This will change all my controls and to resize them. You have to work a little to put this information pretty well, let's say, for example, I take this form and I change the size I go here and let's say well, it's nap to let's say six fields: six columns, sorry and okay, the title posts this size account.

D

The customer says that the department needs to be this big and the position is this big?

D

Okay, everything seems okay, but we are getting again with the issue with the with the scroll. Well say: we remove some of the fields here here here. Okay,.

D

Okay, everything is okay. I need to set this big, okay, I'm on the same issue again, so one of the things that I come up to solve this issue because I'm and I don't like the people to be scrolling. All the time is to create virtual taps how to how do I create them so I go here, I create one little line using a rectangle.

D

Okay, I will set this like this go over here sample. Okay, this is my form I'm going to say right here and let's say: let's difference the company field from my expense manager. Okay, so I will put a label here, see little figure. Okay, let's put some fields here for my tabs, that's going to be another.

C

D

Okay, this is going to have the expense.

D

This is going to have the company tail so far, so good.

D

B

D

Okay, I do have this virtual tabs, so I'm going to need a selector for this field. Brittle tabs, so I create a rectangle again and set to here. Okay now it looks like this is a tab for this.

D

Okay, one of the things that I always do is to group the several items together, for example, this is going to be my my menu, so I'm going to set it to my.

D

So four so far, so good, okay, I now can create a new screen where I'm going to copy this menu.

D

Move it accordingly. Okay, now we are on the company tab and it looks some sort of working okay, but what what do I do with all these fields that I do have in the form? Okay? So it's no issue I go here. I am locked these fields to make changes just simply clicking on here and I'm, going to delete them.

D

Everything in the in the data card delete them to be perfectly set height to zero, so I can not see it. Okay, so no more scrolling mode. Just a little bit.

D

So everything is okay, but what about these warnings so I can go to this screen. I can insert one label.

D

Let's insert one text.

D

That's with caffeine. You know you need to do better than this, because this is a demo, and this always chose looks bad. You need to do better than this. Okay, okay, we.

A

D

Information what I'm going to set in here for the data? Okay, so hey! This is going to be my. The name is going to be the company name.

D

This is going to be a dress.

D

And this is going to be a sari from a, and this is going to be temple.

D

So I can go here this one and set your current update field is not going to be the one that you had is going to be. The company.

D

You are going to use.

D

Address, oh now, whenever, if, if I use this form, a I can go here well, one step: I'm missing is one when I put here I'm going to navigate to the company screen. Oh sorry, I I didn't put a name so.

D

And on this screen, whenever I click, the expense I'm going to navigate.

D

D

So when you test this, you can go here. Well, it's not showing data because I'm not connected to the touch upon and at this moment and a because I need to put this.

D

Okay, so a if we use these kinds of of UI building, you can have many tabs many many screams for to display all the information for your user, for example, you need to have all this a let's say you are collecting information from a from an action that you accompanied it and you have. You can have a all the action of this process in one screen, the company that it belongs in to another screen there receives that you collected into doing that project in another screen, without a making all these changes into only one screen.

D

Okay. This is one of the some examples that you can have a when building a power: apps, okay, okay, so this thing that you you can well, we can go back to to SharePoint by using this. This way you can a extend a form into several screens and just use the same form that you have in your first screen when, when you save the the information is going to take all the information from the other screens from the other screens that you have in your application into the same connection, whether with a SharePoint integration.

D

Okay, one of the other things I wanted to show you well now, Akal.

A

I, do I need to apologize on this last stage because we're already ten minutes to the hour and we would have earning wait up on the no.

D

It's okay! It's okay, I, wasn't going to ask you if, over over my time, it's okay.

A

But this is actually really cool because you can actually see now that's associated and it's working like a tap and sure you can align those things in the way that it looks really really consistent to really go really.

D

Really fast with this, but yep.

A

Okay: okay, that's that's really cool demo and absolutely because this shows how you can extend and simplify the form and making it simple making it like a research style form a even you could easily do that as well. Really, cool, really cool stuff.

D

Well, thanks for this, I was going to show you but I'm going to save it for the next time how to work with several environments like when you do when you have a deployment environment and the production environment. Well, but that's for the next session, okay, yep.

A

Let's do that, let's do that. Thank you, a Calif at this one, because we absolutely want to get urban on the on the demo site as well. So Irving, can you flip still you.

B

Will have to promote me to presenter because I I reconnected.

A

Okay, let's, let's make that make you a presenter there we go and show your new status. Thank.

B

You right the starter kit we released a few weeks ago and today the blog post came out and people seem to like it a lot which this makes us very happy. What I will talk about is how we do the provisioning of the starter kit and the components that are into play when you decide to create your own portal. So one of the things we would like to stress is that you maybe want to test this on a development sentence first or accept this test, tenant or whatever tenant.

B

You have around and play around there, because we do create site collections with a predefined name and I'll talk you through I will not run the script. It will take seven minutes, it does a bit boring to look at, but I will talk you through what the script is doing and we started out of files that that make up the whole provisioning story here. So when you retrieve the the github repo, either by creating a clone on your local machine or just simply downloading the zip file from the repository, this is distracting.

B

You get and I open this in future studio code and all the magic of provisioning is happening in the provisioning folder and the main entry points to start your provisioning is the deploy scripts and that's what is on screen right now, and this is a relatively low fee, that long, but a relatively long PowerShell script, a lot of parameters, but the simplest way to actually the provision is starting to deploy the employ scripts.

B

Multipoint youto have to go to the correct follower and deploy you say ten and URL, and this is the routes URL of your tenant like this mob, slash sites, nothing like that, and then you can optionally provide the site prefix. If you do not provide the side prefix, all your sites will be prefixed by default with the demo underscore, and then let me talk you through what's happening actually in the script itself, so we first make sure that you have the latest version of PNP PowerShell installs.

B

Then we will ask you credentials, and these has to be tenant admin credentials because you create site collections for you. There are some checks for parameters. You can say you know what to skip the whole site creation thing. I know: I have my sites already, so you can do that, but some flags, if you want to, then we check if the solution is already prepackaged and built by you. We provide a pre built version to that.

B

You can upload to your tenant app catalog, but if you don't want to use that one, the amount of builds on the fly and you run the script it will check if it already has been built. If not, it will do the work for you, but this requires that you have the SPF X tool chain installed, so NPM yeoman generator gulp all that those things need to be installed on your environment because it will run npm, install and etc. So, if you don't want to do that, you can simply take the existing solution.

B

Packets and upload that one to your app catalog, then we connect to the site, that's to your tenant and we just among others and get a context and make sure that your credentials work. And then we provision the solution and we check if the app is already installed in your environment in your app catalog. If not, we will.

B

If so, we will remove it first to make sure that you get the latest and we will update the version that we just built for you and then we apply provisioning templates, and this is the solution: xml PP, provisioning, template and in that solution, template that we have here.

B

You see, among others, that we upload through the template, the packets, the starter kit packets. So this is being uploaded to your tenant, app catalog.

B

What we also do is make sure that your CDN settings are correct on your attendance, so the office 365 CDN when released, elect a couple of things in a configuration and if you are one of those people that start use that really early when it just came out you you, like this specific configuration, so we make sure that it is there by configuring that, through this solution, XML, then because of this packets being installed, there will be a couple of web api permissions and we all approved them here for you.

B

So, for instance, we need access to the graph and etc etc. So we did a couple of things. We need like being able to read all the sides, all your contacts, your groups etc, and we we pre-approved them effectively for you, so you don't have to navigate to your tenants or use the powershell commandlets to approve those sort of provisioning. Ancient takes care of that.

B

Then we pre populate a term group with the term set and a bunch of terms in there that are being used by the one of the extensions being the footer and that's effective of this. This solution, XML. Does it provisions the solution, create some term sets etc and approves the web api.

B

So if we go back to the script, then we make sure that the quick launch is not shown on the home page, because we don't need that in our root sight, the portal site, if people take hold it like that, and then we apply a theme, and this is not an PNP powershell commandlets. This is a script set theme if not set, and that comes from this functions ps1 and in here.

B

If we scroll a bit down here is the set theme, if not set, and we make sure that the theme is being said now, there's a bit of a tricky thing.

B

We do door tricky, but there's a thing we do here, there's currently no way of figuring out which theme has been applied other than looking into the property back and find a key called theme primary, and if that value is matching this, if we look a bit down this value of the theme primary few theme, then we just simply assume that you have to seem so we have a similar theme at the same primary color.

B

You might have a mismatch there that we will not apply the theme, but this is the theme. So if I saw on the chat earlier that someone would like to have pink theme, this is your entry point make changes here so back to the deploy. Then we make sure that the site is not already a hub site. If it is not, we will register it as a hub site and the video is here.

B

Then we will set a storage entity value which effectively is a property back value in the site, collection, FCAT, local, sorry, no, translation, tenant level, app catalog. That contains a key for an API that we use the key. You will have to retrieve yourself or register for it yourself, that is to retrieve stock values, and then we apply the actual portal template. So the solution was to upload the solution and do some things on tenant level, and then we have the portal XML file that is being applied in line more than 23 over here.

B

That will then apply the design to the site. You see that we sent in a couple of parameters here, so the weather city defaults to I think Seattle. The portal title defaults to like controllers or portal, the stock symbol defaults to in this case, Microsoft. It's all value, she can specify the script and we pick up the ID of the hub site, etc.

B

So a couple of things we set sent into this portal XML file, and if we have a look here, it's a couple of things we do so you see that here is that those parameters they have default values, but you can overwrite them by means of specifying the parameters attributes of parameter on the apply PMP provisioning templates command lit. We we create a couple of side, designs and associate side scripts with those and what we do is decide scripts.

B

When you create a site collection based on the side script, they will associate the site that you just created that site design with the hub site that we are creating here and I'm running out of time. So I hope. Actually it's five o'clock, so I hope I can cross the five o'clock marker and people will hang around a little bit longer it it's not a five minutes. I'm done with my talk.

B

So what we do here is the site designs. They are located also in the solution here and they're, relatively straightforward site designs, but we do a little trick that only the pnp provisioning and you can do is that we can use tokens side, designs themselves and side scripts do not support tokens, but the pimply provisioning engine does and you can actually use PP provisioning engine tokens in your side scripts. They only apply at eppley Kayson time.

B

When you have the engine create a side script, then the Tobit will be replaced with the actual value, so they did not work at runtime. When you create a site collection based on that side, designer side script, then, if we go back to the script, sorry to the portal XML, then here you will see, but that we create the navigational structure and so the hop site navigation is nothing other than the top navigation of a size collection.

B

So we add the hops right navigation here, but the difference is that the up side, navigation, populates down to every slide that has been associated with the hop site. Then we create about a couple of side fields, not that interesting, and then we create the client side pages, and here we create a home page.

B

Now, when you look at design that the VESA shows- and maybe you have looked already at the the actual starter kit but I have it open here see this is a tiles web part and the data of this web part is actually stored in the web. Part properties, it's a it's a JSON string and we pre populate links for you here. So if you want to get an example on how to like populate a web part to a page through the PP provisioning engine with properties already set, this is this is your example.

B

This is the way to go to have a look at so we create a couple of pages. We create a couple of sections in their columns, we set web parts, etc. We upload documents all kinds of things we do here. We create a couple of news articles, here's your article pages and we promote them as a news article, and that makes them automatically show up here these ones here and if we go all the way down.

B

Just like a couple of lists and we create a calendar list, we could calendar items in that list alerts list.

B

We associate here some custom actions with our effectively application, customizers like the footers and redirect and a site classification customizer that we have available for you and then we upload all the files to the side assets folder, that's effectively what this template does. Then, if we go back to the script it.

B

Was a little issue?

B

Actually we can remove this now because in the last release, latest release has fixed is already, but there was little issue with the PP provisioning engine and the association of site designs to the correct web template, but it has me fixed now, so we could actually remove this already these lines here, but it so it doesn't hurt there to have them around, and then we update the navigation we set because we just created two side collections or we actually will create site collections that are part of the hub site structure and we apply a template being the collaboration XML, the color of XML to those specific template sites, but these sites they show up here in the departments, the human resources and marketing sites.

B

These are the two sites and in that script, that I just showed you. We actually add those sites here to the hub site navigation, and we because we don't know what URL is to the site. That's that's at creation time! So that's why we did it in the script. The structure of the site collections that we create is being read the moment. The scripts are, there runs from this hierarchy, JSON file, so here you see the URL for portal.

B

The prefix that you specified will be then set in front of this URL, so it will become teleportal in this case call or demo underscore portal demo on the score, HR and demo underscore marketing. This is a communication site. These will always be created as team sites, so the the whole provision story will grow. We will do more things in the future.

B

You see there is, for instance, already and as your PS ramen as your folder, so we're doing things like being automatically provisioning in the future, most likely things like setting up your at a function, app and creating functions in there, etc, etc, etc.

B

So, there's more, there will be more things happening on this end, but if you want to see a good example, I would say about how to do it so much advanced provisioning and creating pages on the fly and setting content in those pages and doing things with site designs and making them a bit more interactive than they can be out of the box. This is to wait. The the repo to look at.

A

Absolutely this is a really great solution and reference sample for showing how to make those things happen, because I think many of the partners anyway need to automate, for example, if they have multiple tenants to provision stuff on tenants and and provision other stuff there, as well, so really really create solution from that perspective as well, and that's absolutely one of the key points of the shipment starter kit as well.

A

It is a collection of different scenarios, different demos, different technologies, different things, but people can then learn from, but it you can also use it as a demo environment for yourself cool one thing like like urbe mentioned, we will add absolutely additional content in future there additional new years additional pages will do cross linking of things here, kind of a feedback and and all of these typical links and altars and content would be available there. At some point, we're also looking like mentioned in in two unknowns blog post today as well.

A

We're looking into eventually have a self-service website, so you as a tenant administrator, can go to a site where something like hey: share: cool sharepoint, demo, dubs office.com, and then you sign in using a tenant, administrator administrative permissions. And then you fill up what I do or you're able to change the default images and themes. And then you say provision and after a while, you work that can think in an email or a notification that your demo has been a provision.

A

So you can actually use this as your demo environment for anything pretty much in the future, but one step at a time. One step after the.

B

Most short short question in the chat: if we replace the ALM elements, no, we didn't see is still there, so it's called application lifecycle management and it's located under the provisioning template. It's there yeah. It's.

A

There, even though right now in our rhythm for reason, format, we are actually saying that you should manually update this Bay pkg file and that's mainly because we had some issues, technical issues on that most likely. It would actually work properly already right now, but so it should be working fine. But if you follow up on the readme file, if you're using an English tenant and a would start said to be a target release tenant, this is definitely working. We've been testing this to clean tenants and quite a few times.

A

If you need to have a new tenant by yourself, you can always sign up for office 365, developer program and you work at a free tenant for developer usage, and that is a great option for you as well, and let me add that link to door and window and then we need to actually close, but let me get that one more linking and that's seven minutes of the time, but this is super important. So if you get that link into our window, you can go in sign in for the office traces to our developer program.

A

We will actually renew your free subscription as long as you use that tenant for developer usage, so there are analytics behind of the usage of that tenant, which we will be getting for free if you're, using that for developer use, it will automatically renew as well now right now, I think it's time to close we're eight minutes on the a slightly on top of the top of the hour. No worries about the timings too much.

A

The video is getting recorded, we'll get this video under YouTube for those who were forced to drop earlier on this call and we'll align with checks on the future to make sure that he has this kind of a flow and power app section on the slides as well. So we'll always have some news on that side of the story in this bi-weekly call as well, but thank you everybody for joining. Thank you a call for your great demo to the urban for your great demo.

A

You will be absolutely intense and please keep the feedback coming using our t-top and social media channels. Thank you. Thank you. Bye, bye, bye, bye,.