►
From YouTube: SharePoint Dev Weekly - Episode 9 - 16th of October 2018
Description
SharePoint Dev Weekly is a weekly video chat where Vesa and Waldek are talking about the latest news and topics around SharePoint dev area. In this episode, Waldek was joined by Chris O'Brien (Content and Code).
If you want your article or sample mentioned, please use #SPDevWeekly hashtag in Twitter for letting us know.
This video was recorded on Monday 15th of October, 2018.
You can find more details on the weekly summary from SharePoint Dev blog from http://aka.ms/spdev-blog. More details on the SharePoint Dev community available from http://aka.ms/sppnp.
A
A
B
So
I
head
up
the
development
team
at
a
UK
partner,
called
content
encode,
and
we
do
a
lot
of
work
around
office
365
lots
of
different
angles
of
that,
whether
it's
development
projects
on
SharePoint
or
identity
and
cloud
app
security
stuff
on
the
more
platform
side
of
things.
There's
a
variety
of
teams
here
that
are
all
strong
and
I
lead
the
dev
team,
which
is
around
ten
guys.
We
generally
focus
on
office
365.
We
have
the
occasional
on-premises
sharepoint
project,
but
yeah
real
mix
of
things,
yeah
and
you're.
Also
an
MEP
right.
A
B
B
B
A
A
B
How
we
need
our
clients
needs
that
you
know
we're
trying
to
do
things
that
probably
moving
beyond
internet
and
bringing
together
bits
of
office
365.
So
you
know
everybody's
interested
in
things
that
show
teams
that
I'm
a
member
are
my
tasks
in
planner,
as
well
as
usual
things
like
my
files,
my
documents,
my
sites,
my
contacts
and
so
on
so
we're
doing
more
in
teams,
development,
so
I'm
also
planning
to
very
large
SharePoint
depth
projects,
one
for
a
legal
company
and
one
for
a
big
sort
of
tax
and
consultancy
company.
B
A
B
A
Platen
platen
clamps
at
a
firm
CLI
that
allows
you
to
manage
365
and
s.
Vfx,
we've
added
a
few
commands
there
and
then
another
thing
is,
and
we
will
also
get
back
to
that
during
our
weekly
announcement.
Is
that
C
like
it's
becoming
a
part
of
something
else
that
is
being
built,
so
that
is
also
really
cool
so
with
that
I
think
it's
a
good
moment
to
have
a
look
at
the
latest
announcements
in
the
community.
A
Let
me
show
my
screen:
I
had
a
few
links,
aligned
and
I
am
curious
about
your
opinion
on
a
few
of
them
all
right.
So
first,
the
first
thing
that
took
my
attention
was
a
suite
by
you
hoc,
khoa
bula,
who
is
one
of
the
below
guys,
and
he
says
that,
basically,
when
they
were,
they
loved
SPF
x4.
The
fact
that
I
could
that
I
can
build
it
once
and
it
works
both
on
Prem
and
online
and
classic
and
modern.
A
B
If
it's
SharePoint,
then
now
it's
generally
SPF
X
yeah,
and
so
you
know
that's
that's
great,
because
we
enjoy
building
on
the
platform.
We
involve
button
we
enjoy
what's
in
the
framework
and
how
to
connect
to
things
and
so
on.
But
obviously
the
big
thing
that
we're
really
happy
about
is
SPF
X,
webparts
running
in
team.
Soon,
all.
B
Yeah
yeah
I
guess
there
was
some
some
indications
about
it
before
then,
but
that's
great
for
us
and
I
think
great
for
many
SharePoint
developers,
because
all
those
skills
that
you've
been
busy
building
over
the
past
year
or
two
now
transfer
to
teams
and
that
becomes
a
great
canvas
for
line
of
business
applications.
Yeah.
B
That's
right,
yeah
and
you
know
I
think
anybody
that's
doing
an
Internet
these
days.
That
is
really
just
around
communications
and
news
and
content
pages.
You
know
that
they're
really
missing
out
I
think
on
what's
possible
in
office,
365
and
I.
Guess
on
this
the
thing
that
I'm
really
interested
to
see
what
happens
in
the
next
two
or
three
years
is
you
know,
as
sharepoint
and
teams
become
more
prevalent
in
their
use.
A
B
B
And
certainly
for
decisions
we
build,
you
know
we're
making
it
so
that
it's
possible
to
use
either
to
a
certain
extent.
But
you
know
there
are
sort
of
still
trade-offs
and
things
that
are
more
suited
to
one
client
rather
than
the
other.
So
I'm
really
and
should
see
how
the
industry
goes
in
the
next
two
or
three
years
and
whether
it
really
will
have
a
massive
shift
towards
teams
or
whether
there'll
be
a
mix
depending
on
the
organization
and
the
culture.
So
cool.
A
Cool
yeah
and
related
to
that
a
little
bit
the
other
week,
valo
guys,
together
with
Joanne
Kline,
released
an
e-book
that
explains
how
you
can
benefit
of
the
modern
architecture.
Overside
meaning
more
towards,
like
hobbs,
introduced
the
notion
of
more
flat
architecture
of
your
sites
and,
comparing
to
in
the
past,
we
had
subside
sublet
and
all
that.
So
what
approach
do
you
guys
use?
B
Got
some
clients
out
there
that
have
Internet's
where
they've
done
quite
a
lot
with
sub-sites
and
they
do
have
those
hierarchies
and
I
guess
the
solutions
that
we've
built
in
recent
times.
Then
they
generally
all
have
followed
the
flat
structure,
and
this
was
the
case
even
before
websites
and
so
on.
A
Do
you
guys
have
to
deal
often
with
the
case
I
think
there
was
the
one
of
the
value
props
for
Hobbes.
Is
that
when
in
a
past
you
would
build
a
hierarchy
and
then
you
have
to
move
one
site
from
one
place
to
another,
then
you
all
the
things
like
poking
links,
documents
not
being
there
people
not
being
able
to
find
where
things
are
anymore,
whereas
with
topsides.
A
B
Yeah,
absolutely
and
I
guess
the
way
that
our
solutions
have
soft
sidestepped.
That
problem
around
moving
things
around
is
that
it's
always
being
the
logical
structure,
that's
built
on
tagging
and
metadata.
So
it's
always
been
easy
for
us
to.
You
know,
restructure
things
and
inevitably
companies
change
how
they
won't
want
to
express
their
information.
Maybe
it's
a
reorg
or
something
else.
You
know
and
I
think
for
years
now,
we've
always
built
Internet's
that
are
okay
with
that
and
aligned
with
those
principles.
B
A
All
right,
another
thing
that
we
have
here
is
another
summary
post
from
David
who
does
that
every
single
time
PNP
was
something
out.
He
basically
does
assumer
e
with
images,
and
he
does
it
like.
Every
single
time
is
within
minutes,
like
the
recording
is
done
and
within
ministers
sue
Murray
with
all
the
key
messages,
key
slides
already,
basically
me
making
it
if
you
are
on
the
road
or
you're
busy,
and
you
couldn't
join
the
call,
it's
a
really
great
way
to
get
through
the
latest
announcements
and
stay
up
to
date.
Yeah.
A
A
B
A
In
our
analysis,
that
we
have
here
is
from
Tony
Phillips,
who
writes
about
how
to
create
a
Microsoft
SharePoint
web
part
to
show
recent
onedrive
files
and
just
goes
through
the
step-by-step
process
of
how
you
would
create
a
web
part
connect
to
graph
and
from
the
looks
of
it
it's
still
on
version.
One
point
four
point:
one
which
is
the
old
one
and
if
you
would
start
from
one
point
6.0
there
is
a
version
where
connection
to
the
Microsoft
graph
is
in
GA,
meaning
that's
the
officially
supported
way.
A
There
is
a
bunch
of
bugs
that
where
were
available
or
where
presents
in
a
past,
and
now
it's
not
entire
pics.
So
if
you,
if
you
work
with
SPF
X
and
you
do
anything
with
the
Microsoft
graph
or
even
a
ad
in
general,
we
recommend
that
you
update
to
at
least
once
is
6o,
because
that's
basically
the
baseline
for
everything
about
among
those
these
abilities.
A
B
Exactly-
and
we
just
seem
to
find
in
my
team
that
we're
using
functions
a
lot
and
generally
it's
for
connecting
to
the
graph
or
maybe
connecting
to
some
bespoke
system,
but
we
seem
to
be
plugging
them
into
all
sorts
of
different
things,
whether
it's
SPF
X
or
whether
it's
power,
apps
or
flow,
or
maybe
site,
designs
and
side
provisioning,
so
yeah,
it's
a
very
common
building
block
for
us,
but
yeah
those
those
key
technologies
of
SPF
X.
The
graph
has
your
functions.
Basically,
what
we're
doing
all
the
time
and.
B
That's
right,
so
it's
great
that
everything
is
baked
into
SPF
X
now,
and
things
aren't
in
beta
anymore,
and
you
know
we
can
just
do
those
easy
connections
rather
than
having
to
go
off
and
you
know,
use
a
dowel
or
something
to
get
a
token
ourselves
things.
Oh
yeah
things
are
much
nicer
for
a
sharepoint
there,
absolutely.
A
Absolutely
cool
announcement
that
we
have
or
announcement
a
post
is
from
Nandina
not
much
on,
and
it's
about
deploying
your
SPF
x
webparts
to
library
right.
So
when
you
build
a
web
part
or
an
extension,
there
are
a
number
of
ways
in
which
you
or
a
number
of
locations
with
you.
You
can
deploy
it.
You
can
deploy
it
to
library
CDN
or
to
some
other
location
like
as
your
blog
right,
and
this
article
goes
about
the
case
when
you
would
want
to
deploy
it
to
library,
question
which
location.
Do
you
guys
choose.
A
B
A
A
I
guess
I,
so
there
are
two
either
right.
This
one
is
the
bundle
which
basically
means
that
there
are
ways
to,
to
some
degree
reverse
engineer
the
code
mm-hm
and,
and
even
even
without
it,
you'll
be
able
to
run
it
in
your
own
tenon
and
imagine
that
I
would
build
a
web
part
that
shows
stocks.
Then
you
would
be
able
to
reuse
that
in
your
own
environment,
because
they're,
just
a
public
API
right.
B
A
So
unless
there
are
some
specific
things
like
in
properties,
you
would
have
to
specify
the
API
key
without
it,
you
cannot
use
that
I
mean
on
that.
You
would
be
able
to
benefit
all
of
that.
But
another
thing
that
I
wonder
about
is
specifically
for
this
case.
Is
that
if
you
look
at
how
assets
are
being
served
from
SBO,
there
isn't
really
like
things
like,
for
example,
the
long
expiry
time
more.
B
A
Think
that
by
default
is
not
even
http/2,
and
there
are
some
other
things
as
well,
for
which
you
might
say
that
if
you
really
want
to
optimize
it
for
performance,
you
should
go
at
least
with
the
CDN,
but
maybe
with
something
else
that
you
control
yourself
right,
because
if
you
build
a
web
part,
why
should
the
user
download
it
every
day?
Again
it's
not
yeah.
It's
not
like
the
web
part
will
change
every
day
right.
B
A
And
our
one
is
tweed
by
stephan
power
and
that's
actually
ties
into
the
thing
that
that
I
that
I'm
met
first
is
about
CLI
being
a
part
of
something
else
that
and
that
that
we
built
at
PMP.
So
there
is
the
notion
of
the
PNP
community
SPF
edge
and
then
crater,
which
you
could
say,
extend
the
generator
that
we
have
available
out
of
the
box
right.
A
So
out
of
the
box,
you
can
create
your
project
that
uses
knockout
react
or
our
no
library
at
all
and
the
community
won't
extend
that
with
support
for
if
I
recall,
correctly
view
and
now
angular
elements.
So
that's
your
available
or
coming
and
now
the
other
thing
that
it
does
is
that
if
you
would
run
it
so
it's
currently
based
on
SharePoint
framework
11.6
and
imagine
that
you
would
run
it
to
add
something
to
project
that
you
already
have
and
the
project
was
built
on
SPF
x,
1.5
mm.
A
So
we
already
have
in
CLI
the
notion
of
the
ability
to
upgrade
the
project
from
one
version
to
another.
Now
the
same
thing
is
available
here.
So
if
you
run
generator
to
add
something
new
to
project
you've
already
had
that
you've
build
in
a
past,
generator
will
warn
you
to
say,
like
operated
at
first,
because
I
depend
on
new
things
that
are
not
available
to
you,
and
you
can
then
streamline
that
directly.
From
that
experience,
you
don't
need
to
go
to
some
other
tool
to
run
something
else.
That's.
B
Nice
yeah
because
I
mean
I
think
as
the
new
releases
of
SPF
X
come
out,
I
think
it's
really
common
for
you
to
go
back
to
some
existing
code,
and
you
know
you
find
that
you
now
a
new
version
of
SPF
X.
So
you
have
to
decide
whether
to
do
the
upgrade
at
this
point.
I
think
it's
really
nice.
If
it's
built
into
the
generator
yeah.
A
B
A
And
then
another
one
we
have
is
another
blog
post
from
Corey
Ross
about
fixing
horizontal
scrolling
in
your
details
list
using
scrollable
pain
and
sticky.
So
this
is
like
a
really
edge
case.
If
you
have
too
much
info
to
show
on
a
page
both
in
height
and
width,
you
can
build
stuff
in
with
office
life
every
react,
but
the
thing
is:
there's
a
quirk
where
you
have
20
you
need
when
you
have
too
many
rows
to
fit
in
your
container.
A
You
want
to
be
able
to
scroll
that
with
with
the
header
being
fixed,
but
the
end,
if,
if
the
columns
don't
fit
in
with,
how
do
you
reach
them
right?
Because
the
header
is
fixed,
so
you're
gonna
scroll
that
so
so
Corey
gives
tips
like
how
to
work
around
it
using
the
things
available
for
us
and
then
finally,
the
rest
one
is
is
a
kind
of
gem
so
and
that's
from
Sergei
Sergei.
A
B
A
Work
a
lot
with
wrist
with
rest
in
SharePoint,
and
the
one
thing
that
you
do
is
is
I
mean
the
Ducks
aren't
really
that
great
there's
a
lot
of
room
improvement.
So
what
I
tend
to
do
a
lot
is
that
I
would
go
to
underscore
API,
slash,
dollar
and
then
data
to
get
the
latest
list
of
what
is
available
in
rest,
and
he
does
exactly
the
same.
Only
he
build
a
UI
around
it.
So
in
here
imagine
that
you
want
to
see
things
related
to
hub
size.
A
You
say
hub
it's
filters
down
and
therefore
each
one
you
can
click
and
you
can
see
the
methods
a
call
official
Docs.
If
any
so
so
we
can
explore
all
the
methods
pelas
what's
available,
what
is
supposed
to
be
passed
so
kind
of
an
easier
way
to
go
through
the
really
huge
XML
that
you
would
get
otherwise
in
browser
mm-hmm.
B
That
is
nice.
I
mean
that
REST
API
has
always
been
fairly
easy
to
work
for
simple
operations
and
guess,
but
as
soon
as
I
lay
a
few
posts
and
you
need
to
pass
some
complex
data
structure
and
it's
kind
of
different
in
every
every
particular
part
of
the
API
yeah,
it
seems
like
this
are
really
helpful.
Yeah.
B
Right,
if
I
could
pick
only
one,
it
would
be
the
sharepoint
team's
integration.
Ok,
so
the
ability
to
run
an
SPF
x
web
part
in
teams
tabs
and
now
that
we've
got
that
whole
power.
Is
that
the
canvas,
and
also
that
flip
integration,
of
basically
being
able
to
have
teams
solutions
that
are
basically
hosted
in
sharepoint
and
running
from
there.
So
I
think
this
is
really
powerful
and
really
come
forward
to
making
more
use
all.
A
B
A
B
A
Yeah,
it's
like
the
last
thing
you
want
to
do
as
as
a
user
to
have
to
think.
Okay
I've
know
I've
seen
that
was
it
in
Yammer.
Was
it
in
teams?
Was
it
in
SharePoint
we're
in
SharePoint
and
onedrive?
Maybe
there's
like
you
start
thinking
about
and
not
like
being
able
to
be
reward
like
finding
the
things
you
need
to
have
for
your
job
right.
B
Yeah
exactly
and
you
know
we
need
to
get
away
from
knowledge
workers
spending
so
much
time.
Finding
things
I
mean
we've
been
talking
about
that
had
year,
isn't
great
that
we've
now
got
some
kind
of
unified
search,
I
guess
other
things
as
well
devs.
You
know
some
nice
things,
they're
improved
experience
for
ad
out
registrations
that
you
know
it's
been
talked
around
for
a
long
time
all
the
things
in
graph
that
are
now
in
ng,
a
rep
and
preview.
You
know
yeah
some
great
set
of
enhancements,
I,
think
and.
B
So
far
we
were
talking
the
other
day
in
the
office
about
the
ease
of
isolated
web
part
approach,
I
like
being
able
to
do
something
iframe
like
which
is
giving
me
something
secure
in
the
page,
because
that's
obviously
a
topic
that
you
and
I
have
spoken
about
in
the
past
when
you've
got
some
component
on
the
page,
that's
dealing
with
sensitive
data
and
the
fact
that,
right
now,
if
you
don't
do
anything
in
particular
than
everything
else
on
the
page,
can
access
that
data
as
well.
Absolutely.
A
A
A
B
A
B
A
Then
they
don't
realize
like
okay,
but
you
just
added
a
third-party
unvetted
script
to
the
same
environment,
where
you
stole
your
story
or
HR
information,
personnel,
information,
confidential
projects
and
if
CEO
is
the
is
the
person
who
comes
to
that
page
and
she
and
he
or
she
can
do
anything
across
the
internet
whoa.
You
might
have
an
issue
absolutely.
B
You
know
that
reminds
me
just
recently:
I
did
a
solution
review
and
a
code
review
from
an
organization
that
came
to
us.
They'd
had
an
internet
built
in
office
365
by
by
somebody
else,
and
I
was
amazed
to
find
some
of
the
techniques
used
like
they
were
basically
looking
up
sensitive
data
from
box
comm,
the
HR
system
called
Solaris
and
in
all
cases
what
was
happening
is
it
was
being
routed
through
an
anonymous
third-party
service
on
the
internet.
That
was
this,
be
just
a
developer
convenience
that
you
might
using
dev
and
usually.