►
Description
Recording of the SIG from November 1st. Latest SharePoint Development news from engineering and cool community demos.
- Demo on domain single part web parts
- Demo on domain isolated web parts
- Demo on http://www.sitedesigner.io for creating custom Site Scripts for SharePoint Online
Detailed agenda and covered topics are available from SharePoint Dev blog at http://aka.ms/spdev-blog.
Download recurrent invite from http://aka.ms/spdev-sig-call. More details on the SharePoint Dev community from http://aka.ms/sppnp.
A
B
Welcome
everybody
to
sharpen
Patterson
practices,
general
SharePoint
development,
special
interest
trip,
so
that's
quite
a
mouthful,
but
what
it
actually
means
is
that
we
have
a
bi-weekly
this
meeting,
where
we
talk
about
everything
else.
Typically,
then
everything
else
then
SharePoint
framework
and
client-side
development.
So
in
these
Tinashe
upon
development,
special
interest
groups,
we
actually
talk
about
custom
theme,
site
design,
side,
scripts
solution,
designs,
flow
power,
apps
and
all
of
this
customization
and
extensibility
models.
What
we
have
on
SharePoint
Online
or
in
on-premises.
B
So
we
will
have
a
special
SharePoint
2019
meeting
coming
up
at
some
point
as
well,
so
making
sure
that
those
are
I'm
making
sure
that
we
cover
to
2019
and
some
of
those
close
as
well.
So
and
then
we
have
a
separate
special
interest
group
call,
which
is
around
SharePoint
framework
and
client-side
development,
where
we
go
through
the
p.m.
PJs
Kwan's,
our
development,
tooling
or
365
CLS,
and
all
of
that,
so
all
of
these
calls
are
happening
on
Thursdays,
7:00
a.m.
Pacific
time.
B
B
Let
me
actually
quickly
explain
what
this
is
all
about.
If
you
haven't
been
in
this
course
before
so
this
is
like
say:
this
is
the
general
deficit
collar.
We
talked
about
provisioning
automation,
API
is
see
some
core,
as
an
example
will
be
a
future
topic
as
well,
because
we're
still
looking
into
making
that
happen.
B
Our
apps
flow
all
of
these
things,
which
is
none,
SharePoint,
framework
development
topics,
and
if
you
are
interested
and
there's
always
an
opportunity
for
community
demos-
and
we
are
actively
looking
always
community
members
to
do
the
demos,
so
we
can
promote
you
and
the
cool
stuff
what
the
community
is
doing.
So
it's
not
just
about
what
we
do
in
engineering
or
what
we
do
in
the
in
the
PMP
crew.
It's
really
around
giving
all
of
the
other
people
and
well
MVPs
and
everybody
else,
an
opportunity
to
present
what
cool
stuff
they're
actually
creating
as
well.
B
Now,
there's
multiple
ways
of
participating
in
the
ship
on
deaf
community
and
kind
of
mentioned
that
one
already
is
a
demo
solution
or
a
technical
pattern.
I
know
that
I
have
few
messages
in
my
linkit
as
an
example
waiting.
So
sorry,
David
for
that
one
I
haven't
replied
on
that
and
a
few
others
where
people
are
volunteering
to
do
a
demo.
I'll
follow
up
on
those.
B
My
incoming
messages
are
slightly
messed
up
because
I'm
getting
way
too
many
some
having
hard
time
or
following
up
on
things,
but
if
you
are
interested
on
doing
a
live
demo,
showing
a
technical
pattern
or
a
solution
or
a
sample
or
whatever
or
let's
say
a
technology
demo
from
flow
and
power
apps.
Those
are
more
than
welcome
on
this
course
as
well,
so
reach
out
to
me
Patrick
or
anybody
else
from
the
core
team
and
we'll
catch
you
a
cute
scheduled
on
the
demo.
B
You
can
also
contribute
in
a
key
tab,
so
we
have
more
than
400
samples
in
the
SharePoint
dev
SharePoint,
github
repos,
and
we're
looking
into
by
the
way
on
this
particular
topic.
There
will
be
automatic,
catalog
system
relatively
soon
for
all
of
the
samples
in
a
keytar
and
related
on
the
sample
section
on
a
github.
Recently,
we've
been
getting
a
lot
of
feedback
on
the
fact
that
not
all
of
the
SB
FX
samples
are
up
to
date
and
we
aren't
actually
planning
to
have
a
small.
B
So
that's
gonna
help
on
clarifying
what
are
the
samples
which
are
always
up
to
date
and
they
should
work
and
what
are
the
samples
which
might
be
out
of
date
in
the
past
now
the
last
thing
provide
feedback,
so
please
provide
feedback
using
racialist
using
the
social
media
channels
or
whatever
the
way
you
want
to
reach
out
and
tell
Microsoft.
If
something
isn't
working
from
from
your
perspective,
please
tell
us
so
we're
able
to
fix
that.
That's
a
super
important
thing
now.
B
B
It's
also
a
one
way
of
asking
questions
and
providing
feedback
when
personally,
when
I'm
talking
I'm
having
a
hard
time
of
reading
what's
on
the
iron
window,
because
I
can't
multitask
and
so
some
people
can
I
cannot
now
before
today's
agenda,
we're
going
to
do
some
general
announcements
and
updates
on
the
sharepoint
development.
I'm
gonna
actually
explain
two
new
upcoming
capabilities,
which
formation
also
in
the
roadmap
and
then
I'm
gonna,
do
a
live.
B
Demos
of
DOS
I
didn't
actually
update
the
demo
section
here,
but
I'm
gonna
do
a
demo
around
a
single
part
at
pages,
so
what
does
it
actually
mean
and
how
actually
behaves
and
I'm
gonna
explain
what
is
the
domain
isolate
at
the
web
part
and
because
that's
relates
on
single
app
pages
as
well.
It
is
chip
on
framework
topic,
but
it
actually
shows
you
the
future
direction,
how
we
can
do
isolation
of
a
customization
in
SharePoint
Online,
which
comes
to
preview
as
part
of
1.7
release
and
single
part.
B
At
pages
comes
to
preview
in
SharePoint
framework,
1.7
release
happening
relatively
soon.
I
almost
actually
said
it
out
loud.
Luckily,
I
didn't,
but
relatively
soon
that
the
single
page
application
pages
is
not
technically
about
SharePoint
framework
that
you
can
actually
take
advantage
of
them
in
a
different
topic
as
well.
So
I'm
going
to
talk
about
that
one
go
into
demo
and
then
hopefully
we
will
have
Michael
in
the
call
I
haven't
been
able
to
actually
follow
up
on
the
on.
The
discussion
is
Michael
in
a
call.
It's
Miko
in
a
comic.
B
It's
in
a
call
call
I'm
gonna,
promote
me
as
a
presenter
based
on
the
name.
So
hopefully
nobody
else
actually
try
to
act
like
a
Miko
and
Miko's
gonna.
Do
the
second
demo
today
around
the
site,
designs
inside
script,
so
I'm
gonna
be
talking
while
and
then
we'll
keep
this
staged
Miko
around,
showing
a
really
cool
site
design
at
all
which
he
has
built
together
his
with
his
company
now
cool,
let's
actually
get
moving
on
the
slide,
so
a
few
classical
slides
and
documentation
and
guidance,
a
chemist's
SP,
dev
Docs.
B
Remember
this
URL
we
actually
are
quite
a
picture.
We
had
a
quite
a
big
jump
in
october
related
on
the
view
here,
so
we're
now
up
to
four
hundred
and
sixty
thousand
views
in
October,
not
on
September
anyway,
badly
updated
slide.
Let
me
fix
that
and
later
so
now,
we're
heading
closer
and
closer
to
1
million
view
marker
in
the
documentation,
which
is
really
good,
because
it
shows
that
the
documentation
is
valuable.
B
If
people
come
to
know
if
something
is
missing
on
the
documentation,
please
let
us
know
if
there,
if
you
have
comments
on
the
documentation,
please
add
the
comments
on
the
documents
and
we
can
have
this
interactive
discussion
on
making
sure
that
we
are
giving
you
donated
guidance.
What
you
need
for
SharePoint
development
now.
The
second
thing
really
important
is
the
issue
list.
We
are
struggling
on
keeping
up
on
this
one,
but
we
are
trying
to
all
the
time
of
catching
up
on
with
it.
B
We
did
so
if
there
are
any
critical
issues
which
are
fine
or
an
issue
which
run
into
an
API
or
an
developer
topic.
Please
report
that
in
a
chemist's
SPD
of
issues,
this
is
the
way
for
you
to
report
developer
and
extensibility
related
issues
on
SharePoint.
If
your
issue
is
related
on
out-of-the-box
capability,
we
can't
deal
with
that
one
using
the
sticky
list.
B
So
please
report
that
using
the
SharePoint
Online
standard
SharePoint
online
support
channels,
but
if
it's
a
developer
related
issue,
please
do
open
up
an
issue
here
and
then,
if
it
really
feels
like
a
critical
thing
like
what
me
feels
like
SharePoint
Online
is
down
or
API,
isn't
working
at
all
editing
here,
ping
me
and
other
people
in
social
media
and
reference
that
issue,
which
has
the
additional
data,
so
we
can
actually
jump
on
fixing
those
things
as
fast
as
possible.
Now,
quick
update
on
the
roadmap,
I
haven't
actually
done
any
updates
on
this
slide.
B
Yet
a
small
update
at
which
I'm
gonna
show
in
a
second
but
1.7
SharePoint
framework
1.7,
is
really
the
thing
what
we
are
now
concentrating
on
the
SharePoint
engineering
site.
So
it's
a
big
thing
for
us
to
get
it
out,
because
that
then
aligns
to
SharePoint
development
together
with
Microsoft
teams
development,
and
it
also
has
a
really
awesome
set
of
additional
capabilities
for
SharePoint
framework
development.
So
it
will
include
domain
isolator,
quick
parts.
I'm
gonna
do
a
demo
on
that
one
today
or
quickly
explain
what
it
actually
means
it
has.
B
The
dynamic
data
GA
certain
or
availability
of
dynamic
data,
so
connections
between
the
components
list,
subscription,
they're
able
to
say
I,
want
to
have
events
when
an
item
to
the
list.
This
is
getting
at
it,
so
your
big
part
will
get
notified
when
an
item
is
changed
on
a
list
or
functionality
is
well
list.
Items
are
changed
or
added
or
deleted
from
a
list,
so
you're
able
to
subscribe
to
those
events,
SPF
X
components
and
teams,
a
huge
thing
which
we
originally
demonstrated
first
time
in
SBC
on
May
this
year.
B
Now
it's
getting
into
preview,
so
you're
able
to
start
using
that
one
and
testing
that
one
supporting
provide
a
hosted
solution.
Big
thing,
I'm
going
to
actually
do
a
live
demo
on
this
one
today
as
well,
so
taking
deems
applications
and
hosting
them
in
SharePoint,
so
magically
SharePoint
will
just
start
supporting
Microsoft
teams
application
as
such
as
an
iframe
in
the
pages,
and
they
will
be
completely
obviously
responsive
as
well,
which
is
a
cool
thing
and
then
the
web
pages
we're
going
to
have
a
role
I've
done
on
that
one
as
well.
B
Now,
there's
additional
set
of
improvements
coming
theming
inside
design,
side
scripts,
additional
placeholders
all
done
we're
working
on
them.
There
will
be
then
announcements
coming
up
on
those
whenever
the
they
are
coming
out
as
well
and
SharePoint
2019
g8
week
ago,
Monday,
if
I
remember
correctly,
I
think
it
was
week
ago,
Monday
right
somebody
can
confirm
this
in
I
window,
so
the
SharePoint
2019
is
now
generally
available
and
it
supports
technically
SharePoint
framework
1.4
except
the
except
the
craft
api's,
because
the
craft
is
not
Indo
on
premises.
B
So
we
were
able
to
use,
create
a
modern
experience.
There's
modern
web
parts
and
extensions
in
SharePoint
2019
a
big
thing.
Obviously,
now,
let's
see
if
I
can
actually
get
moving
here
we
go
so
one
of
the
things.
What
I
wanted
to
quickly
show
today
before
the
Miko's
demo,
and
this
is
the
demo
which
I'm
gonna
about
I'm
gonna,
explain
this
in
a
demo
as
well.
B
It
is
automatically
scaled
100%
and
wife
and
height
on
the
on
the
level
whatever
the
web
part
or
the
base
layout
actually
has
on
the
page.
The
navigation
is
visible
there
if
you,
if
you
used
this
in
the
collaborate,
sorry
group
associated
team
sites
or
a
modern
team
sites,
but
if
you
use
it
in
the
communication
side,
the
left
navigation
is
not
there.
So
if
you,
you
can
actually
choose
how
the
behavior,
how
it
look
like
been
based
on
what
kind
of
underlying
site
you
are
actually
using
and
it's
natively
responsive.
B
So
you
can
actually,
even
though
it
would
be
much
the
team's
application
which
you're
adding
there
or
a
web
part
there.
It
is
responsive,
so
we're
scaling
everything
automatically
based
on
a
deep
voice,
what
you're
using-
and
that
is
kind
of
mentioned
already.
So
this
is
supported
with
client-side
web
parts
or
within
Microsoft
themes,
apps.
So
just
as
well,
you
can
take
any
of
your
if
you
have
built
Microsoft
team's
application,
which
works
currently
as
a
team's
tab.
B
You
can
actually
release
those
as
a
SharePoint
application
in
the
SharePoint
app
catalog,
and
then
you
can
use
those.
Also
in
here
the
Maxis
team's
apps
are
basically
provided
hosted
solutions
because
they
are
URLs
which
are
surfacing
inside
of
an
iframe
in
the
context
of
SharePoint
and
we're
gonna
talk
about
that
one
when
I'm
doing
the
demo
and
but
technically
what
this
gives.
B
You
is
a
capability
of
exposing
a
whatever
HTML
structure,
whatever
layout
you
want
inside
of
that
whole
one,
the
whole
section
with
with
the
paid
sale
to
exposing
you
now,
there's
obvious
questions
like
can
I
get
rid
of
the
shipment
header
and
the
answer
right
now
and
use
this.
No
we're
not
planning
to
give
that
capability,
because
why
would
you
then
use
SharePoint
in
the
first
place,
if
you're
not
using
SharePoint?
B
So
we
want
to
have
that
SharePoint
hitter
there
so
that
people
know
that
they're
in
SharePoint
and
if
they
need
to
do
any
SharePoint
stuff
in
the
in
the
page
or
in
the
context
they
can
actually
still
do
that.
Can
I
get
rid
of
the
whole
header
section.
Then
the
question
is:
why
would
you
then
use
office
365
or
SharePoint
in
first
place?
You
can
absolutely
then
implement
your
custom
azure
ad
application
and
do
whatever
you
want
in
that
case.
B
So
there
are
certain
limitations
on
this,
and
whenever
this
comes
out
as
a
preview,
you
can
then
give
us
feedback
on
what
should
be
needed
and
what
is
supported
and
how
it
should
be
working
in
the
future.
This
works
by
default
when
we
go
live
in
preview,
it's
a
single
part
of
page,
so
it
supports
only
one
single
client-side
web
part
or
one
single
Microsoft
team
stamp.
If
you
have
to
add
parts
on
a
page,
you
can't
transform
that
to
be
a
single
page.
B
Add
page
single
product,
page
I'm,
going
to
show
that
one
in
practice
as
well
we're
looking
into
potentially
having
then
multi-part
pages
or
a
pages
at
some
point
and
we'll
see
how
far
we
need
to
go
on
this
context
now
cool
now,
the
next
and
the
second
thing.
What
I
wanted
to
quickly
touch
I'm,
not
going
to
do
a
huge
demo
on
this
one
but
I
quickly
through
some
slides
and
explanation
and
what
it
what
it
actually
is.
So
we
are
also
releasing
a
domain.
B
Isolated,
webparts
and
dominance
about
the
wave
parts
is
something
where,
if
you
have
any
security
concerns
related
on
the
fact
that
the
javascript
is
actually
running
in
the
context
of
the
page,
you
can
actually
de
man
or
you
can
control
in
the
package
solution.
Chasin
that
this
particular
web
part
should
be
actually
executed
in
a
domain
isolated
way.
B
What
that
web
part
is
actually
having
based
on
the
UI
is
in
the
SharePoint
or
you
can
see
same
missions
also
an
azure
ad
side.
So
basically
we
are
dynamically.
Creating
then
application
in
the
azure
ad,
which
is
matching
into
your
web
part,
and
then
you
are
able
to
control
in
detail
what
permissions
that
web
part
is
actually
having,
and
it
cannot
actually
access
any
other
other
permissions.
B
So
this
is
a
really
cool
functionality,
advanced
functionality,
which
goes
to
the
preview
as
part
of
the
1.7
release
and
now
I'm
saying
that
isn't
super
active
discussion
will
later
on
power,
apps
and
something
else,
but
sorry,
I
missed
the
original
story
on
that.
So
I
can't
participate
on
that,
but
let
me
actually
do
a
quick
demo
on
both
of
those
using
my
screen
and
then
I
will
actually
try
and
then
we'll
set
the
stage
for
mica
and
show
some
other
stuff.
B
B
Here
we
go
cool
so
so
you
should
be
seeing
now
a
shape
on
square
screen
on
a
SharePoint
site
contents
based
page
page.
If
I'm
not
mistaken,
somebody
can
confirm
somebody
can
confirm.
Please
confirm
it's
confirmed,
exact
excellent
Thank,
You
Hugo
so,
and
this
is
our
e
doc.
So
this
is
super
early
Edo
key
environment.
So
this
is,
how
would
I
put
it
its
day-to-day
builds
are
happening
in
here,
so
you
might
see
something
which
you're
not
intended
to
see,
but
luckily
we
are
not
Rico.
B
We
are
recording
this
okay
and
if
you
see
something
which
is
nothing
tended
to
say,
and
then
you
are
saying
something
which
is
not
intended
to
see
and
no
can
do,
but
let
me
actually
create
here:
AB
one
page
and
I
can
show
the
in
practice
what
it
means
that
we
have
a
single
part
at
page,
so
I'm
going
to
create
a
page
and
let's
call
this
page
as
a
something
simple
like
seek
a
special
interest
group
call,
so
I
can
easily
find
it
from
the
URL
and
then
I'm
gonna.
Add
here.
B
B
And
here
we
go
here's
my
web
part
and,
let's
actually
populous
debates
and
it
to
be
called
modern
page
which
is
natively,
responsive
and
all
of
that,
so
nothing
that
traumatic
about
this
one.
Now,
when
we
go
to
the
Deaf
preview,
which
will
happen
relatively
soon,
there
is
no
UI
to
flip
and
this
existing
page
as
a
single
part,
half
page.
But
what
actually
happens
is
that
I'm
gonna.
B
We
cannot
give
you
the
needed
guidance,
because
this
is
a
developer
experience
either
use
console
or
PNP
powershell
or
office
365
see
align
to
actually
make
that
transformation
happen.
So
we
can
actually
double
check
my
URL
that
it
is
in
the
Visayas
site,
and
what
we
want
to
do
is
that
it
is
a
sick,
SPX
I'm,
going
to
zoom
in
and
explain
what
are
we
doing
here?
So
this
is
a
deaf
preview
and
we
are
we.
B
It
is
not
intended
for
end-users
or
administrators
in
preview,
so
we
need
to
start
at
some
point
and
then
we'll
see
how
we
will
expose
these
options
in
the
future.
But
what
we
are
basically
doing
here
is
that
we
are
updating
depth
page,
which
we
just
created
and
to
use
a
single
a
web
part
at
page
page
layout.
So
there's
our
page,
there's
a
URL
there's
the
page,
what
we
were
actually
just
created
as
a
secret
aspx
and
we're
gonna
flip
the
page
layout
type
to
be
a
single
word
web
page.
B
B
We
are
actually
seeing
what
is
a
single
page,
a
single
part,
a
page
in
practice,
and
the
key
points
here
in
the
notes
is
that
there
is
no
edit
page
functionality
for
infusers.
You
can't
modify
what's
actually
on
the
page.
It
is
basically
locked
down
based
on
what
did
the
developer
wanted
that
page
to
be
now
in
this
case,
this
isn't
actually
super
interesting
functionality,
because
we
are
mad
at
a
one
web
part
there,
but
over
the
web
part
can
do
something
slightly
different.
B
It
can
render
something
more
nice
at
UIs
and
and
you
can
absolutely
also
get
rid
of
the
left
navigation.
Now
one
of
the
interesting
things
which
I
mentioned
in
the
oh
there's
a
good
question
from
Raymond.
If
you
want
to
change
the
Bates
layout
back,
you
can
actually
absolutely
do
that
as
well.
So
you
can
flip
the
base
layout
back
to
be
an
article,
and
then
you
can
modify
the
page,
and
then
you
can
flip
that
back
be
an
airport.
B
So,
but
key
point
here
to
understand
is
that
we
are
natively,
taking
advantage
of
the
of
the
webparts
sharepoint
framework,
equipments
and
SharePoint
framework
experience
and
we're
looking
down
the
page.
So
it
feels
like
a
single
page
application,
but
it
isn't
releasing
of
its
application.
It
is
say
a
page
layout
which
does
not
support
that
the
end
users
are
modifying
that,
so
you
can
lock
down
what
is
actually
on
the
page.
Now
I'm
gonna
do
a
few
demos
here
and
then
I
need
to
come
back
on
the
questions
which
I'm,
which
we're
seeing
here.
B
The
second
thing.
What
what
we
actually
mentioned
already
in
the
in
the
roadmap
is
that
we
will
support
natively
teams,
applications
and
themes,
files,
teams,
solutions
should
be
hosted
in
SharePoint
and
this
is
natively.
So
what
it
means
is
that
if
I
have
a
look
on
this
task
me
out
here,
so
let
me
actually
show
if
I
click
open
what
happens
today.
Oh
there
we
go
exile,
so
it
did
open
that
properly
and
let
me
get
rid
of
the
left
navigation,
so
that
sounds
too
confusing
there.
B
We
go
so
that
ASP
I'm,
sorry
done
zip
file,
which
is
track
and
drop
to
the
app
catalog
is
actually
a
standard,
Microsoft
team's
application.
So
now,
if
I
open
up
the
manifest
Jason,
which
was
unfortunately
associated
to
Visual
Studio
ideas-
and
let
me
actually
that's
open
it
up
on
a
different
screen
one
second-
we
can
actually
see
that
this
zip
file
is
actually
native
Microsoft
themes,
application,
there's
no
changes
whatsoever
on
the
zip
file.
It
is
just
a
Microsoft
Ames
application
with
somebody
created
for
Mac
systems.
B
B
This
is
almost
like
robot
a
hostile
aliens,
except
that
it
doesn't
have
their
classic
or
model,
but
you
can
easily
integrate
any
application,
and
then
you
could
do
something
like
dust.
Mew
is
doing.
It
is
taking
a
tremendous
refresher
ad
as
a
multi-tenant
application
for
you
to
sign
in
as
a
to
authorize
the
persons
now
what's
cool
around
this.
B
One
also
is
that
let's
actually
save
the
draft
and
do
a
populist
natively
or
these
applications,
they
work
like
a
web
part
and,
let's
see,
and
they
also
adjust
like
a
record,
so
they
scale
and
even
though
it
is
an
iframe,
it
is
a
provider
house
whole
application.
It
scales
automatically,
so
everything
happens
automatically
in
our
layout,
which
is
super
important
thing,
because
classic
provider
hosted
add-ins
didn't
actually
do
this,
so
we
don't
automatically
scale
everything
now
this
case
we
created
a
6-2.
B
So
let
me
actually
do
flip
this
Bates
to
be
a
single
based
application.
Oh,
we
can
actually
see
how
different
our
how
it
will
look
like.
So
let's
actually
call
that.
Then
that
was
the
URLs.
Yes
was
executing
done.
So
let
me
refresh
the
page
and
now
we're
in
a
full
page
mode,
a
single
page,
application
mode
or
single
based
up
a
single
part.
B
A
page
mode
using
a
in
quotes
provide
a
hosted
solution
rendered
in
the
page
and
that's
actually
pretty
cool,
because
now
you
can
basically
surface
whatever
layouts
and
experiences
from
that
section
and
an
area
within
within
in
the
context
of
share,
and
we
were
able
to
Opia
sleekit
information
around
where
your
getting
hosted.
You
have
some
level
of
an
access
on
SharePoint
context
and
the
users
as
well
with
this
really
really
really
super
powerful.
Now
you
can
actually
get
this
to
the
level
of
following
so
in
here.
B
B
One
second,
so
in
here,
so
this
is
say,
communication
site
communication
sites,
point
of
all
do
not
have
a
left
navigation.
It
did
have
an
hitter
on
navigation,
but
I
actually
manually
took
a
read
of
it.
So
if
I
do
that,
that's
now
the
Welcome
page.
If
I
go
in
here,
we
can
say
that
it's
a
normal
communication
site
that
didn't
actually
save
that.
So
let
me
go
back
in
here.
B
So
let's
and
as
a
home
page
was
I
too
fast
top
dollars.
That
should
be
fine
and
let's
get
in
here,
and
maybe
if
I
was
true
for
us
to,
let
me
actually
requested
that
he
kept
under
on
the
dog.
So
that
might
be
the
case
as
well:
okay,
fine
and
but
you
can
absolutely
set
the
single
part
update
as
the
welcome
page
of
the
site
as
well,
because
now
anytime,
I
land
on
the
site,
I'm,
actually
seeing
the
the
Welcome
page,
a
single
part
updates
here
and
rendered
by
default.
Now.
B
What
you
can
also
do
here
is
that
you're
able
to
what
I'll
did
as
an
additional
step
and
as
an
upcoming
capabilities
we
are
able
to
control
how's.
The
hitter
actually
getting
rendered
so
the
default
rendering
of
a
SharePoint
site
header
is
actually
quite
quite
big,
as
we
can
see
from
here,
and
it
has
the
search
over
there
and
all
of
that
stuff.
B
Now,
as
part
of
the
the
changes
which
we
actually
already
introduced
in
ignite,
we
will
expose
you
additional
set
of
options
so
you're
able
to,
in
the
theme
or
in
the
chance
to
look
you're
able
to
go
back
to
a
minimal
level
so
which
will
then
reduce
the
sharepoint
sectioned
relatively
small.
Here
now
there
will
be
additional
options
here
as
well
and
obviously
if
people
are
demanding
with
none
option,
that
might
be
the
case,
but
obviously
the
suit
bar
will
never
go
away
because
we
want
to
end.
B
We
don't
want
the
end
users
to
get
confused.
Now
the
search
text
box
will
be
relocated
in
upper
section,
that's
something
which
we
actually
announced
already
in
ignite,
so
it
might
be
that
that's
further
is
gonna
reduce
the
size
of
the
header,
but
it
gets
to
the
relatively
small
level
already
and
then
it's
still
exposing
additional
settings
and
options
to
the
site
level
as
well.
So,
but
whether
we
call
now
good
design,
if
even
have
a
business
requirement,
we're
saying
I
need
to
do
something
super
crazy
on
a
welcome
page
well.
B
This
is
how
you
do
that
now
you,
you
use
a
a
provider,
hosted
solution
in
this
case
the
team's
application
or
provide
a
hosted
solution
in
office
365.
You
expose
that
true,
a
SharePoint
communication
side
and
you
can
do
whatever
layout
you
want,
if
you
don't
want
to
take
advantage
of
any
of
the
normal
editing
experience
is
and
in
the
communication
sites
now
on
the
BMV
provisioning
supports
technically
this.
B
The
the
api
so
are
supporting
this
one
already
because,
like
you
saw
from
the
rest
api,
the
sorry
javascript
api
perspective,
we
were
able
to
modify
this
B&B
technically
does
support
this
already,
so
you
would
be
able
to
create
pages
and
modify
this
one
using
the
BMP
provisioning
templates.
We
will
make
it
more
easily
in
the
future,
as
well,
so
more
simplified
you're
able
to
just
select
the
bates
layout.
You
want
to
use
on
the
on
the
side
cool
if
you're,
using
a
SharePoint
framework
extensions,
those
will
be
rendered
and
displayed
as
well.
B
So
this
page
is
the
space
layers,
do
support
extensions,
so
headers
and
footers.
So
all
of
that
is
an
options
for
you
as
well,
so
super
cool,
more
options,
more
design
options.
What
you
can
take
advantage
may
be
tasks
meow.
Well.
The
reason
why
I
use
tasks
meow
as
an
example
is
that
it
completely
random
outside
of
SharePoint
context
as
an
experience,
so
you
can
see
how
it
will
look
like
as
whatever
you
want
to
do
now.
The
second
thing
what
I
wanted
to
quickly
show?
B
Yes,
the
puppy
was
program
because
there's
a
kind
of
pictures
of
cats.
We
have
two
cats
at
home
as
well.
So
that's
that's
not
the
case
action.
So
what
was
I
doing
now,
you
distracted
me
I
was
demonstrating
an
isolated,
isolated
web
part,
so
I'm
so
isolated.
Do
I
frame
that
I'm
not
trusted,
so
there's
an
isolated
way.
Part
1
I'm,
not
actually.
Okay,
that's
up
currently
working.
So
let
me
see
if
I
can
find
a
functional
one,
because
I
didn't
really
really
super.
Well
prep.
This
I
just
wanted
to
high-level
test
the
functionality.
B
Okay,
so
there's
a
small
issue,
apparently
on
rendering.
So
that's
fine,
we're
in
a
dog
like
said
this
all
right:
this
is
our
day-to-day
rendering
and
wanna.
But
now
what
what
happens
here
is
that
whenever
you
have
an
isolated
backward
so
technically,
let
me
show
you
that
from
here
a
start
point
of
1.7.
B
So
obviously
the
solution
name
is
the
one
thing
after
that,
there's
a
new
choice
of
options.
So
are
you
kind
of
choose
this
solution
to
be
part
of
sure,
supported
on
SharePoint
Online
with
the
latest
and
greatest
always,
or
is
it
targeted
to
support
Chapman
2016
forward
or
including
2019
and
SharePoint
Online
or
SharePoint
2019
and
forwards
include
including
a
sharepoint
online?
Now,
in
our
case,
if
we
lose
the
sharepoint
online,
that's
always
the
latest
and
greatest
it's
gonna
ask
around
the
folders,
but
then
it
gets
to
the
interesting
part.
B
Do
I
wanna?
Have
it
it's
a
non
scope
deployed
answer
is
yes
for
that
one,
but
then
it
asks
a
new
question.
Will
the
components
in
the
solution
require
permissions
to
access
web
api's
that
are
unique
and
not
shared
with
other
components
in
the
tenant?
I
wasn't
the
one
who
decided
this
text,
but
basically
what
it
means
is
oversimplified.
This
in
English
do
I
want
to
isolate
this
webpart
from
the
page.
B
That's
what
it
basically
means
so
and
if
I
answer
yes
on
this
one,
what
it
means
is
that
it
actually
controls
this
attribute
in
the
package.json
file.
So
it's
domain,
isolated,
equals
true
or
false.
20
fault
is
false.
If
it's
dominated
true,
it's
gonna
actually
then
execute
that
webpart
and
let
me
get
back
on
the
page.
Let's
get
the
page
in
edit
mode.
B
But
it's
gonna
render
the
web
part
in
a
different
eye
frame
dynamically,
and
it's
gonna
basically
render
that
in
a
different
in
different
context,
and
what
it
means
is
that
by
default
and
that's
because
it's
rendered
in
a
different
domain
completely
that
web
part
cannot
access
any
of
the
other
area
elements
in
the
end
page,
so
it
adds
additional
set
of
security.
This
is
the
same
thing.
B
What
we
had
in
the
Edinboro
SharePoint
framework
area
model,
where
the
SharePoint
aparts
were
rendered
through
an
iframe
with
a
app
domain
which
added
this
additional
lose
a
security
layer
where
they
cannot
access
the
information
on
a
site
and
that's
basically
what
the
attribute
is
then
doing
what
happens
at
the
same
time
when
we
said
that
to
be
true,
we
actually
dynamically
start
creating
permissions
and
which
you
can
actually
then
control
in
a
web
part
level,
which
is
technically
also
the
solution
level
so
like
in
this
case
the
updated.
A
I'm
management.
B
Ui
is
basically
explaining
that
it
and
there
is
a
set
of
Microsoft
graph.
Emissions
which
are
10
out,
might
approve,
but
then
there's
a
1
Mike's
of
craft
permission,
which
is
actually
context
of
trade,
which
is
supported
only
for
this
package.
So
we're
able
to
start
grinding
packages
and
sorry
permissions
for
individual
webparts
and
that's
a
really
interesting
thing.
So
what
happens
behind
of
the
scenes
is
that
this
gets
up
to
the
level
of
the
azure
ad.
B
So
you
can
actually
see
the
same
isolated
one
client-side
solution
with
part
which
we
deployed
on
the
SharePoint
site.
Behind
of
the
scenes,
what
we
did
do
when
you
approve
the
permission,
we
actually
automatically
created
a
sure
ad
application.
We
cram
that
the
permissions
we
did
all
of
the
needed
configurations
and
everything
else
so
that
you
don't
have
to
do
that
as
a
developer.
B
The
only
thing
was
a
developer
needed
to
do
is
basically
ant
that
ad
in
the
app
catalog
and
then
go
to
the
central
admin
level
and
click
approve
for
the
permission
and
whenever
you
granted
that
permission,
we
actually
automatically
created
to
Azure
ad
application
for
you.
So
you
don't
have
to
even
understand
what
happens
in
Azure
site
related
on
granting
of
these
permissions
and
that
should
definitely,
let's
say,
increase
the
productivity
of
the
developers
and
help
people
to
adapt
the
right
ways
of
doing
customizations
and
providing
also
security.
Isolation
between
the
functionalities.
B
B
Users
can
resist
your
application
sweetener.
Sure
no
can
can
a
regular
user
at
this
kind
of
web
part.
Yes,
they
can
regular
user
can
add
this
kind
of
a
web
part
in
the
page
in
in
the
and
I'm
technically,
any
regular
user
would
just
see
the
web
part
in
here
now.
If
the
web
part
is
then
trying
to
hit
a
ad
API,
for
example,
graph
API,
which
request
the
permission.
That's
when
the
the
permissions
in
Azure
ad
will
matter
technically
you
as
a
developer.
B
Again,
you
don't
need
to
have
any
additional
knowledge
or
understanding
what's
happening
behind
of
the
usher
side,
if
you
don't
want
to
as
a
administrator,
whenever
you
are
approving
things,
you
need
to
be
a
tenant
administrator
to
be
able
to
approve
the
permissions
for
the
individual
solutions,
and
after
that,
the
solution
is
executed
in
an
isolated
web
part.
I
will
isolate
an
iframe,
isolated
domain
for
additional
set
of
security,
and
it
will
have
its
unique
on
permissions,
which
are
automatically
managed
a
nutter
ad.
B
Can
a
domain
eyes
web
parts
then
not
share
dynamic
data
with
other
web
parts,
an
extension
right
now,
I
think
when
we
start
to
the
preview
relatively
soon
almost
set
it
online
again
when
a
but
relatively
soon
they
can
not,
but
we're
looking
into
different
options
on
potentially
even
supporting
dynamic
data
sharing.
But
technically
it's
an
iframe.
The
intention
is
that
it's
not
going
to
jump
outside
of
the
iframe.
B
Good
dose
and
Asha
administered
roadworks
or
approving
API
and
Dirk
is
answering
as
I
think
in
react,
but
not
approve.
Yes,
the
approving
means
the
non-lover
permission
just
it
requires
quite
high
hectic
permissions,
not
ready
to
make
this
operation
sudden.
But
anyway,
that's
a
quick
like
a
clarification.
How
to
domain
isolated
parts
will
work
horrible
demo
because
they
didn't
work
today
on
the
e
dog
again.
That's
because
this
is
our
day
to
day,
up-to-date
environment.
So
basically,
this
is
something
which
some
of
the
code
which
are
saying
in
here
was
checked
in
yesterday.
B
So
that's
a
super
olive
preview
for
some
of
the
stuff
for
you
to
read
this
call
as
well,
but
now
I
think
that's
enough
from
my
side
for
me
talking
a
lot
today.
Let's
actually
jump
to
Michael
and
I
can
then
follow
up
on
the
questions
and
I
window
related
on
this
stuff
and
potentially
we'll
have
some
Q&A
time
on
the
end
as
well
so
Miko,
hopefully
yes,
how
this
works.
B
B
A
B
While
you're
doing
that
Prime
Minister's
kind
of
question,
can
you
package
multiple
web
parts
with
the
same
isolated
emission
management
so
that
they
can
be
a
scoped
and
approved
together
and
not
ten
on?
Quite
answer
is
actually
yes,
they
would
be
then
multiple
web
parts
in
a
single
package
solution.
So
that
should
be
fine
now
and
also
just
to
note
that
one
as
well
the
domain
isolation,
all
numbers
for
web
parts.
So
if
you
choose
to
domain
isolation
when
you're
creating
the
solution,
you
can
no
longer
include
extensions
on
that
solution.
B
A
Yes,
so
my
name
is
Fiona
McCabe
also,
my
SharePoint
pattern
has
started
back
in
the
2007
with
SharePoint
I
also
have
a
longer
history,
with
dotnet
than
JavaScript
and
I
wrote
I
think
my
I
wrote
my
first
straight
back
in
the
nineties.
Already
so
old
guy
I've
done,
I
have
done
million
things
of
the
depth
right
now,
I'm
working
mostly
with
react
office,
365,
SharePoint
and
Azure.
A
B
I'm
gonna
take
quickly
on
that
one,
nothing
in
the
short
timeframe,
at
least,
because
we're
still
investing
more
on
the
on
the
core
capabilities.
On-Site
designs,
rather
than
the
tooling
behind
of
it,
and
clearly
this
tool
and
a
unique
has
done
a
great
tool
as
well
as
a
web
part.
This
will
help
for
people
to
adapt
the
functionality
as
well,
but
sorry
for
interrupting
so
feel
free,
no.
A
A
A
So
this
is
part
of
air,
as
you
see
build
them,
if
you're
not
sure
what
the
element
does
we
have
this
small
icon
here,
which
will
show
you
a
little
bit
information
from
from
each
of
these
fields.
What
needs
field
testing,
but
most
of
them,
o
Adly,
is
the
old.
If
all
the
elements
have
this
small
help,
I
think
you
can
use
I
think
we
should
support
the
whole
schema
at
the
moment,
but
of
course,
it's
possible
that
there
are
some
some
elements
that
just
have
slipped
and
we
need
to
add
them
later.
A
But
if
you
notice
something
that
is
not
here,
let
me
know
the
schema
is
long.
The
official
schema,
so
it
has
been
just
been
a
big
job
to
actually
put
everything
in
here,
but,
as
you
can
see
in
the
schema
actually,
as
I
can
tell
about
this,
for
example,
there
is
a
create
page
which
is
not
in
production
at
this
point,
so
that
would
be
great
if
it
actually
would
be.
There.
A
A
A
B
A
A
Hopefully
we
will
be
there
within
there
will
we
go
to
I'm
also
thinking
about
adding
this
to
the
Chrome
as
an
extension,
so
that
would
help
users
to
well
connect
to
the
tenant
level
directly.
So
so,
instead
of
just
seeing
examples
here,
you
would
actually
see
your
own
site,
scripts
and
and
so
forth,
but
yep
that's
coming
when
I
have
time
to
do
it
so
most
likely.
B
A
B
Were
speed,
questions
actually
on
the
underlying
window,
which
I
wanted
to
jump,
so
they
will
say
Steven
correctly
and
pointed
out
that
there
is
an
ongoing
discussion
and
Sean
squares
also
said
in
the
in
the
previous
demos,
in
the
six,
and
also
in
the
Ignite
that
we
are
working
on
a
native,
UI
and
native
extensibility
on
this
one
on
this
side,
scripts
and
site
designs
at
some
point
it
is
in
the
pipeline.
Does
it
mean
that
it's
coming
in
in
the
next
month
or
two
or
three
highly
most
likely?
B
Like
mica
said
there
is
in
the
schema,
there
is
a
set
of
actions
already
available
which
are
not
yet
supported.
Officially
in
the
target
release
tenants
or
in
production
tenants,
we
use
those
actions
actually
in
the
a
dock
which
has
been
warm
and
what
you
saw
already
from
mysen
my
screen
for
testing
the
upcoming
capabilities
and
stuff,
which
is
in
development.
So
we
absolutely
want
to
have
a
native
support
for
modern
pages,
but
that
is
extremely
complex
to
implement
to
support
every
single
scenario.
B
So
it's
coming
and
it
might
be
real
simple
as
a
first
step,
natively
inside
some
designs
and
side
scripts.
But
then,
if
you
need
to
have
anything
complex,
you
can
always
fall
back
on
the
BMP
PowerShell
in
the
and
the
PMP
provisioning
templating
model.
Until
the
side,
scripts
and
side
designs
are
natively
supporting
all
of
the
stuff.
B
There
was
also
a
question
from
Joel.
If
I
remember
correctly,
the
question
was
any
future
option
to
connect
to
an
existing
site
and
extract
templates
of
existing
elements,
which
is
a
fair
question,
would
be
great
to
have
a
capability
of
to
be
able
to
extract
existing
elements
and
I
would
say
sure.
Miko
can
probably
comment
out
there
any
designs
and
aspirations
on
it
one.
It
is
actually
a
surprisingly
difficult
thing
to
do
so.
B
We
use
PMP
crew,
we
implemented
the
PMP
provisioning
template
model
and
we've
been
implementing
that
now
for
five
years
and
it's
not
yet
even
ready,
and
that
shows
the
complexity
and
there's
130
contributors
in
the
PMP
provisioning
templates,
which
supports
extraction
so
shown,
and
the
engineers
behind
of
this
feature
are
looking
into
having
extraction,
support
for
lists
and
a
simplistic
lists
anything
complex.
It
will
be
delivered
later,
so
one
step
at
a
time
heading
forward
on
the
on
the
right
direction.
Let's
split
this
one,
not
super
cool,
really
valuable,
valuable
stuff.
B
Joel
had
a
speed
comment,
no
fun
if
it
sees
it.
That's
absolutely
true
and
Thank
You
Steven
for
referencing
the
set
of
sample
site
scripts,
so
github
calms,
my
SharePoint
as
PDFs
and
scripts
and
there's
example
set
of
size
scripts
available,
which
can
we
make
a
put
your
notes,
don't
stop
there?
Can
we
put
your
tool
on
the
spot?
Can
we
go
to
the
s/pdif
side
scripts
and
take
a
one
off
the
script
and
show
how
you
take
one
of
the
scripts
and
then
put
it
in
your
tool.
A
A
B
Somebody
already
well
I
will
one
more
time
get
a
link
on
the
site,
design,
side,
script,
documentation
in
the
official
Docs,
which
is
explaining
what
supported?
How
does
it
work?
How
do
you
use
this
with
SharePoint
Online
PowerShell
PNP
PowerShell
supports
this
as
well.
There's
a
REST,
API
interface
for
this
as
well,
and
then
you
can.
If
the
native
scripts
do
not
fulfill
your
business
requirements,
you
can
always
use
a
flow
or
Asha
functions
to
further
extend
the
what's
being
supported.
So
you
can
run
some
code
and
do
modifications
with
them.
A
A
B
Really
cool
stuff-
and
it's
carried
great
to
see
the
open
source
model
being
used
here
as
well,
because
it
helps
even
though
the
people
wouldn't
contribute
once
you
create
it
and
make
it
they
would
learn
from
the
sample
what
you
have
and
then
they
can
build.
On
top
of
that-
and
that's
always
super
valuable
as
well
obviously
would
be.
Creative
people
would
contribute
on
these
things,
but
hey
it
is
what
it
is.
Everybody
has
a
day.
Job
even
I
do
have
a
date
too.
B
There's
some
other
stuff.
What
I
always
also
do?
Not
only
this
stuff
said
it
is
fun,
it
is
gorgeous
Thank,
You,
Miko,
crate,
crate
demo.
We
we
have
like
five
minutes
so
for
Q&A
next
ship
on
deaf
stick
meeting
is
in
the
November
15.
Just
out
of
curiosity
should
be
covered,
do
a
deep
dive
on
ship
on
2019
dev
platform
and
do
live
demos
on
the
ship
on
2019.
Would
that
be
interesting
or
not,
or
is
there
any
other
kind
of
a
topics
which
people
would
like
to
see
in
the
generic
SP
dev
sick?
B
Next
time
for
SharePoint
framework,
we
were
pretty
obvious,
pretty
clear
what
we're
gonna
do
on
the
ownership
on
framework
side
of
the
things.
But
if
you
have
any
suggestions,
20:19
is
getting
some
attention.
We
could
have
a
special
2019,
a
session
where
we
really
go
to
the
ship
on
2019
and
get
it
documented
us
or
a
video
recorded
and
share
it
with
and
never
connect.
So
that's
that
probably
helpful.
B
Clearly
2019.
It's
a
good
idea.
Cute.
We
haven't
done
actually
that
much
power
apps.
There
was
some
power
amps
in
some
of
these
course,
and
it
is
really
dependent
also
on
what
kind
of
community
questions
and
community
demos
what
we
are
kidding.
We
do,
I
have
my
Q&A
I,
don't
have
a
queue
next
line,
and
so,
if
we
are
interested
in
seeing
more
power,
apps
in
the
context
of
SharePoint
I
definitely
will
be
again
checks
and
asked
run
demos
where
we
are
with
that
one
and
how
to
get
started
on
things.
B
Power
Apps
deployment
would
be
good.
Cec
I
see
the
sort
of
stuff
right
now
Kevin.
Unfortunately,
a
lot
of
this
stuff
in
with
power
apps
is
not
really
really
really
that
super
well-documented
or
does
it
actually
work.
So
it's
a
manual
operation
flaminius,
the
things
I
know
that
they're
working
on
API
so
that
stuff,
sir.
B
Can
we
have
a
generic
call
on
SharePoint
usage
such
as
content
types
subscription,
not
just
developer
and
and
pavol?
We
understand
you're
in
Bhutan
that
one
that
would
be
different
people
than
I
am,
and
so,
if
we
would
like
to
have
kind
of
an
but
I
do
understand
that
it
would
be
cool
to
have
let's
say
a
bi-weekly
or
monthly
calls
where
and
then
and
let's
say
so,
Chris
McNulty
and
all
of
these
people
would
actually
show
the
demos
and
have
a
discussion
on
the
future
direction
of
the
infuser
Trivium
functionalities.
B
That
would
make
a
lot
of
sense,
as
once
did
Roloff
SharePoint
framework
extensions,
do
not
work
on
a
classic
pages
and
not
support
it
pregnant
after
not
level
permissions
needs
when
using
powershell
that
such
good
feedback,
we
need
to
do
a
bit
up
a
bit
of
work
on
the
on
the
documentation
and
yes
were
off
in
the
classic.
You
would
have
to
use
chase,
link
or
user
custom
actions
on
those
models,
and
thank
you
kevin.
That's
a
good
point.
B
So
the
interest
own
is
a
great
podcast,
absolutely
what
mark
and
christmas
now
they
are
doing
now.
They're.
It's
not
interactive.
Demos
like
these
are
so
that
could
be
something
which
I
can
have
a
chat
with,
Mike
and
and
Chris,
and
and
then,
if
we
could
actually
set
up
something
like
that,
because
that
would
make
sense
in
this
goal.
B
We
talked
about
architectural
designs
and
use
its
patterns,
but
we
don't
really
go
to
the
admin,
admin
topics
or
IT
pros
topics
or
or
let's
say
into
the
topics
that
much
which
I
think
we
hit
the
hour
so
not
too
much
time
today
on
Q&A,
because
I
took
some
time
extra
time
on
my
discussion.
Hopefully
we
answered
many
of
the
questions
which
you
had
still
on
the
on
the
call
looking
forward
on
your
input
on
the
on
the
new
stuff,
which
is
going
to
be
released
on
SharePoint
and
F
platform
side.
B
We
will
absolutely
do
more
demos
on
those
in
the
upcoming
course
as
well.
Sharepoint
framework,
well,
the
1.7,
together
with
all
of
that,
so
edit
functionalities
is
coming
out
relatively
soon.
So
we
should
well
definitely
before
Thanksgiving,
because
you
should
not
ship
anything
between
Thanksgiving
and
holidays,
because
that's
not
a
good
thing.
So
that's
from
a
timing
perspective
I
can't
give
you
an
exact
date,
because
the
dates
might
still
move
slightly
now,
but
thank
you
everybody
for
joining.
Thank
you
for
your
input
and
please
reach
out.