►
From YouTube: SharePoint Dev Weekly - Episode 40 - 21st of May 2019
Description
SharePoint Dev Weekly is a weekly video chat where Vesa and Waldek are talking about the latest news and topics around the SharePoint dev area. This time they were joined by Simon Ågren (Sogeti) for a chat and article coverage.
If you want your article or sample mentioned, please use the #SPDevWeekly hashtag on Twitter for letting us know.
This video was recorded on Friday 18th of May 2019.
You can find more details on the weekly summary from the SharePoint Dev blog from http://aka.ms/spdev-blog. More details on the SharePoint Dev community available from http://aka.ms/sppnp.
A
Welcome
this
is
chef
and
a
weekly.
Take
sorry
episode.
40
take
two
actually
because
we're
talking
like
50
minutes,
and
then
we
realize
that
the
recording
isn't
working.
That's
really
so,
let's
jump
on
the
point
where
we
were
banned.
We
realize
that's
recording
us,
but
no
sorry,
now,
let's
see
when
we
get
back
and
what
forget
we
need
to
repeat,
but
it
is
17th
of
May.
It
is
Friday
and
day
before.
B
B
A
A
A
A
They
made
a
joke,
so
they
actually
dive
in
and
they
booed
a
statue
of
the
Paavo
Nurmi,
who
is
a
Finnish
runner
on
the
front
of
the
boat
so
when
they
they
actually
took
this
boat
up
from
like
1600,
they
will
say:
that's
your
famous
runner
on
on
the
front,
it's
like
really,
but
but
a
good
cute
practical
joke.
If
nothing
else
finish,.
C
A
Well,
yeah:
we
we!
Actually
we
didn't
talk
about
this
one
in
the
first
recording
but
Finland's
kind
of
a
considered
Sweden
as
the
big
product.
So
nothing
the
way
the
big
brother
series,
but
rather
in
the
way
of
their
kind
of
a
friends
we
get
along,
but
we
see
them
as
the
country
which
were
kind
of
a
following
and
because
they're
bigger,
there's
more
population
and
all
of
that,
so
so,
especially
in
the
past
that
I
think
so
and
we're
anyway,
a
smaller
country.
So
Sweden
is
just
slightly
bigger
than
in
Scandinavia.
We
didn't.
A
B
Yeah
actually,
my
first
encounter
was
like
five
years
ago,
which
are
point
and
I
ended
up
in
a
classroom
for
days.
We'd
weighed
their
urban,
so
I
was
like
okay,
so
you
have
never
worked
with
check.
One
I'm
gonna
teach
you
SharePoint
in
four
days.
This
is
not.
We
would
like
to
know
which,
of
course,
you
can
t
just
SharePoint
in
four
days.
We
know
everything.
C
B
A
Collection,
we
have
a
massive
massive
package
with
SharePoint.
Do
the
historical
things
because
it
is
I,
think
Jeff
deeper
was
part
of
the
original
team,
creating
a
Tahoe
back
in
2001.
It's
2019
such
a
sort
of
a
kind
of
a
historical
package
which
was
still
carrying
with
us,
but
hey
one
step
at
a
time
and
I
think
kind
of
relates
on
the
discussion
which
we
did
not
actually
record,
but
I
wanted
to
actually
tie
in
and
to
mention
that
one
as
well.
We
talked
about
the
fact
that
you
can.
A
C
C
A
The
whole
point:
you
don't
want
that
to
look
like
SharePoint
a
well
there's
still
con
sites
which
look
like
SharePoint
as
well,
but
hey,
but
we've
kind
of
moved
more
and
more
towards
the
direction
where
we
have
slightly
more
limited,
and
especially
we
now
that
Microsoft
actually
explicitly
calls
out
what
should
be
document
customers
and
what
not
I
think
that's
a
beneficial
thing,
hopefully
for
people
as
well.
Well,.
C
But
it
was
the
whole
point.
There
was
time
when
we're.
Actually
the
Microsoft
team
would
say
it's
perfectly
fine
to
do
internet
sites.
It's
perfectly
fine
to
do
this,
so
it's
not
like
people
tried
to
cross
the
limit
of
the
product.
It
was
more
like
product
was
being
positioned
as
suitable
for
everything
as
the
Swiss
life
of
the
web.
You
can
you
want
to
have
collaboration,
environment
change
point
you
want
to
have
you
internet
side
SharePoint.
C
B
Tailor-Made
stuff
there
we
need
to
tell
them
it
is.
We
need
to
make
it
not
look
at
SharePoint
and
then
we
just
kind
of
like
over
branding
stuff
but
I
mean
I.
Think
it's
a
part
of
the
organical
move
towards
not
doing
a
smart
customization,
but
you
know
as
I've
also
matured
as
we
discussed
earlier.
I,
don't
recommend
doing
the
same
amount
of
customizations
I
mean
we
kind
of
more
like
work
with
SharePoint.
Now
right.
C
C
Like
yes,
there's
an
interesting
point
because
over
the
last
few
months,
I
talked
March,
customers
and
I
think
I've
done
before
in
in
all
the
years,
and
it's
only
proves
the
point
of
being
deaf
that
wasn't
really
my
job
to
talk
to
customers
and
the
one
thing
I
realized
is
that
it's
not
necessarily
true
that
people
are
all
no
adays
customized
less,
because
one
thing
that
we
see
like
SPF
X
is
still
or
is
the
hardest
growing
development
Auto
full-time.
So
people
still
build
things,
but
they
do
it
differently.
A
Maybe
a
few
times
that's
change
and
Albertine
on-premises.
You
were
always
having
the
opportunity
of
doing
and
then
stir
beside
it
changes
and
significant
changes.
There.
We
had
to
serve
aside
time
it
jobs
and
everything
else
now
we're
in
a
sure
which
is
a
completely
different,
ballgame
and
and
different
options
and
massive
amount
of
additional
opportunities
as
well
yeah,
which
isn't
done
a
really
shape
on
the
extensibility
anymore.
It's
it's
kind
of
offloaded
somewhere
else.
C
B
A
C
Because
for
them
they
would
say
so
we
invested,
we
made
deliberate
choice
to
be
on
premises,
but
then
we
would
build
everything
in
a
cloud
ready
way,
with
all
the
cons
of
that.
While
we
are
perfectly
fine
to
build
things
on
premises,
because
we
are
on
precedent
because
there
was
our
choice
to
be
on
premises,
sure
sure.
A
B
A
C
A
First,
yes,
welcome.
This
is
a
share
pontiff
weekly,
today's
so
ship
on
conference
coming
up
next
week
and
just
importing
for
this
one.
If
you
are
I,
think
you
can
still
get
tickets
for
it.
So
this
is
your
last
chance
you
we
are
releasing
this
video
on
Tuesday,
22nd
or
21st
of
May,
so
you
might
still
actually
get
a
massive
kind
of
a
demand
on
I
want
to
be
there
on
Wednesday.
If.
A
A
It
is
an
empty
Jim
Trent.
It
is
a
boo
birthday
last
week
last
year
as
well.
So
it's
it's
pretty
nice
location.
So
it
is
a
nice
setup.
Absolutely
that
and
you
don't
have
to
walk
as
much
as
in
the
classic
Chicago
ignite
I,
don't
know
if
you
waldek
were
actually
yes
I
was
there
I?
Was
there
I
just
don't
need
to
walk
because.
A
A
To
another
Wow
I
still
remember:
we
had
a
pre
day
in
Chicago
I,
don't
know
how
we
ended
up
on
this
discussion.
We
had
a
pre
day
in
Chicago
and
and
when
we
had
a
lunch,
we
had
a
one-hour
lunch
break.
It
took
us
20
minutes
seriously
to
the
walk
from
the
room
to
the
cue
of
the
lunch,
and
they
don't
realize
well
that
I
need
to
start
walking
back.
Fergus
I
need
to
be
on
time
under
its
well
yeah.
A
That
would
not
happen
in
Mt
amor
in
Orlando,
silence,
I
think
yeah
people
and
distances
read
and
like
anyway
or
Finland
anyway,
and
the
week
after
spc
there's
ten,
the
European
collaboration,
summits
and
I
think
European
cooperation
summit,
just
Prague
2,000
attendees
I
saw
that
in
Twitter,
which
is
pretty
cool.
It
is
a
community
treatment
conference
no-profit
conference.
So
it's
a
slightly
different
than
SBC,
but
and
it's
that's
why
it's
actually
quite
much
cheaper
as
well
so,
but
you
still
have
more
time
joining
on
European
collaboration
summit.
I,
don't
know!
A
C
A
So-
and
this
is
basically
so-
there
is
a
a
introduction
on
the
story.
David
did
a
video
around
the
library
components
in
one
of
the
community
calls
already
and
I
think
this
is
the
kind
of
follow
up
on
that
and
then
talking
about
the
similar
topics
as
well,
but
really
good
set
up
and
good
discussion
point
library
components
are
still
in
preview,
but
they're
heading
to
GA
as
part
of
the
1.9
release
of
SharePoint
framework,
which
we
don't
have
a
public
date
yet,
but
it's
coming
relatively
soon,
not.
A
It's
a
good
way
of
putting
that
you
say
next
week,
the
a
Tuesday
in
one
month.
Some
of
the
months
reason
why
it's
gonna
be
an
a
to
say
is
that
we
are
looking
into
actually
moving
into
this
monthly
releases
cycle
relatively
soon
start
starting
already
in
June,
potentially
and
it's
gonna
be
I.
Think
we're
targeting
and
I
can't
promise
this
yet.
But
our
target
is
the
second
Tuesday
of
every
single
month
and
why
Tuesday?
A
C
C
A
Because
the
season
PowerShell
doesn't
have
a
dependency
on
SPF
X,
so
the
season
and
PowerShell
is
released
once
a
month
as
well.
We
aligned
that
on
a
month
month,
cycle
already
three
years
ago
or
something
like
that
when
I
moved
to
engineering
and
started
releasing
those
you
know
once
a
month
cycle
and
and
the
reason
for
that,
one
was
that
people
are
then
more
aware
when
something
is
coming
out
so
that
they
can
prepare
beforehand
said:
okay.
A
I
know
it
is
the
last
Friday
of
every
single
month
when
to
season
PowerShell
shipment
online
powershots
released,
that's
it
so
then
you
can
actually
prepare
your
own
internal
process.
For
that
and
in
same
way,
we
are
heading
to
there
with
SPF
X.
We
want
to
give
you
an
exact
date
or
approximate
idea
of
the
date,
so
you
can
actually
prepare
your
upgrades
and
plans.
Based
on
that
sorry
Simon,
you
were
about
to
say
something
when
no.
C
A
Still
I
can
still
oh
really
I
can
so
much
relate
on
the
fact
that
when
we
did
those
on-premises
sharepoint
updates
and
we
started
doing
those
some
Saturday
and
then
every
now
and
then
it
went
completely
sideways
and
then
it's
a
Sunday,
10:00
p.m.
and
they're
still
kind
of
a
I
need
to
get
this
up.
It's
ten
to
ten
thousand
people
are
coming
tomorrow
morning.
I
need
to
get
this
up.
C
Proves
the
point
right
is
it's
like:
is
their
thing
and
sure
it's
not
not
comparable?
On
the
other
hand,
maybe
it
is
right
if
I
look,
for
example,
at
CLI
like
we
ship
every
week,
every
weekend,
a
beta
and
then
once
every
month
the
beta
becomes.
The
release
and
release
is
just
push
of
a
code
that
if
that
has
been
tested
and
vetted,
and
so
the
release
itself
doesn't
really
mean
anything
there
is,
you
know
like
hours
of
process
that
can
go
wrong.
C
And
I
guess
we
have
to
do
it
because
it's
not
a
full-time
job.
For
me
to
maintain
CLI,
it's
a
sight
thing
and
it's
a
community
thing
as
well,
so
I
cannot
be
the
only
person
that
is
able
to
do
do
or
we
automated
all
of
it.
So
if
you
have
permission
to
push
code,
you
can
do
a
release
as
simple
as
that.
Yes,
absolutely.
A
It's
almost
the
same
as
with
the
BMP
see
some
new
cat
or
BMP
PowerShell.
It's
all
automated
as
much
as
possible
everybody
and-
and
there
should
not
be
a
single
point
of
failure
in
this-
this,
yes
and
sorry.
By
the
way,
David,
we
are
having
a
really
interesting
discussion
on
your
screen,
be
railed
slightly,
ok,
moving
on
on
the
articles,
let's
see
how
do
we,
where
we
ended
up
with
Sebastian's,
how
to
search
your
hub
sign
data
using
SharePoint
search
API?
We.
A
A
A
Complicated
okay,
creating
an
access
token
for
a
service
and
SPF
X,
and
this
one
is
from
May
14th
from
from
Paula
yeah
Paula
is
working
for
pH
calm,
and
this
is
really
around.
Let's
see,
how
do
we
actually
grant
access
token
for
SPF
X
and
how
does
it
actually
work
and
how
does
the
third
party
API
work
in
the
in
the
SPF
X
as
well.
B
A
Point
here
the
note
also
is
that
it's
it's
a
run
handling
of
the
of
the
access
token.
If
you
are
using
an
isolated
way,
part
I.
We
should
have
this
one
documented
properly
here
as
well,
and
if
the
isolated
way
part
is
requesting
access
tokens,
it
will
automatically
create
a
specific
issue,
ad
application
for
or
per
touch
solution,
which
is
a
good
thing
to
remember.
So
you
can
have
a
isolated
Krantz
and
permission
spell
web
part
as
long
as
the
web
parts
are
being
isolated,
and
this
is
a
setting
actually
in
in
the
web
config.
A
C
That
brings
us
I
think
also
to
an
interesting
discussion.
Point
that
we
can
maybe
spend
a
minute
or
two
on
like
interesting
to
me
is
that
this
is
now
developers
decision
to
run
isolated
or
not
where
in
reality
me
I
would
say
it
is
an
admin
who
say:
I
have
a
package
from
a
vendor,
maybe
with
whom
we
don't
have
a
deep
relationship
or
trust.
I
want
to
isolate
it
or
there
is
something
specific
to,
and
so
it
doesn't
it's
not
defined
by
the
package.
A
We
would
be
able
to
absolutely
relatively
easily
introduce
a
checkbox
or
an
option
in
a
deploy
functionality
when
you're
adding
an
SP
pkt
faulted.
Our
catalog,
which
is
then
I,
want
this
one
to
be
isolated,
which
is
a
fair
point.
It
is
slightly
kind
of
a
confusing,
does
a
developer
decision
at
the
same
time.
This
is
the
first
version
and
we
evolve
things
as
we
move
along,
and
you
might
also
argue
that.
A
Well,
every
single
admin
should
know
exactly
what
they're
deploying
I
do
understand
that
that
is
not
reality,
but
the
admin
ultimately
is
responsible
of
deploying
stuff
in
our
catalog.
So
the
administrator
and
the
solutions
which
are
getting
deployed
in
the
tenant
should
be
vetted
and
signed
off,
using
whatever
process.
I
think.
C
I
would
like
to
rephrase
that
I
really
what
I
think
I
would
like
to
say
that
I
haven't
should
shouldn't
be
able
to
make
educated
Asian
about
what
they
put
in
production
and
because
they
do
not
read
read
code.
They
need
to
have
tooling
that
allows
them
to
understand
what
is
it
that
they
put
in
production
and
only
to
have
a
zip
and
then
having
to
go
through
code
in
XML?
That
is
not.
A
Whenever
you
have
a
SP
vacate
a
file
which
contains
and
unique
permissions
or
permission
Krantz,
it
is
actually
not
defined
for
the
administrator
yeah.
This
package,
this
package
is
actually
containing
unique
permissions
and
access
to
AP.
Are
you
sure
that
you
want
to
do
this
so
because
it
grants
access
to
those
krafayis?
So
there
is
an
additional
set
of
kind
of
AX
information,
but
I
do
agree
with
you.
We
can
make
it
more
better
in
the
future,
in
the
deployment
of
things
so
and
that's
one
of
the
things
what
we're
absolutely
doing
in
the.
A
If
I
put
my
engineering
hat
on
and
SPF
X
p.m.
hat
on
we're
looking
into
more
and
more,
let's
say
polish,
the
experiencer
is
what
we
are
having
so
not
just
introducing
new
features
and
because
we
actually
talked
a
few
times
in
SPF
weekly,
already
I
think
from
a
feature
perspective,
we're
starting
to
be
in
a
relatively
good
shape.
A
It's
not
about
introducing
something
as
traumatic
eyelash,
upon
framework
extensions,
sure,
adding
more
extensions,
but
as
a
completely
new
time-
and
this
gives
us
then
the
opportunity
of
starting
to
polish
and
maintain
and
improve
existing
stuff,
which
funny
enough
is
actually
what
our
engineers
are
asking
us
to
do
as
well.
So
they're
like.
Can
we
stop
rushing
and
introducing
new
stuff?
Can
we
just
make
the
existing
stuff
better,
which
is
a
funny
thing,
because
then
we
have
other
teams
and
engineering
teams,
who've
been
actually
maintaining
and
improving
and
obviously
they're
saying.
C
It's
it
all
comes
down
to.
Is
this
interesting
dynamic
of
managing
a
product
right
at
some
point
like,
depending
where
you're
at
you
might
be
at
some
point,
come
compute
to
the
point
where
you
say
you
know
the
marketing
is
this:
we
have
this.
There
is
a
gap
that
we
need
to
close
and
then
it's
somebody
like
ok,
we
support
80%
of
the
90%
of
the
most
important
thing.
C
C
A
One
way
of
actually,
even
if
you
think
about
this
VFX
dev
team
I,
can't
go
to
an
exit
details
because
I
don't
want
to
because
people
will
probably
make
out
but
and
but
it
it's
it's.
It's
almost
like
a
startup
which
we
are
building
and
sure.
Then
we
have
our
internal
customers
who
are
improving
and
building
their
components
on
top
of
them.
A
So
out-of-the-box
experiences
are
all
built
on
top
of
SP
FX,
but
but
sure-
and
you
might
consider
that
as
the
startup
inside
of
the
bigger
company,
because
it
acts
super
a
channel,
we
have
few
PM's
and
and
then
engineers
actually
implementing
stuff
on
top
of
the
specs
and
planning
of
the
PM's.
And
but
it's
not
like
the
Satya
or
rushes
is
actually
saying
what
needs
to
be
done
in
this
matrix.
No,
no,
no,
no,
we're
actually
controlling
that
and-
and
we
are
making
that.
C
In
a
sense,
it
makes
my
day
yeah
yeah,
but
I
mean
they.
They
don't
scale
at
that
point
across
Microsoft
everything
Microsoft's
from
AI
to
Azure,
to
cloud
to
Dynamics
through
Expo,
no
sorry
to
break
it
for
you
and
and
I
think
that
are
too
poor,
not
I.
Don't
think
I!
Don't
think
that
that
is
the
power,
because,
no
matter
how
big
your
dev
team
is,
there's
always
a
limit
to
it.
Tran
developing
a
product
that
is
one
difference
that
I
experienced
myself
like
coming
from
from
project
world
project
ends
right.
C
It
has
a
start,
it
has
and
you
build
the
things
that
are
expect
and
you're
done.
There's
you
ship,
it
delivery.
You
close
it
and
you're
done.
If
that
is
never
taken,
some
product
there's
always
more
work
than
hours.
In
a
day.
It's
a
never-ending
process.
There's
always
no
matter
how
many
people
you
have.
There
will
always
be
more
work.
You
might
ship
more
in
less
time,
but
there
will
always
be
improvement,
because
the
moment
you
ship
things
you
give
them
to
customers,
they
will
come
up
with
an
another
requirement.
C
B
A
Absolutely
the
question
is
more
on:
when
is
it
good
enough
for
shipping?
And
then
you
need
to
have
this
kind
of
an
improvement
mindset,
which
is
the
fact
that
you're
not
a
perfectionist,
because
that
would
mean
that
you're,
never
shipping
and
but
if
you're
improving
list,
you
are
accepting
the
realities
and
you're
able
to
ship
a
version.
But
then
you
keep
on
improving
and
improving
and
improving
it's
an
endless
cycle
of
improving
and.
C
The
key
point
there
is
to
help
everybody
to
understand
that,
what's
being
shipped,
what
it's
supposed
to
do,
what
is
meant
to
do,
and
what's
next
right
and
not
trying
to
say
like
yeah,
we
solve
problems
yeah,
but
you
only
did
this
one
thing
yeah,
you
know.
So
it's
really
important
to
help
people
to
understand.
We
ship
this
as
a
first
stage
to
address
this
one
one
issue
and
we're
looking
into
doing
issue:
2
3,
&,
4,.
A
Which
I
think
we'd
be
done,
a
relatively
good
job
with
SPF
X,
because
we're
being
quite
open
and
honest
on
what
are
we
doing
and
what
are
we
shipping
and
what
are
we
addressing
and
and
then,
if
something
is
a
gap
or
something
isn't
working,
we
open.
Let's
say
that
it's
not
working
so
because
I
think
that's
a
highly
beneficial
thing
for
everybody.
This
kind
of
relates
on
a
and.
A
Where
are
we
progressing
and
when
is
it
actually
identified
when
this
is
actually
closed?
If
there's
any
workarounds,
rather
than
trying
to
hide
things
and
having
a
one-to-one
isolated
discussions,
that's
not
beneficial.
We
work
in
the
scale
in
the
global
scale.
We
need
to
be
able
to
go
and
boot.
Our
own
I
can't
say
this
out.
If
we
were
to
out
loud
to
say.
C
B
B
A
C
A
C
C
Sometimes,
knowing
less
it's
better,
it
puts
you
at
ease
and
having
somebody
taking
care
of
the
you
know
ironing
out
wrinkles
did
this
is
good
as
long
as
you
know
sure,
once
in
a
while
things
might
go
wrong,
but
there
is
somebody
on
it.
Somebody
owns
it,
things
will
be
fixed,
I
will
not
be
harmed.
That
is
all
I
want
to
know.
Yep.
A
A
A
The
PNP
templating
engine,
starting
from
May
2019,
is
actually
supporting
also
managing
our
ad
users,
so
you're
able
to
actually
create
a
PNP,
10
or
template
and
then
which
is
actually
creating
at
your
ad
users,
and
this
is
basically
intended
to
be
used
with
the
demo
tenants.
We
were
able
to
actually
set
up
a
really
kind
of
a
large
tenant
template
and
then
we're
able
to
apply
that,
and
then
you
have
a
the
licensees
and
users
and
azure
ad
and
everything
else
defined
usage
so
should
be
helpful
for,
for
example,
automatic
testing
if
needed.
A
So
how
to
solve
a
spec
multi-line
filled
render
in
a
single
line
text
issue
which
comes
trying
to
create
a
multi-line
text
box
in
SPF
X.
So,
let's
see
this
is
a
multi-line
text
box.
This
is
a
rendered
multi-line
text.
There
we
go.
So
how
do
we
solve
this
challenge
of
a
multi-line
text
here
and
then
it's
being
rendered
in
a
single
line,
because
we
basically
take
just
the
text,
which
is
that.
C
A
A
A
Gute
didn't
hear
from
pram
this
new
version
of
the
sharepoint
client
process.
If
you're
not
aware
of
what
is
the
shape
on
client
projects
ever
look
on
this.
This
is
absolutely
brilliant,
tooling,
for
getting
insides
of
your
sharepoint
form
if
it's
on
prim
on
SharePoint,
Online,
tenants,
so
absolutely
absolutely
brilliant
stuff,
and
what
Prem
has
been
building
this
for
quite
a
few
years
actually
and
basically
what
I
did
provide.
You
is
a
really
nice
insights
as
you're
able
to
go
to
site
collection,
regional
settings,
lists
list
items
properties
all.
A
Everything
inside
of
the
things,
so,
if
you're
kind
of
as
an
example,
if
you're
wondering
I,
think
we
as
an
example,
would
pretty
recently
use
this
quickly
to
check
what
is
the
difference
between
the
Bates
template,
folder
and
Bates
templates
in
the
related
on
page
10,
modern
page
templates.
So
we
were
able
to
figure
out
what
are
the
property
differences
between
the
folders,
which
makes
a
modern
page
as
a
template
rather
than
more
on
page
yeah,
because
it
exposes
all
of
those
properties
and
ever
so
really
really
really
really
great
tool
and.
C
A
Fine,
that
is
a
good
as
well
and
and
then
pram
is
sharing
only
the
docks
and
the
actual
releases,
so
he's
not
actually
open
sourcing,
the
code,
which
would
be
good,
and
it
would
be
probably
beneficial
for
him
as
well,
so
that
other
people
can
contribute
on
this
tool.
So
right
now
he
is
managing
that
by
themselves.
A
Whatever,
yes,
that's
true
as
well,
that
is
change
and
then
in
here,
from
search
a
what's
new
and
what's
changed
in
SharePoint
Online
REST
API
between
March
and
April
2019,
so
search
a
has
created
this
REST
API,
a
metadata
Explorer,
which
is
a
really
really
really
cool
tool.
So
basically
it's
listing
what
the
REST
API
is
and
what's
available
on
pana
getting
exposed
there.
It
is
automatically
basically
scanning
the
metadata
of
the
old
data,
endpoint,
really
cool
stuff,
and
this
is
basically
a
list
of
things.
A
What
has
been
changed
related
on
the
REST
API
is
behind
the
scenes,
so
comparing
two
older
versions
on
the
newer
version-
maybe
one
thing
to
notice
here-
is
that
the
fact
that
the
REST
API
exists.
It
doesn't
mean
that
it's
available
for
third
party,
so
it
doesn't
mean
that
it's
intended
to
be
used
by
a
third
party.
So
we
might
actually
change
that
unless
it's
documented
and
then
we
document
any
changes
and
we
do
the
versioning
or
precisely
so.
The
challenge
is
that
we
might
actually-
and
we
need
to
do
this
all
the
time.
A
So
we
implement
a
new
web
part
in
engineering.
We
need
to
have
a
new
specific
API
for
it.
We
introduced
the
API,
but
it's
not
intended
for
third
party,
and
then
we
modified
the
API
still
until
it
is
actually
released
properly.
So
please
be
aware
of
that
good
and
then
the
last
piece
was
here:
BMP
provisioning
templates.
This
is
a
company
called
provision
points
but
they're
using
the
BMP
provisioning
templates
behind
the
scenes,
and
it's
interesting
way
of
combining
the
business
and
then
to
the
open
source
templating.
A
It's
not
a
massive
blog
post,
but
it's
actually
interesting
to
say
that
people
are
able
to
build
their
businesses
based
on
top
of
the
open
source
tooling
as
well,
which,
in
the
case
of
PMP
proration
templates,
I,
think
that's
relatively
safe,
there's
more
than
thousand
multiple,
multiple
thousands
of
customers
and
partners
using
PMP
templates
every
single
month.
So
it's
quite
safe
and
everything.
What
we
do
in
the
PMP
templates
and
PMP
in
general
are
designed
to
be
backward
compatible
so
whenever
they
say
API
change.
A
A
A
A
C
The
worst
part
is
that
you
actually
could,
and
that's
it
always
scary,
hey
what
oh
you
actually
could
you
actually
keep
doing,
what
you're
doing
what?
What
so,
what
you
know
now
you
could
retire.
There
are
companies
that
are
still
on
premise.
There
is
still
that
used,
2003
sure
no,
they
will
still
be
companies
that
are
in
2016
19
for
the
foreseeable
time.
Fair
point
fair
point,
good
point.
Well,
the
other
thing
is:
do
you
want
to
do
that,
but
that
does
yeah.
A
B
A
A
B
B
A
C
A
C
A
C
A
Yeah,
okay,
it's
good
to
know
good
to
know,
and
one
of
the
number
one
rules
by
the
way
with
why
isn't
Microsoft
employees
never
know
about
licenses,
one
of
the
number
one
rules
as
much
of
consultant
or
as
a
p.m.
or
as
an
engineer,
is
that
you
do
not
talk
about
licensing.
You
do
not
talk
about
writing.
C
A
C
A
B
C
C
A
For
fitness,
culture
and,
let's
close
up
the
Finnish
culture,
is
that
you
give
me
a
price
and
there's
a
price
and
it's
the
same
price
for
everybody.
If
what
do
you
mean?
That
is
a
separate
price
based
on
the
couch
they
supply?
It
is
the
same
price
for
everybody,
because
that's
how
it
should
be.
That's
the
right
thing
to
do
and
that's
beneficial
for
everybody.
C
A
Thinking
this
yesterday
or
this
morning
when
I
was
walking
out
with
the
dog
and
the
differences
between
the
culture,
I
think
there
was
something
like
when
there's
a
9:00
a.m.
meeting
in
the
morning
with
the
customer.
The
differences
between
sweets
are
that
sweets
are
still
negotiating
who's,
gonna,
be
on
that
9:00
a.m.
in
a
meeting
in
the
morning
when
the
meeting
actually
happens
and
the
the
Germans
will
be
arriving
on
that
meeting
at
9:00
a.m.
A
in
the
morning
sharp
and
they
will
open
the
customer
door
at
9:00
because
they're
precise
and
they
will
be
there
at
9:00,
because
we
agreed
that
it
would
be
not.
The
difference
between
FinCEN's
Germans
is
that
we
actually
arrive
10
to
15
minutes
before
9:00,
and
then
we
circle
around
the
house
until
it's
9:00.
C
C
A
Just
in
case-
and
we
are
absolutely
precisely
on
on
there
at
the
same
time,
so
cultural
differences
on
that
bombshell,
okay,
cool
I-
think
that's
it.
Thank
you
for
this
one,
a
few
failures
I
took
much
longer
than
we
were
planning.
Okay,
these
things
do
happen,
and
hopefully
this
recording
was
successful.