►
Description
In this 17-minute developer focused demo, Vesa Juvonen shares list extensibility capabilities that will be rolled out incrementally April through June 2022 within the next SharePoint Framework (SPFx) version 1.15. The early April preview release supports creation of modern custom forms for – viewing, creating and editing individually selected list items. SPFx forms are associated to a list/content type. If a list item is returned in a search result, then it is rendered and editable within the custom form associated to the item. This PnP Community demo is taken from the weekly Microsoft 365 Platform Community call recorded on April 5, 2022.
Demo Presenter: Vesa Juvonen (Microsoft) | @vesajuvonen
Supporting materials:
• Documentation - Overview of the SharePoint Framework | aka.ms/spfx
Learn more:
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp/videos
A
It
has
to
automatic
single
sign-on
automatic
hosting,
which
is
a
big
thing,
so
you
don't
have
to
worry
about
azure
hosting
or
anything
any
of
those
configurations,
plus
operational
cost
and
maintenance
there
and
then
consistent
dev
experience
and
using
industry
stranger
to
web
stack
tooling.
Now
the
name
is
a
bit
confusing,
but
like
chef,
deeper
loves
to
say,
sharepoint
is
the
content
and
application
services
for
microsoft
teams
and
for
the
broader
microsoft
365.
So
we
are
looking
into
potentially
again
naming
the
sharepoint
framework.
A
One
of
the
classic
requests
related
on
shipment
framework
for
many
many
many
many
many
years
is
that
well,
please,
please,
please,
microsoft,
allow
us
to
build
a
or
develop
custom,
modern
forms
with
custom,
edit
experience
so
as
part
of
the
the
sharepoint
framework
initial
release
back
in
2017
and
after
that
we've
been
having.
Is
it
20
releases
already
consistently
a
few
times
in
a
year?
A
And
quite
often
people
started
asking
that
well,
I
would
like
to
have
an
extensibility
options
and
editing
experiences
in
the
list
level
as
part
of
the
1.13
release
of
sharepoint
1.3
version
of
sharepoint
framework.
We
introduced
field
level
customizers,
but
those
only
works
when
we
are
when
you
are
viewing
a
field
value
in
a
list.
Not
when
you
are
editing
a
field
value
in
the
list
and
that
was
kind
of
a
not
an
optimal
experience,
so
one
of
the
number
one
requests
do
we
have
the
number
of
votes.
A
Yes,
we
do
two
one
one
of
the
number
one
requests
in
the
microsoft
feedback
center
related
on
sharepoint
has
been
this
item
with
2579
votes.
This
picture
taken
today,
and
it's
probably
in,
is
a
bit
more
than
that
nowadays,
so
it's
in
top
five
of
the
most
requested
capabilities
within
the
sharepoint,
which
is
kind
of
cool
that
we're
finally
addressing
this,
and
and
yes
it's
about
time.
There
are
certain
internal
reasons
and
discussions
why
this
took
a
while,
but
we
are
finally
getting
there
now.
How
will
this
actually
work?
A
The
first
version
will
be
released
as
part
of
the
1.15
and
1.15
preview,
which
is
coming
either
this
week
or
next
week.
We'll
have
a
preview
capability
of
this
to
be
available,
but
what
we
basically
provide.
You
is
an
option
to
associate
an
item
level,
editing
a
new
or
a
view
form,
so
you
can
overwrite
the
whole
form
any
way
you
want
now
just
to
be
just
to
be
super
clear
on
this.
A
This
is,
in
an
item
level
we're
going
to
talk
about
those
limitations
as
by
doing
the
demo
as
well,
and
that
is
where
we
are
starting.
So
basically,
in
the
first
version
of
this
in
1.15
when
1.15
goes
out,
you
cannot
overwrite
the
whole
list,
so
you
will
not
have
an
option
to
overwrite
the
whole
list.
A
Where
we
will
show
multiple
items,
you
can
only
overwrite
the
new
edit
and
view
individual
item
experiences,
but
what's
really
cool
on
those
overriding
support,
as
you
can
see
on
the
right
side,
the
bigger
picture
is
that
you
will
have
the
full
ownership
of
the
whole
canvas.
Now
we're
not
going
to
give
you
just
to
be
super
clear
setting
the
scenes.
We
are
not
going
to
give
you
reusable
controls.
A
We
are
not
going
to
give
you
reusable
buttons
or
anything
like
that
in
the
first
stage
from
the
engineering
side,
it
might
be
that
community
is
building
something.
That's
a
separate
discussion,
but
the
engineering
will
give
you
the
full
white
canvas
which
you
can
own.
You
can
build
whatever
you
want
here
using
then
react,
angular,
no
framework
or
whatever
is
your
preferred
option
and
that's
actually
really
really
really
cool.
You
will
get
access
on
the
context
details
in
the
code,
so
you
can
basically
say
I
have
disk.context.list
id
or
desktop
context.item
id.
A
So
that's
kind
of
the
experience
here
looking
and
and
super
excited
to
finally
get
things
in
moving
and
again
it's
just
first
step.
I
will
come
back
on
just
the
follow-up
thing:
follow-up
steps
after
the
demo
as
well,
so
what
we
will
have
in
1.15-
and
this
is
what
we
will
have
in
1.15
with
the
initial
preview
within
with
this
week
or
next
week
and
I'll
show
this
one
in
practice.
A
So
as
part
of
the
creation
of
the
1.15,
so
I'm
running
a
1.15
version
of
1.15
beta
version,
beta
5
version
of
the
sharepoint
framework.
Here,
let's
close
up
things,
let's
zoom
up
the
things
a
bit
and
let's
close
that
one,
and
so
now,
if
I
run
yo
microsoft,
sharepoint
so
run
the
yeoman
generator
of
sharepoint
framework.
A
We
will
have
additional
options,
so
I'm
running
spf
execution
generator
1.15
beta
5.,
it's
by
the
way,
really
cold
of
its.
The
version
is
visible.
Finally,
in
that
window,
which
is
which
is
great
and
let's
call
this
a
new
project-
so
that's
fine.
If
I
select
now
extension,
we
will
have
a
new
extension
type
here,
which
is
the
form
customizer
and
that's
actually
the
one
with
sustain
target
to
be
used
in
the
view,
editing
or
view
editing
or
new
experience
of
an
individual
item
in
the
list,
and
we
will
provide
you
two
different
templates.
A
So,
let's
give
it
a
name
and
no
framework
and
the
react
template
as
a
starting
point,
but
again
like
with
anything
with
sharepoint
framework.
You
can
use
any
javascript
framework
and
libraries
we
in
microsoft.
We
use
react,
but
that's
not
set
the
stone
that
you
need
to
use
react
okay
up
to
you.
What
are
we
going
to
do
then?
A
And
it
is
also
for
libraries.
So
that's
actually
a
good
point
russell
and
thank
you
for
calling
that
and
that
out,
so
it
will
work
actually
in
the
library
level
as
well.
So
technically
libraries
are
lists
with
files,
so
it's
super
super
close
technically
behind
of
the
sense
now,
I'm
not
gonna
run
the
creation
in
here,
because
I
already
created
this
a
new
solution.
This
has
been
just
created
before
our
session,
so
I
will
actually
go
in
the
visual
studio
code
and
I
will
show
you
what
we
got
so
surprise.
Surprise.
A
It
is
a
typical
business
studio,
sorry
sharepoint
framework
solution
with
the
packet
solution,
nothing
special
as
such,
it
will
have
the
default
extension,
which
is
then
based
on
the
new
component
type,
which
is
a
base
form
customizer.
So
this
is
the
new
component
type,
a
new
extension
type,
which
we
can
then
associate
to
be
used
in
a
content
type
level.
I
will
come
to
the
details
on
that
one
in
a
second
and
then
in
here
in
this
component.
A
It
is
relatively
simple,
at
least,
as
we
start
start
the
game
and
start
to
turning.
It
will
basically
have
a
render
option
and
then
again
you
can
do
whatever
you
want
and
you
have
full
access
on
the
dom
element
and
basically
the
div
and
you
can
render
whatever
you
want
inside
of
that
section.
Full
ownership,
no
control
from
our
side,
which
gives
you
the
full
flexibility
on
what
you
want
to
render
as
we're
then
closing
in.
A
If
you
can
call
on
close
or
unsave
and
those
are
technically
the
ways
of
okay,
are
we
going
to
do
saving,
or
are
we
going
to
go
closing
in
this
case,
so
you
would
be
drawing
those
buttons
and
make
that
happen
so
relatively
simple
from
that
perspective,
jim
is
asking
how
secure
it
is.
I'm
not
sure
if
that's
related
on
this
one,
but
of
course
this
is
sharepoint
framework
solution.
You,
as
an
administrator,
you
deploy
this
you're
unable
to
otherwise
get
these
solutions
in
place,
and
so
secure
admin
controlled
like
any
sharepoint
solution.
A
Now,
as
we
start
then
this
journey
and
as
we
start
testing
this,
let's
do
a
quick
example
on
how
I
would
be
doing
development
in
this
case,
I'm
going
to
start
at
the
terminal
in
the
serve
json.
We
do
give
you
a
default,
let's
say
starting
point
of
doing
debugging
and
let
me
be
super
clear.
This
is
part
of
the
preview
experience
and
because,
as
part
of
the
initial
preview,
modern
lists
are
not
yet
aware
of
this
new
component
type
and
there's
no
api
level
support
of
setting
this.
A
So
we
need
to
do
some
tricks,
and,
and
so
we
can
start
doing,
development
and
testing,
but
you
cannot
access
from
the
ux
directly
to
this
experience.
Yet
that's
going
to
be
coming
obviously
later
this
spring.
So
that's
our
default
structure
and
that's
our
default
debugging
thing
in
the
surf
json.
So
let
me
go
back
on
my
develop
test
tenant
and
let
me
actually
create
here.
I
didn't
create
a
new
list,
or
did
I
let
me
create
a
new
list
and
let's
create
a
new
list
and
blank
list.
A
Let's
call
this
call
demo,
it
doesn't
really
matter
it's.
The
name
is,
and
let
me
create
that-
and
it
is
of
course
a
normal
normal
list,
so
whatever
you
want,
you
can
do
it
with
less.
You
can
do
it
with
the
list.
So
no,
no
problems
with
that.
Now
one
of
the
challenges
is
answering
start
this
journey
and
again
this
is
mainly
for
the
preview
preview.
Not
for
the
ga
is
that
we
need
to
be
able
to
now
figure
out.
A
Let
me
actually
zoom
this
bit
more
and
then
I
will
go
to
classic
advanced
settings
in
the
advanced
settings
of
the
list.
I'm
going
to
go
to
advanced
settings,
advancing
cyclone
settings
and
I
will
say,
allow
management
of
content
types,
because
then
this
gives
me
the
visibility
of
the
content
type
level
you
can
programmatically
solve
this.
You
can
programmatically,
then
access
this
information
and
set
the
information.
A
Also
in
the
content
type
level,
whenever
we
get
the
feature
g8
now,
what
happened
with
that
setting
is
that
now
I
have
this
content
type
section
available
in
the
list
would
be
the
same
as
in
libraries
and
now
I
can
actually
go
to
the
content
type
of
item
now.
In
this
case,
the
content
type
id
of
this
particular
item
is
visible
in
the
url,
and
this
gets
a
bit
tricky
again.
A
A
Let
me
then
go
to
the
actual
code
and,
as
I'm
doing
debugging
again
jim
is
referring.
That's
the
list,
content
type
id.
It
is
correct.
That
is
correct.
Again,
terminology
things
are
a
bit
debatable
always,
but
as
I'm
doing
debugging,
I
want
to
do
debugging
against
that
list.
I'm
going
to
say
that
the
content
type
which
I'm
associating
this
item
is
that
particular
content
type,
so
I'm
able
to
then
actually
associate
the
code
to
actually
work
in
there.
I
need
to,
of
course,
also
update
the
base
url.
So
let
me
go
in
here.
A
A
So
this
is
then,
enabling
me
to
do
debugging
of
my
codes
in
that
list
item
when
I'm
actually
going
to
do
cop
serve
now
before
I
do
that
and
before
I
we
see
that
did
my
settings
and
everything
work.
I
just
wanted
to
call
out
that
in
the
code
of
course,
as
we
are,
writing
sharepoint
framework
components,
you
will
get
access
on
this
context
and
then,
in
the
context
we
will
get
access
on
the
list
list.
Instance.
A
Cool.
Now
I'm
going
to
do
here,
cop
serve
and
that's
oop.
If
I
can
run
right,
let
me
actually
abort
that
observe
and
based
on
now
our
serve.json
configuration
it's
going
to
start
to
default
default
hosting
and
it's
gonna
fire
the
running
in
here
and
now.
I
have
clearly
a
pac
which
I
know
and
that
I
have
a
block
here
now.
I
started
that,
but
I
can
see
immediately
that
my
debugging
is
starting
in
a
completely
wrong
list.
So
something
is
wrong.
Let
me
go
back
in
here.
A
Let
me
go
back
and
search
the
json
and
we
can
see
that
didn't
I
save
this
is
the
saving
is
missing.
So
that's
what's
missing,
okay,
so
let
me
add
there
that's
in
a
wrong
way.
I
didn't
update
the
actual
site
correctly
and
let
me
actually
upload
that
so
we
can
see
that
it's
starting
in
the
right
context.
So
one
more
time
checking
it
is
a
subside
collection
called
comms
in
that's
tenant.
That
looks
good.
A
That
url
looks
good.
That
was
the
code
demo
and
now,
if
I
do
one
more
time
called
serve,
we
can
actually
see
that
the
pros
of
windows
starts
in
the
context
of
that
url
and
it
feeds
the
right
query
parameters
and
it
starts
loading,
the
scripts
and
the
jiva
script,
and
when
I
click
that
one
we
still
have
an
exception.
No.
A
Let's
see
one
more
time,
let
me
see
what
I'm
doing
actually
wrong
here
and
load
deeper
scripts,
and
there
we
go
now.
We
didn't
actually
get
any
input.
So
let's
do
this
one
more
time
in
here.
Let
me
go
here
and
write
the
code.
Where
do
we
have
the
output
and
call
demo
call
demo
and
save
it?
We
can
see
runtime
saved
there,
that's
good!
A
So
the
next
1.15
preview
release
will
support
that
overriding
of
item
level
new
edit
and
viewforms,
and
you
will
need
to
do
that
debugging
directly
in
the
context.
So
it
will
not
understand
yet
in
the
list
level
that
you
are
associating
custom
component
to
the
content
type.
So
you
need
to
do
some
level
of
a
tricks,
as
I
did
in
this
demo,
and
that's
the
reason
why
we
wanted
to
have
this
demo
recorded
as
well.
A
A
So
if
you
are
using
the
site,
scope,
deployment
option
with
sharepoint
framework
solutions,
and
then
we
are
looking
into
having
a
additional
options
for
this
extensibility
in
the
future
as
well
and
no
eta
on
those
and
no
decisions
at
this
point
that
they
will
happen.
But
that's
it
for
my
demo.
Hopefully,
that's
interesting
good
to
have
questions
and
and
comments
on
the
slide
I'll
follow
up
on
the
comments
right
after
the
call
as
well.