►
From YouTube: SharePoint Dev Weekly - Episode 21 - 8th of January 2019
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.
If you want your article or sample mentioned, please use #SPDevWeekly hashtag on Twitter for letting us know.
This video was recorded on Monday 7th of January 2019.
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
Here
we
go
episode:
21
ship
under
weekly,
our
director
chief,
deeper,
of
course,
who
else
would
be
directing
this
he's
responsible
of
everything?
So
it's
January
7th
Monday.
This
is
the
first
real
working
day
after
Christmas
right
for
you
for
some
people.
Yes,
yes,
yes,
you've
been.
Actually
you
were
away
for
well
away,
you're,
not
working.
B
A
A
B
A
B
B
A
Right
sure
it's
we
are
looking
into
now
that
it's
Monday
after
the
holiday
break,
we'll
probably
gradually
get
moving
again
on
the
core
dotnet
standard
versions
of
the
season
and
then
that's
on
craig's,
the
core
version
of
PowerShell,
which
then
means
that
power
sure
can
be
executed
outside
of
the
of
the
windows.
But
how
many
Mac
people
are
actually
using
PowerShell
core
I,
don't
know
so.
B
A
B
B
A
B
Oh
yeah,
so
so
in
CLI.
What
we
do
is
that
every
single
time
you
run
a
command.
We
will
pick
up
like
the
command
that
that
you
used
and
which
options
you
use,
not
the
values
like.
If
you
use
a
URL,
we
don't
keep
track
of
your
own
because
like
for
us,
the
Euro
doesn't
make
any
sense
like.
There
is
no
point
for
us
to
track
track,
URLs
or
track
things
like
item
names
or
file
names.
There
is
we
don't?
We
are
not
interested
in
that.
B
B
A
B
A
B
A
Be
fair
just
not
enough
that
people
are
freaking
out
and
oh
I'm,
not
using
BMP
polish
of
them
at
all?
No,
no,
that's
not
what
it
actually
means.
So
certain
scenarios.
Maybe
the
memory,
has
an
impact
on
those
scenarios.
Might
one
have
a
look
on
the
CLI,
but
if
you're
familiar
with
PowerShell,
you
can
use
the
PowerShell.
Please.
B
A
So,
on
my
side,
what
we
did
last
week
or
what
I
did
last
week,
we
released
a
new
version
of
the
on-premises
nougats.
Finally,
so
seasonal
cuts
for
2013
29
2016.
There
is
a
no
nation
in
2019
which
I'm
still
investigating.
What's
the
right
solution
to
fix
that
I
have
no
idea
how
all
of
this
has
fallen
on
my
table,
I
just
keep
on
managing
them,
so
I,
don't
it
should
be.
Somebody
else
is
actually
taking
care
of
it.
A
No
can
do,
and
so
that
went
live
on
Friday
and
then
obviously
we're
working
on
the
provisioning.
So
we're
still
getting
that
one
out,
hopefully
soon,
there's
some
legal
stuff
with
which
I
need
to
still
tackle
plenty
of
other
topics
as
well:
prepping,
actually
prepping,
tomorrow's
and
today's.
If
you're
watching
this
on
Tuesday
or,
if
you're,
watching
this
after
Tuesday,
then
yesterday,
so
the
previous
community
call
and
and
making
sure
that
those
are
going
fine
as
well,
and
we
actually
have
a
pretty
cool
call
coming
up
on
now
on
Tuesday
the
January
monthly
communica.
A
B
A
All
coming
in
and
I'm
talking
about
the
latest
on
printing
provisioning
and
experience
is
what's
coming
and
what's
the
latest
on
that
topic,
so
that
should
be
pretty
cool
life
and
then
plenty
of
other
stuff
as
well.
But
that's
a
that's
that's
how
it
is,
and
now
let's
actually
jump
on
the
on
the
topics,
and
so
we
we
actually
get
on
them
as
well.
There
was
actually
quite
a
lot
of
items
again
last
week,
even
though
it
was
a
holiday
week
which
is
kind
of
cool.
A
So,
first
of
all,
if
you're
interested
on
the
on
the
new
nuggets
for
on-premises
and
on-premises
is
quite
big
still
in
SharePoint.
So
quite
often
we
in
these
calls
we
always
talk
about
SharePoint
framework
and
the
cloud
and
everything
else.
And
then
we
forget
about
the
fact
that
well
there's
a
lot
of
people
who
are
still
in
on-premises,
so
we
as
I'm
sure
pond
engineering
we
do
not
need
should
not
forget
about
these
people,
because
we
need
to
help
them
to
be
successful
in
there
as
well.
A
And
now
this
has
been
a
long
overdue,
but
basically
what
we
did
was
we
updated
the
SharePoint,
2013
SharePoint
2016,
look
at
packages
matching
the
May
2018
see
us,
and
this
is
something
this
used
to
be.
Let
me
actually
open
that
one,
for
example,
SharePoint
20
2013
and
look
at
used
to
be
baseline
on
a
may
2015
if
I'm
gonna
well,
but
this
correctly,
so
it
was
really
old
and
the
question
might
be
why
why
are
using
such
an
alteration
of
a
same
place?
A
A
B
A
Long
story
we're
not
going
to
deep
dive
on
that
one,
but
basically
it
was
started
there
in
2013
will
look
like
and
it
there
as
a
new
capability
in
2013.
2016
was
already
out,
and
people
forget
about
backporting
the
same
change
to
2016,
and
these
things
do
happen,
sir,
but
anyway
quite
a
lot
of
new
properties
which
might
be
useful
on
2016
site
by
the
way.
A
This
actually
kind
of
interesting
was
a
surprise
for
me
as
well,
so
because
it's
always
interesting
to
see
what
are
we
back
port,
so
the
the
records
management
stuff
in
season
is
in
2016
season,
so
these
were
added
in
SharePoint
Online
at
some
point
and
then
when
and
they
apparently
were
backwater
in
2016
as
well,
which
is
cool.
So,
if
you're
looking
into
making
that
happen,
so
you're
able
to
use
season
to
create
records
in
SharePoint
when
I
16.4
and
that's
actually
critical
anyway.
So
that's
for
the
on
premises.
A
B
A
Sir,
not
a
massive
deal
but
like
right
now.
This
is
owning
your
Kitsap
repo,
and
we
already
talked
about
the
fact
that
when
yes,
we'll
move
it
into
the
same
shape
once
our
targets
repo,
so
it's
a
one
location
what
people
can
find
the
latest
on
shipments,
knotting
everything
yeah
everything
is
it
PowerShell?
Is
it
CLI?
Is
it
whatever
assets?
Everything
will
be
in
here?
We
will
be
working
on
this
one
starting
this
week
quite
significantly
as
well.
A
We
need
to
update
some
of
the
areas
in
here,
make
it
sure
that
it's
working
properly
in
provisioning
engine
and
all
of
that,
so
it
should
be
fine.
The
1.4
version
of
starter
kit
actually
was
released
in
December,
so
there
was
a
changes.
We
are
credit
it
to
be
1.71
if
I
remember
correctly
or
mark
or
other
well.
Actually,
we
didn't
community
date,
but
yeah.
Okay,
that's
how
it
works
with
this
awesome,
that's
how
the
open-source
works
now,
I'm.
Moving
on
on
other
things
that
this
one
was
really
cool.
A
So
this
one
is
from
multiple
corner,
so
mutters
gonna
do
actually
live
demo.
This
one
in
one
of
the
upcoming
special
interest
group
cause
actually
this
Thursday
upcoming
Thursday,
but
this
is
a
really
cool
story
around
using
out-of-the-box,
quick
chart
reports
and
to
be
boosting
them
with
flow
which
is
like
okay.
What
does
that
mean?
Well,
what
it
means
is
that
they're
using
the
out-of-the-box
chart
what
part
you're
pinpointing
that
to
a
list
called
opportunities
and
from
there
you're
then
raising
the
data
which
is
kind
of
okay
cool.
But
we
do
you
get
the
data.
A
Well,
that's
the
interesting
part
here
we
can
actually,
in
this
case,
mattias
building
a
story
where,
though
there
is
an
opportunities
functionality
in
Dynamics.
So
what
if
we
would
just
use
the
flow
to
replicate
the
relevant
data
from
Dynamics
365
did
a
SharePoint
for
a
reporting
perspective,
and
then
you
can
actually
have
a
nice
data
and
a
weekly
updates
on
the
opportunities
which
are
getting
at
it
on
the
dynamics.
Trees
is
defined
and
the
amount
of
code
needed
is
basically
a
zero,
but
somebody
might
say
that
this
is
toad
coding.
A
A
Absolutely
absolutely
it's
it's
it's
interesting
how
how
what
you
can
do
with
Microsoft
flow,
it's
just
insanely
powerful,
which
also
changes.
If
you
think
about
SharePoint
deaf
as
a
story
and
and
and
I
say,
let's
say
skill,
it
does
change
what
we
need
to
be
capable
of
doing
right
because,
yes,
lo
can
take
care
of
some
of
the
middle,
were
middleware
section
and
integrations
and
like
on
behalf
of
us,
so
we
don't
necessarily
need
to
write.
The
code
again
depends
on
a
scenario.
A
A
So
this
one
is
from
workman
it's
a
really
great
article
related
on
working
with
application
permission,
so
basically
having
a
demon
application
running
somewhere
on
behalf
of
not
not
in
the
context
of
user.
In
the
context
of
the
application
in
SharePoint,
Online
Animax
of
craft
and
there's
there's
a
few
different
options.
A
How
you
can
register
your
client
ID
or
do
you
need
a
client,
ID
and
secret,
or
do
you
use
certificate
and
what's
actually
available
there,
and
this
is
really
around
the
fact
that
how
do
you
have
a
rich
history
application
to
a
resistor
that
using
SharePoint
adding
registration,
which
is
the
cick
way
of
doing
stuff,
using
what?
How
would
I
put
it
using
the
ACS
which
wasn't
an
ACS?
That's
the
right
way
of
putting
that.
B
A
We
called
the
ship
went
down
in
registration
model
as
an
ACS
easiest
registration
model
right
like
three
years
ago,
but
then
ACS
was
deprecated
and
shut
down
on
November,
but
the
ship
went.
Adding
model
registration
would
under
still
continue
and
it's
fully
supported.
So
it
wasn't
an
ACS.
It
was
I,
don't
know
what
we
should
shut
up.
The
Colin.
A
B
A
A
But
it's
great
that
people
are
sharing
this
because
if
somebody
else
is
actually
running
into
this
like
he
is
writing
here,
as
well
as
the
the
most
of
all
Googlers
who
who
experience
unexpected
issues
which
happened
framework,
so
it's
good
to
have
the
notes
available.
So,
if
you're
running
in
to
invite
SharePoint
that
packets,
bad
part,
you
are,
is
not
valid,
for
rules
defined
in
open
brackets
Convention
specification
and
might
be
the
fact
that
you
have
spaces
in
your
shipment
favorite
project.
A
That's
apparently
not
working
properly,
I,
never
thought
about
this
one,
but
it's
its
gift.
Maybe
we
should
actually
fix
that
in
engineering
yeah
and
the
second
thing
was
the
build
failed
because
task
wrote
outputs
STD,
they
are
exiting
with
an
exit
code.
One,
that's
super
useful
description.
Isn't
it
well.
B
No,
no
especially
so
there
are
two
things
like
if
you
look
at
the
image
below
that
use,
consider
error
all
the
way
down,
but
actually
the
warnings
are
above
and
and
the
reason
so
so.
This
is
a
known
issue
that
we
discussed
with
Pete
on
github
a
while
back
already
yeah,
and
the
reason
for
that
is
that
this
will
only
fail
a
ship
build.
Why?
Because
during
dev
and
and
that
was
the
reasoning,
Pete
gave
us
that
that
the
product
team
used
behind
it
actually
intentionally.
B
Do
it
that
way
it's
like
in
during
dev,
when
you
do
a
debug
build,
you
will
see
a
warning,
but
that
warning
will
not
fail
a
build
because
I
mean
you're
doing
def.
You
want
to
do
your
stuff
and
then,
when
you
ship
like,
if
that
bill
was
still
didn't
fail,
despite
the
warning
world-
and
you
would
ignore
the
warning-
we
just
ship
the
thing
and
the
warning:
is
it
there
or
nothing
right?
The
warning
is
there
with
purpose,
which
is
why
on
ship
build,
it
will
fail
exactly
this
right.
B
A
And
absolutely
make
sense,
absolutely
make
sense
and
searches
article
explaining
what
station,
how
the
result
that
and
and
all
of
that
so
modify
the
code
and
all
of
that
school
if
we
effects
ListView
command
set
and
a
panel
from
ionic
really
good
stuff
actually,
because
quite
often
and
malarkey
is
writing
here
on
the
article
as
that.
Well,
you
could
use
a
dialogue
for
modifying
or
editing
something,
but
what
if
the
dialogue
does
and
the
size
of
the
Dalek
isn't
suitable
or
you
need
to
have
more
information
or
you
need
to
have
flow?
A
Maybe
it
makes
more
sense
to
have
a
custom
panel
and
their
side
of
the
books
with
parts
which
are
using
custom
panel
as
well
before,
unless
I'm
completely
mistaken,
I
think
there
is
right,
I,
don't
know,
I
don't
know
either
most
like
somebody
from
our
decent
organization
will
come
back
saying
we'll
see
so.
But
basically
the
whole
point
is:
is
that
ok,
how
do
I
start
a
left
side
panel?
And
how
do
I
implement
the
last
left
side
panel
in
a
way
that.
A
Sorry
right
side,
the
other
left,
the
other
left,
yes
and
the
other
left
side
panel
and
put
it
it's
visible
when
I'm
clicking
and
open
and
in
its
editor.
So
basically
let
me
zoom
here
clicking
to
open
an
editor.
It
will
then
open
up
the
look
the
right
side
panel,
but
if
I'm
turning
on
this
side,
then
it's
a
let
it
still
right.
A
It's
always
right.
Yes,
but
it
opens
up
the
panel,
then
Danity
variable
to
modify
things
and
save
and
whatever
there's
a
button
actually
doesn't
and
continue
from
there
really
good
stuff.
Jannik
is
gonna.
Do
a
live
demo
on
this
one
in
the
car
coming
community
calls,
although
so
that
should
be
a
really
cool
moving
on
on
to
things
from
Dennis.
So
this
is
a
nice
kind
of
a
story
and
a
video
related
on
the
Google
Analytics.
So
writing
an
application.
A
Customizer
and
then
you
need
to
have
Google
Analytics
on
the
site,
are
using
Google
Analytics
to
understand
how
people
are
using
your
portal
as
an
example,
where
do
you
store
the
Google
Analytics
tracking
code
as
a
where
is
the
unique
identifier
stored
and-
and
this
is
basically
a
story
around
the
fact
that
we're
using
the
tenon
wide
extensions
list
for
the
application
customizes
to
store
dots,
and
so
my
story
on
how
to
make
that
happen
and
how
things
should
be
working
from
that
perspective?
Maybe
actually
that's
the
element
and
there
we
go.
A
There
is
the
property,
that's
yeah,
that's
the
key
and
then
we're
loading
the
key
and
using
that
key.
Basically,
when
we
use
the
Google
Analytics
making
sure
that
we're
getting
proper
analytics
entries
now,
this
is
absolutely
100%.
Suitable
solution
on
one
alternative
could
be
also
the
channel
properties
which
would
be
then
set
in
the
in
the
tenant
level.
So
again
matter
of
a
preference
for
this.
B
The
other
hand
I
mean
if
you,
if
the
portal
on
which
you
want
to
use
it,
consists
not
only
of
the
modern
size
but
also
learn
the
classic
ice
egg
experiences.
Then
you
would
not
be
able
to
use
this
approach
because
that
won't
only
work
or
work
on
modern.
So
you
would
need
to
keep
the
or
keep
track
of
the
code
twice.
Yeah,
alright,.
A
Back
basically,
in
a
tenant
level,
then
that's
available
using
REST
API
is
for
both
Eric
and
so
yep,
which
makes
sense
now
again
debatable.
So
there's
multiple
design
options.
It
really
depends
again
on
how
the
customization
is
being
used.
What
do
we
need
to
track?
Are
you
using
classic
at
all?
Can
we
disable
classic
completely
and
whatever
so,
multiple
multiple
discussion
point
yep
now
and
then
the
final
piece
from
here
from
Janos
standing
ship
won't
let
users
to
get
a
simple
link
to
a
document
or
a
folder.
A
If
you
used
out-of-the-box
copy
link
functionality,
let
me
zoom
in
you
get
that
this
sharing
links
which
are
relatively
complex,
and
it's
like
well
what's
happening
here.
Where
is
it
actually
pointing
and
well
to
be
fair?
Some
of
these
are,
and
they
have
access
tokens
inside
of
them,
you're
able
to
share
that
to
anybody
in
your
company
and
they
will
get
access
and
all
of
that
which
is
super
cool
functionality.
A
Now,
if
you
would,
however,
want
to
have
a
simple
URL,
just
pointing
to
a
site
library,
path,
folder
or
a
document,
how
would
you
actually
do
that?
Well,
Jonas
is
basically,
then
showing
here
how
to
build
an
extension.
Espy
effects
list
view
command,
set
and
get
a
button
on
a
list
with
this
copy
direct
link
and
then
show
a
panel
and
you're
able
to
copy
down
so
cool,
simple,
clean,
and
this
could
be
a
potentially
pushed
directly
to
all
of
the
document.
A
Libraries
in
the
tenant
use
in
the
tavern
or
tenant
my
deployment
of
extensions
capabilities,
so
neat
neat
sample
and
obviously
solution
is
available
in
github
as
well
so
perfect
and
already
having
discussions
with
your
nurse.
That's
able
to
a
live
demo
on
this
one
as
well
in
there
some
of
the
community
calls
so
because
it's
always
nice
to
see
and
have
that
discussion
on.
What
did
you
learn
about
writing
this
solution?
What
was
the
challenge
is?
A
B
A
Us
know,
and
you
raise
use
the
hashtag
SP
dev
weekly
in
the
Twitter.
You
can
just
click
post
and
normal
tweets
and
then,
for
example,
reply
to
your
own
tweet,
saying
hey
by
the
way,
guys
here's
a
good
one
I
wrote
this
one,
so
we
would
actually
know
about
what
you've
written
in,
because
it's
surprisingly,
actually
time
consuming
trying
to
give
up
on
what
everybody
is
doing
across
the
world.
It's
basically
impossible
so
help
us
to
help.
You
write
exactly
helped
me
to
help
what
was
yes.
B
A
B
B
B
A
A
B
B
You
probably
won't
you
know,
I'm
trying
to
finish
up
an
article
that
I
was
working.
I
started
working
on
already
before
Christmas
around
integrating
application,
insights,
NSP
effects
yeah,
so
that
is
already
a
work
in
progress.
I'm
sixty
seventy
percent
in
and
then
on
the
other
hand,
like,
over
the
last
few
weeks,
we've
seen
a
great
number
of
people
adding
were
self
to
CLI.
So,
even
though
you
might
be
not
seeing
work
directly
from
me,
I
will
try
to
process
PRS
and
get
them
in
whenever
they
are
Eddy
right.
B
So
so
we
always
try
to
get
new
version
of
self
CLI
every
weekend
and
then
once
a
month
month,
a
release.
So
even
though,
like
it's
feels
like
we
were
finally
getting
to
the
point
where
it
does
not
stand
or
fall
fall
fall
on
on
me.
Yeah.
There
are
a
number
of
folks
who
help
who
you
CLI,
who
help
with
the
code
issues.
B
A
A
B
A
And
I
still
yeah
that's
what
we
want
to
do
as
well,
so
making
sure
that's
that
well!
Well,
their
nose
does
really
well.
One
of
my
big
fear
is
that
nothing
what
we
do
in
B,
&
B,
should
be
dependent
on
me
right
and
that's
that's
one
of
the
men's
holidays.
What
we've
been
discussing
as
well,
because
we
never
know,
what's
going
to
happen,
you
can't
predict
the
future,
so
you
want
to
make
sure
that
whatever
you've
done
will
just
live
by
itself,
also
in
the
future.
So
yeah.
B
That
is
one,
but
also
another
thing
is
there's
scale
like
I
mean
there
are
only
so
many
hours
in
a
day
or
right,
physically
limits.
I
could
do
so
many
commands.
If
that's
the
case,
if
I
can
scale,
if
others
are
willing
to
spend
their
time
on
it,
we
can
build
so
much
more
together
correct,
but
it
cannot
be
me
like,
like
it,
wouldn't
be
fair
for
them
to
build
it
then
me
say:
like
look
at
me:
it's
mine.
A
Which
says
sharing
is
caring.
That's
the
exactly
point
why
we
built
this
together,
because
the
community
is
much
stronger
together
rather
than
competing
between
each
other
or
I
have
to
cool
off
thing.
No,
no!
No!
Let's
combine,
and
this
will
be
brilliant,
so
exactly
everybody
will
benefit
on
event,
so
this
will
be
the
let's
make
2019
the
year
of
being
nice
in
open
source.
Also,
just
a
a
note:
I'm
gonna
actually
promote
that
one.
So
now
I've
this
just
a
reminder.
B
A
Be
nice
so
because
every
now
and
then
that's
the
final
thing,
let's
close
after
that,
but
it's
it's
is
one
of
those
things.
There's
a
lot
of
people
who
contribute
on
these
things
and
well,
there's
a
lot
of
community
people
who
spend
evenings
and
days
evening
some
weekends
on
the
open
source,
stuff
and
then
every
now
and
then
you've
got
those
those
comments
and
issues.
So
it's
like
yeah.
This
doesn't
work,
yeah
yeah
sure
there
bucks,
but
you
can
actually
help
us
to
fix
that.
No,
no,
no!
That's
not
my
job!
B
A
And
the
community
who's
contributing
on
the
open
source
as
well,
so
sure
some
people
are
getting
paid
on
coordinating
the
open
source
work,
but
really
the
maturity
of
contributions
come
from
the
people
because
they
want
to
help
each
other
so
which
is
a
which
is
great.
That's.
How
would
you
anyway?
That's
a
crate
crate.
A
A
final
note,
so
thank
you
all
thanks
for
joining
once
again
for
next
one
we're
trying
to
get
a
let's
get
a
visitor
I
think
we
have
a
good
list
of
visit
candidates
for
the
next
ones
and
the
holidays
is
earnest
always
slightly
more
hard
to
schedule.
This
thing
spun
and
thank
you,
everybody
for
watching
and
please
use
the
SPD
back
at
SP,
dev
weekly
hash
tag.