►
From YouTube: Upcoming Preview Word APIs - March 2023
Description
A 13-minute Developer-focused demo from Yun Wang. This is a quick briefing on Word APIs that will Preview in March. New/updated APIs include new insertFileFromBase64 API (insert content from source document into destination document), updated Style API (retrieve, show and insert other document’s styles in current document), Save / Close API (save/close new/existing documents), Fields API (more Field properties for selected types), and Content Control Events API (adding enter and exit events). Target mid-year GA.
This PnP Community demo is taken from the Office Add-ins community call – February 2023, recorded on February 8, 2023.
Demo Presenter
• Yun Wang, Principal Product Manager (Microsoft)
Supporting documents
• Survey - Future Word API candidates | aka.ms/WordApiNext
Learn more
• Microsoft 365 Unified Sample gallery - https://aka.ms/community/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/community/videos
• Microsoft 365 Platform Community - http://aka.ms/community/home
A
B
And
I
am
the
product
manager
for
world
extensibility,
and
today
I'll
talk
about
upcoming
preview
world
apis,
so
in
March
we
will
release
several
sets
of
apis
and
I
will
quickly
go
through
each
API
set
quickly.
Today,
and
hopefully
we
can
have
a
further
detailed
introductions
of
each
one
in
upcoming
Community
course,
but
today
I
will
quickly
go
through
those
and
the
the
first
one
is
the
new
insert
file
from
basic
base64
API.
B
So
if
you
have
ever
used
this
API
previously,
we
already
have
the
insert
file
from
base64
at
the
body
level
in
the
past,
so
the
past
behavior
is
that
you
know
user
users
can
leverage
this
API
to
insert
the
content
from
a
document
into
the
the
current
document
that
the
user
is
working
on.
So,
as
shown
in
the
the
picture
here,
you
know
on
the
right
side,
it
is
the
source
document,
and
if
we
want
to
insert
the
content
of
this
document
into
the
left
side,
then
they
they
bought
it
down.
B
B
You
know
it
has
another
behavior
that
if
the
source
document
that
you
want
to
insert
into
the
target
has
a
much
more
richer
format.
For
example,
if
the
source
document
has
you
know
different
fonts
different
styles
style
settings
and
also
you
know,
borders
Watermark
Etc,
when
the
user
tries
to
Leverage
The
API
to
insert
these
things
into
the
target,
it
will
fail
to
the
fail
means
that
you
know
only
the
text.
Content
will
be
inserted
into
the
target
document.
B
But
what
are
those
those
watermarks
header,
footer
or
page
border
and
stylings-
are
all
lost
during
this
process?
So
we
make
a
enhancement
the
the
reason
why
we
lose
all
those
things
was
because
that
many
of
these
settings
are
not
at
the
body
level.
They
actually
are
at
the
section
level
level
or
the
document
level.
So
that's
the
reason
why
we
introduce
a
new
API
with
the
same
name
at
document
level,
so
document
object
will
have
the
a
new
API
with
exactly
the
same
name.
B
The
purpose
here
is
that
once
the
user
wants
to
insert
a
source
document
into
the
target,
then
we
want
to
retain
as
many
things
as
possible.
So
in
the
example
here
example,
one
a
user
wants
to.
You
know
import
or
insert
a
file
with
different
things.
Like
page
borders,
watermarks
Etc
into
a
blank
document,
then
these
things
will
be
retained
after
the
insertion.
B
So
after
the
insertion
you
will
see
the
page
border
header,
footer
Watermark
from
The
Source
document,
so
that's
first
Behavior
or
first
feature
and
also
if
the
target
document
is
not
a
blank
document
which
means
that
the
the
target
document
also
contains
Different
Page
borders,
footer
header,
those
settings,
then
after
the
insertion
we
will
create
a
new
section
and
the
new
section
will
keep
the
source
document
settings.
So
if
you
take
a
look
at
the
result
in
the
picture,
you
know
we.
B
If
the
user
wants
to
append
The
Source
document
content
into
the
target
document,
then
those
page
borders,
header
things
will
be
kept
and
appended
into
the
document
as
well.
So
this
is
another
enhancement
we
do
for
this
new
API
and
also,
instead
of
keeping
these
content
level
things.
We
all.
We
also
select
several
document
level
settings
to
give
the
user
the
choice
to
to
see
whether
you
want
to
retain
these
settings
or
not
when
doing
the
insert
file
from
base64,
for
example,
track
changes.
B
If
you
want
to
retain
the
track
changes
settings
when
doing
the
insertion
now
we
provide
you
the
capability
to
see
whether
you
want
to
do
that
or
not
also.
It
is
the
case
for
the
style
settings,
for
example,
in
this
example
here,
the
source
document
has
a
style
setting
and
also
for
for
the
Target
document.
It
has
a
different
style
setting,
but
after
the
insertion,
the
user
can
choose
whether
to
whether
to
keep
the
source
document
styling
settings
Etc.
B
So
that's
for
insert
file
from
base64
and
next
one
is
style
apis
we
receive
different
requirements,
and
here
I
just
show
a
sample
add-in
that
can
demonstrate
the
requirement.
So
the
requirement
here
is
that
the
the
add-in
wants
to
not
only
apply
the
Styles
into
the
document
to
the
paragraphs,
but
also
the
add-in
want
to
select
different
styles
from
some
other
documents
in
this
example.
B
Here,
if
you
take
a
look
at
the
side
panel
here,
the
word
add-in
actually
can
list
different
styles
from
another
document,
so
in
this
case
the
user,
the
add-in
will
choose
some
specific
files
from
another
document
and
apply
them
into
the
current
one.
So
if
you
take
a
look
at
this
picture,
you
know
the
side,
the
left
panel.
B
The
task
plan
actually
shows
the
the
styles
from
another
document
and
after
the
user
click
one
of
the
Styles
and
this
style
will
be
applied
to
the
current
document
and
also
the
users
can
choose
whether
to
apply
these
Styles
into
the
style
gallery
or
not.
So
we
have
a
set
of
apis
to
support
the
scenario.
So
basically,
there
are
two
major
capabilities
here.
One
one
is
that
we
can
retrieve
and
pass
the
styles
from
a
base64
format
of
a
Word
document.
B
So
this
word
document
can
be
another
document
or
it
also
can
be
the
current
document
that
you
are
working
on.
So
once
the
base64
format
is
there
and
you
can
retrieve
and
pass
different
style
settings
and
retrieve
different
types
of
the
Styles,
including
the
used
Styles
in
the
source
document
or
the
customized
styles
that
created
in
the
source
document.
And
after
you
retrieve
all
types
of
the
styles
from
the
source.
B
Then
you
can
have
another
API
to
apply
these
styles
to
your
current
Word
document
so
that
it
will
have
the
the
user
not
only
say,
hey,
I
want
to
choose
some
specific
bonds
to
form
a
cell.
Then
you
know
the
add-in
now
can
be
that
you
know
I
can
select
some
specific,
look
and
feel
from
another
document
and
apply
that
look
and
feel
into
my
current
document.
So
that's
that
is
the
basic
working
flow
and
next
that
is
the
the
save
close
apis.
B
So
there
are
different
cases
whether
you
need
the
the
prompting
dialog
is
needed
in
order
to
specify
a
file
name
and
for
close
apis.
We
also
provide
the
support
for
new
document
and
existing
document,
but
for
closed
API.
The
current
behavior
is
that
once
you
choose
to
call
it
after
you
finish,
the
calling
for
the
close
API,
the
add-in
will
disappear
and
you
don't
have
the
the
control
of
the
add-in
anymore.
B
So
this
is
the
current
behavior
of
the
office
add-in,
but
in
the
future
we
could
have
some
enhancement
there,
but
today
you,
you
will
lose
the
control
there
and
the
next
set
is
Fields.
Api
I
know
many
of
our
partners
asked
for
this
for
years.
Actually
so
Fields
API
in
1.4,
we
actually
released
a
support
for
get
Fields
functions
so
that
you
can
retrieve
and
get
different
fields
from
your
document
for
the
upcoming
preview.
Now
we
have
the
full
support
like
create,
update,
delete,
Fields
capabilities
in
March
preview
version.
B
We
will
support
a
selective
types
of
the
field,
so
we
will
start
with
the
add-in
type
and
later
on,
May
extend
to
other
types.
So
in
March
version
you
could
see
one
two
or
three
types
of
the
fields
there
to
have
a
try-
and
this
is
not
only
enabled
for
word
desktop,
but
we
also
do
many
enhancements
for
word
online
so
that
your
editing
can
also
work
for
what
online
or
for
the
specific
types
of
the
fields,
content
control
event
apis.
B
You
may
already
know
that
we
have
different
content
control
events
apis
in
the
preview
already,
but
we
added
two
recently
so
one
is
enter
a
Content
control
and
exit
a
Content
control
again,
not
only
API,
but
also
the
word.
Online
capabilities
was
enhanced
that
you
know
what
online
support
more
content
control
features
so
that
your
add-in
will
work
across
the
platforms.
So
previously.
The
first
four
events
related
apis
are
there
in
the
preview
set
for
a
while.
We
are
expecting
to
have
all
these
six
apis
moving
into
GA
state
in
the
middle
of
this
year.
B
So
that's
the
quick
briefing
for
different
apis
as
preview
in
March
and
again,
these
apis
will
have
highly
possibilities
to
be
G8
in
the
middle
of
this
year
and
we
also
want
to
collect
your
further
feedbacks
for
future
enhancement
requirements.
So
please
scan
the
QR
code
or
or
click
the
the
link
here
so
that
you
can
enter
into
a
survey
for
future
advice
and
suggestions
to
us
and
that's
all
thanks
very
much.