►
Description
Recording of the SIG from May 3rd. Detailed agenda and covered topics are available via the MS Tech Community (http://aka.ms/spdev-community).
Download recurrent invite from http://aka.ms/spdev-sig-call.
A
Excellent,
so
let's
actually
get
started
on
this
one,
so
welcome
everybody.
This
is
to
share
pon
Patterson
practices.
How
matter
webcast
this
is
the
community
called
bi-weekly
community
call-
and
this
is
the
general
shape
on
deaf
community
calls.
So
originally
when
we
started
the
SharePoint
BMP
initiative,
this
school
was
actually
called
as
a
office
hours
as
we
noticed
that
the
monthly
community
calls
were
always
super
super
busy
and
there
was
no
time
for
Q&A.
A
And
then
we
have
a
separate
special
interest
group
which
is
meeting
bi-weekly
as
well
at
the
same
time,
which
is
around
the
SharePoint
framework.
So
on
that
one
we
concentrate
more
on
the
clients
are
developed
in
topics
and
other
client-side
and
SharePoint
framework
and
other
JavaScript
development
topics,
a
game,
SSP
PMP,
community
or
AKM
SSP.
A
Three
modes
are
typically
10
to
15
minutes,
and
then
we
talk
about
what
was
actually
shown
and
the
learnings
and
that
a
partner.
Then
you
can
also
contribute
and
github,
so
you
can
submit
pull
requests.
You
can
submit
issues
and
let
us
know
on
two
things
and
obviously
that's
one
way
of
providing
feedback
as
well,
so
submitting
an
issue
letting
us
know
if
there's
something
which
we
need
to
fix
or
you
found
potential
balk.
A
B
A
Community
course,
please
also
do
remember
to
mute
yourself
until
we
are
in
a
Q&A
section.
Potentially,
you
can
actually
open
up
yourself
or
open
up
the
audio
for
questions
no
moving
or
nothing.
So
today,
there's
a
few
slides
around
the
channel
announcements.
Nothing
super,
let's
say
traumatic,
all
those
few
things
actually
there,
which
is
interesting
and
then
we'll
concentrate
well,
I,
wouldn't
say
maturity
of
the
time,
but
quite
a
lot
of
time,
actually
on
the
modernizing
your
SharePoint
site.
A
A
What's
the
limits
of
that
one
and
how
it
actually
works
and
we're
gonna
talk
about
modernization
in
general
and
then
after
Burt,
we
have
dim
Joe
explaining
well
dim
Joe
released
a
adding
to
the
SharePoint
store
pretty
recently,
and
actually
we
haven't
really
paid
attention
that
much
on
the
SharePoint
events
in
this
course,
so
I
think
it's
a
good
time
to
do
a
refresh
on
the
on
the
process
and
the
learnings
from
game/show
around
that
process.
So
how
does
it
actually
work?
A
What
was
released
and
talk
about
that
one,
and
also
at
that
topic
or
after
the
topic
topic
I,
took
about
the
potential
future
direction
on
the
SharePoint
framework,
so
I'll
come
back
on
that
one
after
them
shows
demo
and
then
we'll,
hopefully
have
some
time
on
the
Q&A.
Now,
let's
actually
move
on
a
few
announcements,
so
documentation
guidance
over
as
I
mentioned
already,
a
MSS
PDF
ducks
and
is
our
location
for
official
SharePoint
documentation
we
dynasty
and
will
be
shut
down
actually
by
end
of
June.
A
If
I
remember
now
correctly,
the
timing
so
we're
moving
the
season,
documentation,
service
line,
documentation
all
of
the
documentation
to
dr.
Markham,
and
that
will
be
then
the
location
where
everything
will
be
maintained.
Some
of
this
transition
is
still
under
work,
so
we're
still
working
on
that
one.
But
the
whole
objective
is
to
get
everything
done
by
end
of
June.
A
We
had
eight
hundred
and
twenty
thousand
views
on
on
here
on
April,
which
is
pretty
recent
number,
we'll
I'm,
hoping
to
break
one
million
by
end
of
July,
sorry
and
by
end
of
June,
but
who
knows
we'll
see
if
we
can
keep
up
the
interest
on
our
documents
now
running
into
an
issue?
I
mentioned
this
one
already
around
the
feedback,
but
also,
if
you,
if
we
run
Indonesia
and
the
API
SharePoint
framework,
whatever
you're
trying
to
do
from
a
customization
perspective.
A
Please
let
us
know
so
use
the
AKMs
SP
dev
issues
list,
which
is
the
issue
list
and
the
SP
dev
dogs,
which
we
asked
this
twice
a
week.
Right
now,
with
an
engineering
potentially
might
be
increasing
that
to
be
three
times
in
a
week
and
we
then
prioritize
those
issues
which
are
coming
in.
Obviously,
if
you
run
into
a
critical
issue
like
SharePoint
Online
is
down,
this
is
not
necessarily
the
location
to
report
critical
issues,
critical
critical
issues,
and
then
you
absolutely
need
to
report
them
using
their
other
channels
as
well.
A
But
this
is
really
around
letting
us
know
that
some
API
has
changed.
Sharepoint
framework
has
changed,
there's
a
behavioral
change
on
somewhere,
and
then
we
can
figure
out.
Is
it
a
buck
on
our
side
and
SharePoint
the
engineering
side,
or
is
there
something
other
things
to
make
you
successful
within
your
customization
and
also
all
of
the
comments,
if
you're
adding
a
comments
on
the
documents-
and
they
are
actually
visible
in
this
issue
list
as
well
for
a
discussion?
So
please
remember
that
this
issue
lists
are
not
just
one-to-one
discussions
between
you
and
shape
and
engineering.
A
It's
also
meant
to
be
a
channel
for
community
discussed
between
each
other.
So
if
you
know
actually
an
answer
to
some
of
the
questions,
you
can
absolutely
participate
on
new
season
version
for
SharePoint
Online
would
live
on
last
Friday.
So
this
is
the
new
NuGet
package
for
client
SharePoint
Online.
The
client-side
object
model
package
made.
The
main
changes
here
are
around
GPR
D,
so
GDP
our
GDP
are
the
European
legislation.
A
Now
on
the
kind
of
new
things
this
went,
live
actually
I
think
on
Tuesday
Tasha's,
well,
Monday
Tuesday,
depending
on
which
side
of
the
world
you're
actually
living
Tasha's
pushed
out
the
blog
post
in
the
Microsoft
tech
community.
So
the
admin
and
API
supports
for
connecting
existing
SharePoint
team
sites
to
new
office.
365
groups
is
rolling
out,
so
this
is
now
available
from
a
powershell
side
and
also
from
a
see
some
sites.
A
We're
able
to
programmatically
create
a
new
group
for
your
existing
class
except
a
SharePoint
site,
and
this
is
basically
the
same
thing
as
Krupa
find
within
our
official
terminology.
I,
don't
know
who
said
it,
but
anyway
we're
not
supposed
to
be
using
the
Krupa
fighter
him
anymore,
which
is
kind
of
awkward,
because
we've
been
using
the
Crucified
term
within
these
calls.
For
since
when
was
it
November
I
think
in
November
timeframe,
November
monthly
community
call.
We
actually
showed
the
first
time
to
Chrome
if
I
preview,
which
is
by
Bert
but
anyway.
A
So
it's
not
about
Krupa
fiying,
it's
about
connecting
at
the
site
to
the
group.
That's
really
the
terminology
that
should
be
used.
I
think
the
same
applies
for
hoop.
If
I,
which
I
used
view
community
calls
back,
I,
don't
think
who
Biff
is
really
the
right
term.
On
the
other
hand,
it
actually
explained
what
happens
there.
A
C
C
C
C
A
Maybe
one
thing
to
consider
is
that
it
is
by
design
that
communication
sites
do
not
have
of
a
straight
65
group
associated
to
it.
Now
it's
that
decision
and
the
right
decision
from
a
feature
crew
who
owns
the
communication
site.
Obviously
that's
debatable.
There's
multiple
different
opinions
on
that.
A
So
I
would
rather
recommend
to
open
up
a
discussion
in
social
media
or
in
Mike's
of
tech
community
around
the
fact
that
why
isn't
group
created
for
communication
sites
and
then
making
that
native
as
a
native
behavior
as
part
of
the
communication
side
Edie,
if
that
is
where
we
actually
want
to
go
your
feedback
as
a
community
member
super
super
important
on
these
things.
Personally,
probably
shouldn't
say
this
out
loud,
but
my
personal
feeling,
my
personal
thing,
I'm,
not
in
the
future
pronate
the
communication
site.
A
But
for
me
it
would
make
more
sense
to
have
a
consistent
creation
time
for
anytime.
You
create
a
set
point,
SharePoint
site
collection.
You
could
get
a
crew
now
it's
different
people
who
make
those
decisions
for
that
particular
call.
So
please,
please,
please
give
feedback
using
the
different
channels
sometime.
A
Cute
moving
on
are
things
so
one
slide,
a
few
more
slides,
some
numbers
from
April
2018
and
the
numbers
are
obviously
more
interesting
for
us
in
in
SharePoint
community
and
share
content
sharing.
Then
you
as
a
participant
on
this
call,
but
this
actually
shows
that
there's
quite
a
lot
of
material,
quite
a
lot
of
other
people,
then
only
you
interested
on
on
the
SharePoint
development.
That's
why
we
actually
showed
those
numbers
we
had
150
4,000
minutes.
Youtube
watch
watch
time
with
kind
of
cool
25,000
views
in
YouTube
the
average.
A
You
can
easily
count
how
many,
how
many
minutes
is
average
from
that
one.
The
watch
time
github
uses
growing
all
the
time
with
this
good
sign,
because
more
and
more
we
will
be
releasing
open
source,
stuff
and
open
source
initiative
in
the
future
as
well
so
learning
to
use
the
kitten
is
super
important
for
any
upon
developer
as
well
in
the
dorfner,
my
stuff
that
come,
we
had
eight
hundred
and
twenty
three
thousand
views
and
that
went
actually
slightly
down
any
a
fraction
down
from
march,
but
basically
april
is
the
spring
break
month.
A
So
that
is
as
expected.
We
can
see
that
across
the
multiple
two
other
channels
as
well
on
the
PMPA,
reusable
components.
This
is
BMP
powershell,
BMP
season
and
PM
peaches.
We
had
eleven
thousand
five
hundred
and
eighty-one
tenants
being
used
using
any
of
those
in
april,
and
we
hit
nine
point.
Ninety
nine
billion
HTTP
requests
and
it
was
so
close
the
prague,
the
ten
billion
requests
in
a
single
month
limiter,
which
which
the
team
was
slightly
disappointed,
will
get
that
and
get
there
absolutely
but
Lou
looking
into
growth.
A
Metrics
will
absolutely
break
the
ten
billion
within
the
May
one
node
in
here,
because
we
get
that
comment
quite
a
lot.
People
are
then
asking
that
well
wait.
What
about
the
SPF
X
we
right
now
we
don't
have
any
public
numbers
with
cyclic
actually
share
around
the
SharePoint
framework.
Use
it's
in
the
SPF
X
bi-weekly
community
call,
which
show
the
growth
curves,
but
we
don't
actually
show
numbers
so
probably
in
SharePoint
Conference
in
the
keynote
will
actually
talk
about
the
real
success
of
SharePoint
framework
using
actual
numbers.
A
So
within
a
few
weeks
or
a
few
weeks
now
a
quick
update
on
the
roadmap.
So,
basically,
everything
what
we
promised
to
deliver
in
ignite
in
this
developer
roadmap
has
been
pretty
much
now
delivered
at
least
to
preview.
So
a
certain
capabilities
like
the
azure
ad
and
the
craft,
access
from
SPF
X
are
still
in
preview,
so
it
hasn't
g8.
Yet
all
of
and
the
latest
thing
going
life
in
the
preview
at
least,
is
to
crop
refine.
A
The
next
big
announcements
are
queued
up
for
starting
from
next
week,
till
next
week,
Tuesday
I
think
a
little
Monday,
we'll
probably
announce
something
as
a
blog
post
on
Tuesday
there's
a
SharePoint
portal
session
or
SharePoint
session,
which
I'm
doing
in
a
built.
So
if
you
are
in
build,
please
check
it
check
that
one
where
we
actually
going
to
talk
about
a
lot
of
the
new
capabilities
for
SharePoint
framework
as
well,
and
then
SPC
is
coming
within
two
to
three
weeks
as
well.
A
So
a
lot
of
new
announcements
coming
quite
soon,
but
we
can't
yet
talk
about
them
in
the
community
course,
but
obviously,
next
week,
Thursday
well,
when
we
have
SharePoint
framework
community
core
will
talk
about
all
of
the
new
announcements
around
the
SharePoint
framework,
which
we
mentioned
or
announced
in
built
and
then
within
a
week
or
two.
We
it's
gonna,
be
SPC
and
we're
gonna
talk
about
more
on
these
things.
So
please
follow
up
on
the
on
the
social
media
and
on
the
under
communications
on
what
is
new
and
what's
actually
happening
so.
A
So
right
now
nothing
until
built
SPN,
a
that
is
correct.
From
now
built
is
within
two
business
days,
so
nothing
is
going
to
be
announced
between
Friday
and
Friday
and
today
and
built
is
actually
starting
on
Monday.
So
we
can
have
first
announcements
going
live
on
Monday,
so
patience,
one
more
day
or
two
days
and
depending
on
how
to
account
this
two
business
days
and
view
the
weekend
as
well.
C
Absolutely
but
this
is
like
and
Ethan
early
preview
of
of
the
guidance
waiting
around
normalization
so
before
actually
jumping
into
the
meat
of
my
section.
I
want
to
take
one
step
back
and
just
talk
about
what
is
causation
mean,
what
are
the
big
components
of
modernization
because
we
touched
upon
these
already
in
past
cuticles,
but
you
can,
if
I
always
try
to
kind
of
break
it
down
in
three
big
steps.
One
is
maximize
to
use
your
model
distant
libraries,
so
what
are
some
areas
is
something
if
you
turn
on
a
tenant
level.
C
Sometimes
there
are
certain
listen
highways
that
don't
work
the
modern
and
we
have
a
scanner
that
you
can
run
to
detect
those
and
to
understand
why,
and
then
you
can
remember
gate
and
kind
of
get
the
most
of
your
list
alive
is
showing
everything
up
in
the
modern
UI.
So
there's
step
one
and
just
to
be
clear:
there
is
the
top
link
acre
of
them
s.
C
These
two
already
were
touched
upon
and
Pascal's
today,
I
want
to
really
focus
on
something
brand-new,
something
which
off
for
the
first
time
so
really
early
preview
and
that's
guidance
and
tech
around
how
to
transfer
your
classic
wiki
and
site
pages
into
modern
site
pages,
so
essentially
a
tool
that
you
can
use
to
take
your
classic
wiki
page
and
get
like
a
modern
equivalent
from
it.
So
now,
let's
jump
in
now.
This
is
for
you
guys
or
be
fairly
basic
information,
but
just
to
get
started.
C
A
wiki
page
is
a
mixture
of
text
and
web
parts
right,
so
text
can
be
I've,
complex,
formatting
and
a
basic
formatting
and
like
tables
full
sizes,
bullet,
etc,
and
then
you
can
have
one
or
more
webparts
in
the
mix
to
it.
The
text
and
the
wiki
page
has
a
layout.
So
you
see
the
text
layout
button
on
the
ribbon,
so
you
get
that's
like
there's
a
number
of
thing
about
eight
defaults,
the
layered
flavors
that
you
can
think
in
my
path
page
is
less
used.
When
we
scan
the
environments
we
see
way.
C
Less
webpages
compared
to
wiki
page
is
better
so
I've
being
used,
and
the
web
page
is
essentially
a
layout
with
red
zones
and
the
rappers
own.
You
can
put
one
or
more
robots,
it's
kind
of
setting
the
scene
where
we
start
from
so
the
scope
of
the
tooling
that
I'm
gonna
show.
Is
this
be
able
to
mobilize
those
sites?
You
might
ask
what
about
publishing
sites?
C
C
So
in
the
first
step,
the
visioning,
the
page
transformation
engine
will
read
our
model
and
we're
going
to
show
the
model
in
the
demo.
But
essentially
it's
the
model
gives
you
all
the
flexibility
you
want
to
drive
the
migration
story.
So
what
others
page
migration
do
essentially
reading
sauce
page
with
webparts
in
creating
something
new,
a
modern
page
with
modern
client-side
web
parts.
Being
first
party
to
her
party
represent
by
customer,
each
customer
might
have
their
own
requirements
might
want
to
plug
in
their
own
turf
rtwebparts.
C
Plus
the
model
is
loaded,
we
analyze
a
page,
so
analyzing
a
page
means
just
reading
the
file
and
him
getting
all
the
web
part
information
and
the
layout
from
the
actual
source
page.
So
this
gets
you
a
collection
of
web
parts
with
that
properties.
Wiki
text
is
kind
of
put
in
a
fake
wiki
takes
the
part,
so
we
just
stuffed
a
wiki
HTML
into
where
I
kind
of
a
fake
web
browser.
So
we
have
a
nice
collection
of
web
parts
and
a
layout
to
go
to
the
next
step.
C
The
next
step
is
step
3,
and
here
we
essentially
enrich
the
information
we
got
from
the
web
part.
So,
let's
give
an
example
and
XSLT
list
you
were
passed,
then
you
put
it
on
a
page.
You
can
pick
a
view
and
say,
like
I,
want
to
show
this
document
library
with
this
particular
view
great
now,
when
you
export
that
well,
look
at
the
properties,
we
don't
tell
you
like,
which
view
was
used.
We
give
you
the
XML
definition
of
the
actual
view.
C
C
We
have
and
that's
what
this
step
3
is,
is
doing
and
then
finally
step
four
is
applied
and
rich
data
and
the
model
to
generate
a
model
glance
at
page
with
webparts,
first
particular
property,
modern
web
baths
on
the
page
and
save
the
page
and
very
high
level
that
more
things
would
become
more
clear.
But
this
gives
you
kind
of
a
quick
overview
here.
C
C
C
C
Here.
Is
the
web
part
page
being
transformed
famous
robber?
You
see
the
image
going
to
the
right
side
as
an
image
here
where
Park
you
see
the
list,
and
you
see
the
right
side.
You
see
a
script
at
the
web
birthday
now
scripted.
The
web
part
is
not
something
that
Microsoft
Office
out
of
the
box.
So
it's
a
third
party
by
part
and
this
just
to
show
you
that
you
can
use
third
party
web
parts
in
the
transformation
model
use
anywhere
product.
C
C
You
should
see
like
a
SharePoint,
yep,
H
yeah,
all
right
super,
so
I
tried
did
my
very
best
to
make
the
most
ugly
looking
wiki
page
in
the
world
and
I
think
I
succeeded,
but
this
for
a
purpose,
because
this
wiki
page
shows
a
lot
of
content
and
web
parts
that
we
can
transform
into
a
modern
page.
So
let's
have
a
first
quick
peek
at
the
source
page.
So
this
is
a
wiki
page
I'm,
going
to
put
it
in
edit
mode.
So
you
can
see
the
layout.
C
C
Inventing
bullets
tables
out
of
table
call
us
so
the
most
commonly
used
the
formatting
options
in
text
are
here
scrolling
down.
We
see
here
like
to
list
view
web
plus
a
basic
list
and
becomes
library
each
having
custom
view.
You
see
a
conflict
editor
web
product
web
content
is
embedded.
We
see
the
same,
pointing
to
an
HP
X
file,
so
just
referencing
a
file.
We
see
right
script,
editor
web
path,
showing
this
alert
message
and
add
in
fact,
so
add-ins
which
work
implies.
C
Images
also
work
on
model
pages
and
same
applies
for
the
modern
web
processes.
This
hello
world,
my
father's
in
modern
as
vivix
webparts,
which
offers
obviously
works
in
a
modern
place
if
it
also
works
on
a
classic
page.
So
we
have
put
those
on
the
classic
page
that
I
didn't
and
a
motor
than
a
web
part.
C
What
else
do
we
have
here?
We
have
a
media
report
showing
media
located
into
the
SharePoint
site,
so
insiders
library,
as
an
mp4
file,
just
YouTube
from
that
which
is
an
iframe
on
that
in
here
we
have
an
Excel
workbook
loaded
should
load
doesn't
want
to
live
right.
Now,
a
Visio
one
picture,
an
image
gallery
showing
widgets
and
here's
the
excel
sheet
by
the
way.
So
it
is
there
what
else
HTML
for
my
parts,
page
viewer
web
part
and
some
really
surprised
so
a
collection
of
commonly
used
web
parts
are
on
this
page.
C
I
want
to
transform
this
page.
You
want
to
create
a
modern,
equivalent
form
from
this
page,
and
since
this
is
very
early
early
preview,
I'm
gonna
show
you
the
code
based
approach,
calling
it
fire
code
later
on.
You
will
be
able
to
also
use
PowerShell,
so
there
will
be
powershell
commandlets
that
you
can
use
to
trigger
the
page
transformation
now
before
doing
the
actual
transformation.
Let's
talk
about
the
model
because
remember
that's
step.
One
I
talked
about
this
flexible
model
that
you
can
tell
it
week
and
that's
actually
an
XML
file.
C
C
Now
each
web
parts
that
you
want
to
transform
is
defined
in
here
so
sample
X
of
T.
This
report
is
defined
and
we
list
the
properties
which
we
think
might
be
interesting
for
you
when
you
drive
page
transformation
of
a
part
transformation.
So
you
have
these
properties.
Let's
remember
that
we
talked
about
that.
That
list.
The
view
ID
the
model
of
a
proxy
is
a
list
view
ready
yeah
and
we
don't
have
it
what's
the
way
to
get.
It
is
to
call
a
function
on
this
web
part.
C
So
when
the
tool
runs,
it
sees
the
exterior
part,
and
it
understands
that
wait.
I
need
to
call
this
function.
This
detect
used
view
and
taking
in
the
input
from
the
web
back
from
the
actual
process
of
taking
actual
list,
ID
and
actual
XML
location
of
the
web.
Part
and
out
comes
a
ListView
ID,
and
this
function
is
nothing
more
than.
C
A
basic
method
that
we
offer-
let's
see
where
this
one
is
here,
is
listed.
Thank
you.
You
see
the
input
string
comes
out.
It
does
check
the
mystery
XML
invariants,
it's
a
pipe
with
the
use
of
UID
or,
if
not
found
the
default
view
ID
of
the
particular
list,
or
you
might
wonder,
like
okay,
fine,
there
will
be
some
functions
delivered
by
the
tool.
Great,
but
I
want
to
make
my
own
functions.
You
can
so
scrolling
up
a
little
bit,
there's
an
add-on
section,
so
you
can
define
your
own
assemblies
here,
scroll
through
Mike.
C
You
see
this
sample
had
all
the
DLL,
so
you
define
your
own
assembly.
You
tell
us
which
type
my
custom
functions.
You
want
to
use
from
the
assembly
and
give
it
a
name
called
the
custom.
Once
you
have
done
that
you
can
then
start
doing
something
like
this
so
say:
custom
votes
and
then
your
matter
thing.
So
you
can
just
extend
the
model
in
the
logic
by
adding
an
assembly,
but
I
was
having
to
change
the
actual
rule.
C
So
I
hope
this
shows
some
flexibility,
let
them
all
there.
So
you
can
enrich
the
web
of
properties.
Next
step
is
mapping
them.
So
how
do
I
translate
this
exhaustive
list?
You
were
passed
in
to
something
modern
for
that.
We
have
a
mapping
I'm
gonna
zoom
in
on
this
mapping,
so
we
map
our
lists
to
this
this
mapping.
We
take
a
real
place
to
the
source
report,
with
a
combination
of
the
client-side
text
and
the
client-side
web
part
of
the
type
list.
C
So
a
box
list
web
part,
as
you
probably
know,
from
previous
calls,
and
for
working
with
clients
at
pages
client-side
web
parts
require
proper
jason
properties,
so
education
control
data,
which
contains
a
collect
the
webcast
properties,
already
swept
up
properties.
They
are
configured
at
runtime
how,
by
replacement
of
token,
so
it's
kind
of
a
tokoha
placement
model.
So
if
I
scroll
in
here
a
little
bit
to
the
right,
you
see,
for
example,
the
title
token
over
here,
and
this
is
server
health,
if
URL
token.
C
C
This
source
report
can
maybe
have
multiple
targets,
which
is
valid
use
case.
This
one
has
multiple
targets:
we're
gonna
pick
another
example:
the
content
of
the
web
part
so
for
content
of
the
web
part.
When
you
provide
a
Content
link,
so
a
link
to
a
file
to
an
HTML
file
to
an
age
fixed
file,
you
can
perfectly
replace
it
with
an
and
all
the
books
content.
Embed
web
part
goes
great.
C
However,
if
you
just
provides
the
raw
HTML
inside
the
part,
then
we
need
something
else
like
a
script
at
the
web
part,
which
is
a
customer
perfect
used
here
and
this
mapping
to
distinguish
which
happened
to
use.
You
can
call
what
we
call
a
selector
which
there's
nothing
more
than
a
methods
which
gets
input
from
the
web
part
and
returns
a
string
being
the
name
of
the
mapping
to
use.
C
So
this
way
you
can
get
a
lot
of
flexibility
around
how
to
which
having
to
apply,
in
which
case
it
can
be
fluid
dynamic
e,
alright,
so
that
some
some
information,
the
model,
let's
actually
run
it
go
to
my
test
case,
and
this
is
just
a
regular
test
case
with
the
shows
the
API.
So
you'll
get
a
base,
transformation,
information
class
that
you
can
populate
and
then
you
were.
C
It
takes
the
actual
pages
input
in
the
constructor
and
then
you
call
the
patient's
Tomatoes
transform,
there's
lots
of
flexibility
in
how
it
behaves
and
what
you
can
convey.
It's
too
much
detailed
for
today,
I'm
just
gonna
today.
Just
read
this
one,
how
it
is,
and
so
I'm
gonna
right
click
and
run
this
test
case.
C
A
C
Already
showed
a
few
seconds
ago,
so
that
should
be
the
one
that
we
need.
Yes,
so
a
few
seconds
ago
a
page
was
created
called
migrated
and
scrap
parts
for
now.
There's
a
convention
used
in
this
preview
later
on.
You
will
be
able
to
configure
how
do
you
named
it
the
new
page-
and
we
couldn't
talk
about
that
as
well-
the
final
slides
of
this
session
so
but
let's
have
a
peek
here.
What
did
we
get?
C
Look
good,
not
at
all
so
first
thing
to
notice
our
alert
so
hey
the
script
prints,
so
this
will
transform
from
the
classic
page
to
the
new
page.
Do
you
want
to
embed
script
like
this?
It's
discussable
and
you
might
want
to
just
stay
away
from
this
approach,
but
reality
is
that
there's
a
massive
amount
of
plastic
pages
having
script
so
scripts
might
be
I
be
valid
to
have
in
there
going
formats
or
not.
C
C
Okay,
all
right
here
we
are
so
in
the
first
row.
You
see
the
wiki
text.
Remember
that
all
of
us
text-
and
you
see
that
the
formatting
of
the
text
is
there.
So
if
I
select
the
bold
piece
and
I
go
to
the
fast
about
confirmation
for
the
text
confirmation
you
see
that
bold
is
selected.
If
I
go
today
highlight
yellow
is
selected,
so
we
create
compare
each
other.
It's
compliant
with
the
text
editor
in
modern
city,
indenting,
being
retained,
two
bullets,
the
numbers,
the
tables,
the
colors,
all
being
retained,
then
going
down.
C
C
We
see
the
content
editor
web
parts,
this
one
with
embedded
link
to
the
file.
Essentially,
documents
this
profile
again
distributor
our
added,
so
this
handsome
here
wants
to
get
control.
Sorry,
Samir,
and
so
this
is
the
add
in
part
that
was
on
the
plastic
page
showing
up
in
a
modern
page.
Here
is
our
model
in
client-side
web
part
showing
up
again
same
configuration,
so
we
we
can
retain
the
confirmation.
C
This
is
there's
one
thing
that
that's
currently
not
there
and
not
supported
from
a
tech
perspective,
and
that's
a
wiki
page
having
embedded
images
and
videos
because,
like
a
text,
part
in
modern
UI
cannot
have
embedded
images
and
videos
as
a
design
choice
so
to
work
around
what
the
to
put
a
place
over
saying
like
okay.
Here
there
was
like
an
iframe
I'm
patting
this
particular
YouTube
video.
C
C
Even
the
summary
links
is
replaced
by
clean
HTML,
which
works
in
each
viewer,
so
what
all
the
parts
are
already
met,
but
the
common
commonly
used
for
us
are
already
are
mapped
in
this
current
version.
We're
working
on
quantify
query
call
to
research
reports,
madam
to
the
highlighter
content,
modern
equivalents,
but
I
hope
this
gives
you
like.
If
you
were
that
there
is
some
level
of
feature
parity
once
we
pass
on
that,
it's
back
to
slides
for
a
second.
A
A
C
Yeah
I
want
to
just
talk
about
two
things,
pretty
quick,
so
what
you
saw
is
that
we
created
a
new
page
for
the
existing
classic
page,
so
we
are
thinking
about
a
model
where
the
classic
and
the
did
the
modern
page
are
linked
together,
where
you
can
kind
of
give
your
users
a
way
to
option
to
acknowledge
that
the
page
has
been
migrated
and
keep
the
modern
page
or
provide
feedback.
White
was
not
good
at
cetera.
This
is
a
mock-up.
C
A
Which
boots
Burt
find
a
way,
so
there's
a
bird's
demo
here,
sorry
for
jumping
Burt
on
this
one
I
can't
help
myself
server
man.
Now.
What
you
just
said
is
super
super
super
super
critical
in
the
discussions
related
on
the
modernization.
Now
you
should
never
ever
go
to
a
customer
or
have
a
discussion,
the
Terry.
We
can
modernize
everything
and
then
without
understanding
what
can
you
modernize
and
what
you
cannot
modernize.
A
So
what
is
the
matching
capabilities
and
sure
the
modern,
a
you
is,
are
going
leapfrogs
every
now
and
then
forwards
and
within
few
weeks
and
there's
busy,
there
will
be
again
with
announcements
so
gradually
they
will
catch
up
on
the
under
functionalities.
What
is
needed
in
classic,
but
really
the
key
is
to
understand
before
going
anybody
to
promise
to
modernize
them
is
to
understand
what
the
customer
is
having
on.
A
What
to
deployment
is
having
what
are
the
webparts
over
there
and
then
is
there
a
matching,
wet
bar,
or
is
there
a
compromised,
wet
work,
because
if
the
customer
or
isn't
any
internal
customer
and
external
customer
demands
that
we
want
to
go
to
the
modern
UI
s,
then
you
can
always
have
to
do
the
discussion
that
ok,
that
particular
web
part
isn't
there,
but
there's
a
close
enough
web
part
which
is
following.
So
what
if
we
would
do,
mapping
one-to-one
between
them
so
absolutely
and.
C
C
That's
a
definite
possibility
and
I
think
you
will
have
to
get
for
it
to
meet
your
customer
requirements.
Yep,
because
my
special
for
the
big
Christmas
just
to
wrap
up
I'm
gonna
go
one
slide
deck.
There
is
a
link
here
on
the
deck
to
the
source
code,
so
everything
that
you
have
seen
is
already
available
from
a
code
perspective.
So
again,
if
you
want
to
get
very
early
access,
you
can
just
get
the
PNP
a
tool,
super
sorry
and
look
at
the
code
and
play
around
now.
C
The
actual
aim
is
to
get
something
published
II
when
you
get
into
power
gallery
before
the
end
of
May,
hopefully
before
the
SharePoint
conference.
Even
so,
this
is
a
developer.
You
can
pick
the
Nuka
package
and
use
it
and
there
will
be
a
powershell
commandlets
as
well
that
you
can
use
to
it's
kind
of
a
transformer
page
using
one
powershell
commandlets.
C
The
reason
why
they
are
separate
for
now
is
just
to
give
some
more
deployment
agility
later
on.
It
definitely
is
the
plan
to
just
embed
all
of
this
in
the
directorship
repeat.
The
cohort
line
and
ship
I
mean
if
I
were
shell
there,
so
that
you
don't
have
to
have
for
it
separately,
but
while
run
the
developer
face
and
in
the
preview
face
of
this
tooling
and
there
will
be
their
circuits,
so
it
gets
easier
to
update
essentially.
C
C
Actual
it's
all
squid
and
feel
free
to
reuse
already,
meaning
if
you
are
I,
think
this
and
I
discuss
about.
If
you
would
like
to
go
the
product
that
does
page
migration
just
reuse,
what
what
there
is
is
is
there
to
reuse
and
to
further
will
further
improve
it.
There
is
an
open
source
components
that
can
be
used
for
patient
summation
for
your
custom
project
for
commercial
purposes.
Whatever
you
want
to
do
with
it
think
you
is
good.
It's.
A
Mit
license,
and
now
you
need
to
remember
that
it's
it
is
an
open-source,
though.
So,
if
there's
a
box
over
there,
we
are
kind
of
a
there's,
no
SLA
for
fixing
that
bug.
But
now,
if
you
build
your
own
offering
on
top
of
this,
you
can
absolutely
get
the
code
and
hopefully
contribute
back
as
well
on
the
structure.
What
is
here
or.
C
You
can
make
it
like
a
nice
mapping
file
with
some
additional
positive
efforts
that
fixes
some
of
ya
gaps
in
our
first
party,
offering.
That
would
be
a
super
great
great
thing
to
share
with
the
community
or
for
you
to
even
the
head
cell.
If
you
want,
don't
don't
share
it,
but
you
see
that
I
think
there's
I
see
a
lot
of
opportunities
and
possibilities
here
and
there's
a
new
terrain
getting
into
a
new
area
and
there's
not
much
out
there.
That
can
do
this.
Thank
you.
Steve
yeah.
A
So
classic
migration
tooling
doesn't
do
modernization,
it
just
moves
content.
It
doesn't
actually
do
mapping
off
the
functionalities.
So
this
is
a
great
starting
point
for
helping
your
customer
to
transform.
When
somebody
raises
their
hands
saying
we
need
to
move
now
so
because
it's
not
really
my
creation,
it
is
transformation,
so
cool,
I
think
from
a
timing
perspective.
We
need
to
move
to
demo
for
the
to
talk
about
adding
an
absurd
process
and
I
I
can
update
in
certain
level.
B
So
tell
me
if
I
speak
too
close
to
my
microphone
or
too
far-
and
you
don't
hear
me
well
so
I'm
starting,
my
name
is
Dylan
off
in
Bulgaria.
This
is
Eastern
Europe
and
I'm,
a
freelancer
I'm
doing
consulting
from
some
time
and
from
the
beginning
of
this
year,
I
decided
to
try
to
move
from
consulting
to
product
development.
Again
rated
in
SharePoint
and
I
have
some
experience
with
that
absorb
store.
B
So
today,
I
want
to
share
what
I
have
learned
and
just
give
you
some
guidelines,
suggestions
and
to
point
to
some
specifics
in
the
adding
development.
What
I
will
do
is
first
I'll
show
you
the
seller,
dashboard
and
some
important
links
there
and
then
I'll
do
a
demo
of
to
audience.
The
message
that
I
want
to
give
with
this
presentation
is
first
adding
a
development
model
is
not
that
it
is
actually
very
powerful
one
and
it
can
be
used
together
with
SharePoint
framework.
B
What
I
mean
is
that
github
is
great
they're,
great
samples
and
functionalities,
but
the
small
companies
they
they
don't
have
the
expertise
to
get
the
code
to
build
it,
to
fill
it
with
their
environment
and
to
deploy.
So
from
that
perspective,
I
would
say
that
up
source
is
important
for
these
small
businesses
to
get
end-to-end
solution,
and
that
is
something
that
I
decide
to
try
to
get
some
more
functionalities
package
them
and
to
deploy
here.
B
So
to
see
whether
the
business
will
like
this,
my
ideas
and
my
solutions
who
can
participate
in
the
absorb
store,
everybody
either
a
single
developer
or
a
company's.
You
can
visit
this
link
and
see
how
you
can
register
for
the
apps
or
store
again
you
can
do
it
as
a
single
developer
or
like
a
company
and
once
you
register
to
the
apps
or
store
you
have
access
to
the
developer,
dashboard
or
so
called
severed
our
board,
and
you
can
choose
the
program
you
want
to
participate
now.
B
B
Let
me
then
directly
jump
on
the
demo,
and
first
I'll
show
you
from
you.
If
the
perspectives,
what
I
have
deployed
for
to
the
store
and
it
is
free
and
then
how
I'll
show
you
more
than
architecture
behind
this
I'm
changing
my
screens
and
now
I
am
going
to
my
SharePoint
page,
just
something
that
when
I
was
asking
the
companies,
this
small
companies
that
I
am
talking
about
what
they
want
as
functionality,
they
always
say
we
want
something
to
work
everywhere.
B
B
Such
kind
of
feedback
form
so
over
here
on
this
form
is
retrieve
dynamically
from
a
list
item
all
these
feedback
text
whether
to
have
ratings,
whether
to
not
have
ratings,
the
submission
text,
even
the
styling,
if
I
scroll
a
little
bit
down
I,
can
show
you
again
the
same
component
but
with
different
power.
So
all
this
is
read
dynamically
and
it
is
viewed
with
padding.
There
is
no
SharePoint
framework
extension
here,
as
I
mentioned
this
word
in
a
classic
page
again.
B
So
here
at
this
page,
I
have
deployed
the
same
component
with
the
same
feedback
settings
here
and
what
I
want
to
show
you
again
is:
there
is
another
option
to
use
patents
with
functionalities.
We
can
achieve
something
like
this,
so
how
does
all
this
works?
First
of
all,
I
have
installed
an
add-in
and
I'm
not
going
to
go
deeper
in
the
add-in
architecture,
but
basically,
when
we
install
an
add-in,
it
has
a
dedicated
subside,
so
this
subside
have
a
specific
URL
and
it
is
just
a
regular
or
inside.
B
This
is
a
page
that
use
traditional
techniques
form
the
on-premises
development,
but
I
have
bring
also
some
modern
experience
like
this
panel
and
the
form
that
I
showed
you
all
settings
are
reached
dynamically
from
this
campaign
lives.
When
somebody
reacted
on
the
forum,
it
is
saved
here
in
another
list,
I'm
not
going
in
in
sorry
in
what
this
list
contains.
But
I
just
wanted
to
draw
you
the
model
that
I'm
speaking
about
and
what
I
showed
you
is
not
new.
B
This
is
the
traditional
Aden
model
and
I
show
you
a
component
that
was
loaded
inside
my
frames,
the
new
thing
here
and
where
I
brought
the
office
UI
fabric,
we
are
visual,
studio,
cold
and
wet
packet.
Is
here
in
the
page
that
we
show
inside
the
iframe.
I
bundle
one
JS
file
and
it
brings
the
whole
functionality
and
this
functionality
it
use.
Rest
goes
to
the
rest,
calls
for
the
list
inside
the
same
way.
The
third
demo
that
I
showed
you
this
one,
which
actually
is
more
nice-looking,
and
there
is
no
strawbe
snotting.
B
It
looks
a
little
bit
different
model
again
on
the
top
of
SharePoint
headings
when
the
adding
is
installed,
I
create
one
passage
library
in
the
root
side
and
then
I
upload
one
script.
So
this
script
again,
bundled
with
the
technology
that
I
have
told
you
now
this
file
can
be
welded
inside
quasi
page
for
content
editor.
B
Just
to
show
you
a
little
bit
advanced
example,
if
scenario
with
SharePoint
framework
extension,
I
change,
my
page
and
what
you
see
now
is
a
modern
on
the
site,
and
it
has
this
component.
This
component
is,
is
teaching
bubble
of
the
office
UI
component
and
it
is
displayed
on
each
single
page,
no
matter
whether
you
have
a
classic
page
or
modern
page.
As
you
see,
this
control
is
here
and
it
can
be
used
to
show
some
small
word
input
messages.
B
This
approach
for
loading
component
on
each
pages
can
be
used
for
different
components,
for
example
I.
Instead
of
this
functionality,
which
is
somehow
inbox
like
Facebook,
it
can
will
feedback
form
and
so
on
again,
just
I
just
want
to
show
you
what
the
approach
the
technical
approach
behind
this
demo
is.
B
First
of
all,
I
use,
combination
of
add-in
and
SharePoint
framework
and
because
I
start
speaking
about
the
apps
or
stores
currently
absorb,
does
not
support
SharePoint
framework,
which
I
would
say,
is
a
big
limitation.
So
if
you
want
to
deploy
something
you
you
should
forget
for
the
SharePoint
framework
at
all
for
now,
but
if
we
go
out
and
look
as
a
development
model,
we
I
think
that
combining
audience
in
SharePoint
framework
is
great
approach,
because,
as
I
said,
we
can
use
the
imagine
web
to
store
our
lists.
B
We
can
deploy
script
at
the
host
web
and
to
have
script,
link
and
custom
application
customizer
deployed
in
our
site,
and
in
this
way
we
are
handled
Kwasi
pages
and
modern
pages
yeah.
So
how
yeah
this
was.
What
I
prepared
I
see
that
I'm
out
of
time,
so
yeah
I
just
wanted
to
show
you
this
I
have
prepared
to
show
you
also
and
the
code,
but
I
think
we
don't
won't
have
time
for
this.
Just
one
few
sentences
when
I
am
referring
to
SharePoint
Dean's
add-ins
I
mean
using
this
visual
studio
project
template
so
yeah.
A
B
So
once
you
have
access
to
this
dashboard
from
here,
you
are
able
to
create
your
component
and
it
is
pretty
straightforward.
So
once
you
develop
your
ad
in
your
package,
you
came
here,
you
upload
it
and
then
you
are
waiting
five
days
around
for
the
Microsoft
teams
to
give
you
a
message
whether
you
have
passed
all
tests
or
not,
for
example,
the
adding
that
I
showed
you
with
this
teaching
bubble.
B
It
fails
the
validation-
and
here
is
what
I
received
I
received
this
PDF,
and
there
was
explanation
about
I
felt
here,
so
this
sentences
means
that
I
cannot
deploy
anything
that
is
outside
of
the
SharePoint
adding
models
and
unfortunately,
SharePoint
framework
was
not
here.
Originally
I
thought
that
this
also
handles
SharePoint
framework,
but
not
and
just
directly,
to
answer
your
question.
For
me,
the
whole
process
of
month
of
submission
is
easy,
so
once
we
get
here,
we
upload
our
package.
B
A
Time,
I'm
just
gonna,
move
back
on
the
slide,
so
we
can
close
up,
but
what
I
am
doing
that
we
can
I
take
again
few
extra
minutes
or
even
err,
so
just
a
quick
notes
on
the
on
the
SharePoint
framework.
So
from
my
engineering,
so
sides
are
good,
my
engineering
hat
on,
and
so
we
are
absolutely
looking
into
having
support
for
AB
source
for
SharePoint
framework
components
now
and
how
it
will
exactly
look
like
how
the
license
and
everything
else
will
look
like.
That's
still
yet
to
be
decided
completely.
A
We
had
a
open
position
in
our
team
so
out.
My
team
is
responsible
of
SharePoint
framework
and
and
underlying
technologies
and
api's
and
everything
else.
So
in
RPM
team
we
had
a
open
petition,
which
was
actually
now
filled
like
last
week
and
we
can
finally
start
slightly
scaling.
We've
been
having
a
scalability
problem
of
getting
things
moving
and,
and
we
know
that
the
store
and
observes
is
super
important.
Most
likely-
and
this
is
don't
hold
me
accountable
of
this
one
yet
most
likely.
A
But
we
want
you
to
be
able
to
easily
boot
your
ship
on
the
framework
solutions
due
to
apps
or
app
source
and
then
promote
them
and
then
potentially
come
off
with
a
few
recommended
options
for
licensing,
but
not
really
take
any
cuts
from
the
sales,
and
all
of
that,
so
that's
not
really
in
our
intention,
but
yet
to
be
fully
locked
down
yet
to
be
fully
design
it.
It's
an
ongoing
discussion,
I'm
going
to
design
discussion,
so
don't
hold
me
accountable
of
this
really
early
speculation.
A
How
it
will
look
like
definitely
won't
be
I
can
actually
spill
the
beans
on
this
one
won't
be
explained
or
announced
in
SPC.
So
that's
not
going
to
happen
within
few
weeks.
We
definitely
will
have
more
news
ignite.
Will
it
be
available
by
ignite
I
would
say
highly
unlikely,
but
we'll
see,
but
it's
definitely
in
our
radar
to
put
some
resources
on
cool
Thank,
You
Bert.
Thank
you,
Tim
Joe.
This
is
actually
really
great
refresh,
also
on
the
adding
model
and
the
possibilities
on
that
in
model
and
immediately.
A
We
know
that
there's
a
massive
amount
of
opportunities
when
we
open
up
the
store
and
app
source
for
SharePoint
framework
solutions
and
even
more
within
week
or
two
when
we
announced
some
additional
core
stuff.
So
this
really
cool
stuff
coming
and
stay
tuned
and
watch
what
we
announced
in
a
social
media
and
join
on
next
Thursday's.
A
SharePoint
framework
community
call
we'll
walk
through
other
stuff
there
as
well.
We
actually
have
the
monthly
community
color
next
Tuesday
as
well,
where
we
work
through
what
we
have
released
within
the
last
month.
A
We
kind
of
talked
about
new
provisioning
schema
support.
We
cannot
talk
about
provisioning
engine
support
and
we
kind
of
talk
about
what
else.
What
else
there
was
one
more
thing,
but
there's
a
few
demos
on
that
one
as
well.
But
what?
If
you
community
course,
everything
will
be
recorded
available
in
the
YouTube
channel
within
24
hours,
but
thank
you
for
the
demos.
Thank
you
for
watching.
Thank
you
for
your
feedback.
Please
keep
the
feedback
and
input
coming
in
the
future
as
well.
Thank
you.
Bye,
bye,.