►
Description
This webcast concentrates on techniques on accessing or updating SharePoint Taxonomy information (groups, term sets and terms) using APIs from SharePoint Framework solutions. As at the time of the video recording, there is no RES APIs to access this information in SharePoint, we need to fall back on existing CSOM API usage from the SPFx solution. This is a workaround until the taxonomy REST API exists in the SharePoint Online.
A
Welcome
to
the
SharePoint
banners
and
practices
webcast
and
system,
we
can
I
talk
about
how
to
consume
taxonomy
data
within
the
SharePoint
framework.
So
if
you
have
a
business
requirements
within
your
client-side
web
parts
or
extensions
to
access
the
taxonomy
data
or
potentially
even
update
the
SharePoint
taxonomic
data,
and
what
is
the
current
situation
of
how
to
do
that?
What
are
the
options
and
potentially,
what's
going
to
happen
in
the
future?
A
A
Excellent
excellent
power,
so
few
slides
and
then
do
a
live
demo
on
how
to
actually
make
this
happen.
No,
I
don't
know
how
well
you,
as
a
person,
who's
watching
the
video,
how
well
you're
up
to
date
on
the
current
situation
of
the
taxonomy,
but
we
have
this
a
small
challenge,
or
at
least
at
the
time
we
are
recording
this
video.
So
please
do
follow
up
on
the
on
the
latest
documentation.
A
This
situation
might
have
changed,
but
at
the
time
of
the
video
has
been
recorded,
there
is
no
native
REST
API
available,
so
don't
know
where
you
can
actually
access
the
ducks
anima
data
is
by
using
the
classic
season,
API
and
classic
season.
Api
is
actually
designed
to
be
used
using
the
managed
code,
essentially
using
Windows
and
don't
need
framework,
and
there
are
certain
set
of
available
types
and
actions.
So
you
can
access
the
taxonomy
session.
A
You
can
access
term
store,
accrue
terms,
that's
in
terms,
so
the
coverage
in
the
taxonomy
layer
in
season
is
actually
really
good.
Starting
from
SharePoint
2013,
SharePoint
2010
didn't
have
a
horrible
system.
Support
for
this
one
2013
good,
say
some
support,
but
then
it
now
in
2018
we're
already
moving
past
the
season
we're
moving
into
this
world
where
we
want
to
have
none
managed
code
abis.
So
how
would
we
actually
make
this
happen?
Well,
you
can
actually
make
this
happen
by
mimicking
the
season,
our
course,
and
let's
have
a
look
on
that
one.
A
So
what
does
it
actually
precisely
mean?
What
it
actually
means
is
that
the
season
is
internally
calling
a
client
SVC.
So
whenever
you're
using
the
writing
managed
code,
if
you,
if
you're
doing
a
console
application
or
provide
a
hosted,
app
or
whatever
and
you're
calling
a
REST
API
using
their
season,
taxonomy
api's,
it
is
actually
doing
a
remote
call
against
client
SVC.
So
it's
it's
a
soap
call
against
the
client,
a
space,
a
service
and
then
the
the
client
definitely
say
services
returning
data
back
remotely
as
well,
because
this
is
a
remote
API.
A
You
can
actually
mimic
calling
this
API
also
using
SharePoint
framework.
So
you
don't
have
to
use
explicitly
the
client-side
object
model
library
to
call
the
client
SVC.
Now
it
means
that
the
the
calling
and
the
structures
do
actually
get
pretty
messy
and
we
can
assured
that
on
in
practice
and
in
a
second
and
somebody
might
be
saying
wait,
is
this
really
supported
and
documented?
A
Well,
the
answer
is
technically
yes,
so
in
our
protocol
documentation
we
are
actually
defining
how
the
process
query
method
works
well,
which
actually
exposes
the
the
details
on
how
you
can
use
to
see
them,
even
though
you
wouldn't
be
using
the
season.
Client-Side
library
for
calling
the
client
area
SBC
and
what
it
means
in
practice
is
that
from
an
engineering
perspective
or
from
your
custom
development
perspective,
you
need
to
kind
of
reverse
engineer
on
what
the
season
is
actually
doing
and
then
copying
that
to
your
wrist
calls.
A
And
yes,
this
is
technically
horrible,
no
doubt,
but
once
again,
there's
no
and
no
native
REST
API
are
currently
available.
So
the
question
is
more
like
okay,
somebody
needs.
We
need
to
have
this
functionality.
I
need
to
make
this
functionality
worked
for
my
SharePoint
framework
solution.
If
options
are
I
can't
do
my
work
or
I'm
gonna
use
the
client
SVC
as
I've
worked
around,
you
can
use
the
client
as
busy
as
a
workaround.
Whenever
will
get
a
REST
API
for
taxonomy
and
native
hell.
A
B
If
I
can
add
a
sentence
here,
because
my
opinion
is
that
I
think
my
opinion
is
that
if
you
need
to
have
access
to
taxonomy
in
order
to
move
to
the
modern
UI
and
to
SPF
X,
it's
better
to
use
these.
Let
me
call
it
work
around
using
the
client
SVC
and
the
person's
query,
rather
than
being
stuck
on
the
classic
mode,
just
because
you
still
don't
have
support
in
system
or
sorry
not
in
system
in
the
REST
API
for
the
taxonomy.
So.
A
Yes,
yes,
absolutely!
So
how
would
we
put
this
in
there
in
a
this?
Is
not
a
black
and
white
recommendation
or
a
decision?
It's
well.
If
your
are
plugged
and
you
need
to
make
this
thing
happen,
this
is
the
only
way
you
can
actually
make
it
happen.
It's
not
a
recommended
way
of
doing
stuff
in
SharePoint
Online
by
mimicking
the
season,
but
it
does
get
you
unplugged.
A
A
B
Okay,
here
we
are
in
SharePoint
Online
in
the
mote,
Ananta,
which
I
will
use
for
this
demo
and,
as
you
can
see,
we
have
a
bunch
of
term
groups
and
some
term
sets
and
one
term
set,
which
is
the
one
I
liked
it,
which
is
made
by
few
terms
in
a
hierarchy
and,
for
example,
some
of
these
terms
have
some
custom
shared
and
local
properties.
Too.
B
B
So
let
me
refresh
this
page
to
show
you
the
output
and,
as
you
will
see
here,
we
have
an
array
of
three
items
which
are
the
three
terms
under
the
term
set
that
I
showed
you
the
first
one
is
the
legal
node
with
some
local
properties,
which
are
the
properties.
I
showed
you
a
few
seconds
ago,
and
we
have
two
more
terms,
of
course,
which
are
the
other
two
that
we
have
in
the
hierarchy,
together
with
the
children
of
the
rules
item
which
are
still
taxonomy
terms.
B
B
A
kind
of
magic
he's
putting
a
song
a
famous
song
yeah,
we
are
in
the
render
method
of
the
client-side
web
part
and
I
have
an
attached
P
taxonomy
service,
which
is
a
type
I
created
using
typescript
in
my
SharePoint
framework
solution
and
the
HP
taxonomy
service,
except
the
context
of
my
clients
at
web
parts
of
the
sharp-eyed
framework
context,
as
the
input
parameter
for
the
constructor
of
the
service.
So
when
I
provide
the
context
to
the
constructor,
I,
simply
create
the
URL
I
build
the
URL
of
the
client.
B
As
we
see
service
/
process,
query,
which
is
absurd,
which
is
the
target
and
point
of
my
service
to
do
the
real
requested
targeting
sharepoint
online
using
the
absolute
you
I
love
the
ways
in
which
I
am
of
the
website.
Sorry
in
which
I
am
and
in
order
to
consume
the
taxonomy
I
simply
need
to
use
a
method
which
is
the
get
terms
from
terms
sector.
B
In
fact,
I
have
to
provide
an
XML
request,
which
is
kind
of
where,
but
basically
simply
defines
based
on
the
documentation
which
we
referenced
in
this
light
back
defines
what
we
want
to
do,
so
it
defines
the
object
and
the
method
that
we
wanna
call
in
the
object
model
of
SharePoint
through
the
client
service
that
we
are
consuming,
and
here
we
just
get
the
term
set
by
name.
This
is
the
meadow
that
we
are
using
and
we
provide
the
name
of
the
term
set
as
well
as
the
locale.
B
If
we
want
to
use
a
specific
language
while
retrieving
the
term
set,
we
make
the
request
as
an
HTTP
request,
using
the
context
of
SharePoint
framework
and,
of
course
we
are
providing
an
XML
request,
and
so
the
content
actor
of
the
request
will
be
a
text
XML.
While
the
response
will
be
an
application
jism
and
the
application.
Json
response
will
be
an
object
which
will
be
made
of
a
bunch
of
objects.
It
will
be
an
array
of
different
objects
and
we
need
to
retrieve
from
that
array
of
objects.
B
What
we
are
targeting,
so
we
get
a
collection
of
term
sets.
We
get
a
specific
term
set,
which
is
the
one
we
have
in
target
and
for
that
term
set
we
get
the
child
items.
In
fact,
we
also
have
a
bunch
of
interfaces
defining
my
project
and
those
interfaces
define
the
output
D
JSON
output
that
I
will
get
back
from
the
process.
B
Query
request,
for
example,
I
can
see
that
at
our
center
is
a
property
called
the
terms
which
is
a
collection
of
terms
which
will
ever
a
child
items
which
will
be
in
our
way
of
term
and
every
single
term
will
be
made
of
all
of
properties,
including
the
children
and
all
the
other
stuff.
So
if
I
go
back
here,
I
simply
get
the
child.
The
items
of
the
children
terms
of
my
term
Center
and
using
a
recursive
approach,
I
can
go
through
all
of
them
and
I
can
expand
them.
B
In
fact,
the
expand
tap
method
will
use
them.
Let
me
scroll
a
little
bit
down
we'll
use
an
error,
get
sine
terms
method
which
will
make
another
request
to
get
a
lot
of
the
children
of
a
term
of
the
term
in
which
I
am
and
will
fill
all
of
the
missing
properties
like
the
custom
properties,
the
local
custom
properties
and
all
the
other
stuff.
The
get
child
turns
method
is
yet
another
method
which
still
uses
the
process.
B
Query
approach
with
another
excellent
request,
in
which
I
will
make
a
query
for
the
IV
object,
identity
of
the
term
that
I
want
to
expand
and
when
I
expand
a
term.
I
will
also
ask
to
sharepoint
online
to
give
me
back
the
custom
sort
order,
the
custom
properties
and
the
local
custom
properties.
So
this
is
a
technique
to
expanded
to
get
all
of
the
complex
properties
of
my
object
and
once
I
have
done
that
again.
Using
an
HP,
HTTP
client
request
a
post
request
and
getting
back
a
JSON
response.
B
I
will
go
through
all
of
the
terms
in
the
third
collection
which
will
represent
the
children
terms
of
my
current
Arman,
and
so
I
will
be
able
to
build
the
full
hierarchy
of
items
in
memory.
Of
course
they
can
do.
Caching
I
can
store
those
information,
for
example
in
the
local
session
storage.
If
we
want
to
improve
the
performances,
this
is
up
to
you,
but
basically
you
simply
say
give
me
the
terms
that,
and
you
will
get
back
a
full
iraki
of
terms,
ready
to
go
and.
A
An
obviously
like
I
said
you
should
be
guessing
some
of
this
data
because
it's
it's
it's
not
like
the
taxonomy
structure.
It's
going
to
be
changed
in
every
single.
Second,
it
might
be
changed
in
once,
every
single,
let's
say
5
minutes
or
10
minutes
or
whatever
is
the
once
a
day,
and
so
you
can
actually
cache
that
all
of
that
the
information
but
which
will
then
have
a
positive
impact
on
the
performance
right
now.
A
However,
we
wanted
to
concentrate
on
how
you
may
get
the
same
from
available,
which
is
how
I
got
it
dirty,
it's
it's
not,
it
doesn't
feel
good
it
doesn't.
It
doesn't
make
us
feel
good
either
in
the
shipment
engineering,
but
it's
it's
a
workaround
right
now
to
achieve
accessing
the
taxonomy
data,
even
though
the
dr.
taxonomy
doesn't
have
a
REST
API,
it's
but
I
think
let.
B
Me
add
one
more
things
or
if
you
just
will
be
available
in
the
upcoming
week,
sir,
based
on
the
date
of
recording,
because
it
is
part
of
a
bigger
project
which
will
become
available
before
some
are
this
year,
I'm
talking
in
2018,
so
stay
tuned.
You
will
find
much
more
content
in
this
sample
solution,
but
you
will
also
find
the
SP
taxonomy
serviced
are
ready
to
go
and
available
for
your
own
solutions.
A
And
there's
some
other
community
efforts
around
this
one
as
well,
so
looking
into
having
centralized
services
around
economy
building
this
old
model.
But
then,
whenever
the
native
REST
API
will
be
available
for
taxonomy,
we
can
just
flip
the
implementation
on
behind
off
the
scenes
and
more
information
on
all
of
that,
depending
on
when
you're
watching
the
video
might
be
already
out
or
might
be
coming
within
a
week
or
two
or
three.
A
But
let's
get
back
on
the
slides
and
close
up
better
webcast,
excellent
Thank,
You
Paula
for
the
great
demo
and
like
like
mentioned
even
when,
before
his
father,
started
the
demo.
Well,
it
looks
awkward,
it
looks
a
slightly
messy
and
it
did
made.
It
is
slightly
messy
that
you
need
to
mimic
the
classic
seasoned
API
calls
with
a
client
SVC,
but
if
this
is
the
only
option
for
you
to
get
your
business
requirement
completed
right
now,
just
a
native
REST
API
is
some
missing.
B
B
And
from
a
cost
perspective
having
in
Asia
infrastructure
to
do
that,
it
can
be
a
problem
if
you
are
just
developing
a
small
solution.
Of
course
you
can
building
a
much
big
solution.
Of
course,
it
will
make
sense
to
have
an
Asian
infrastructure
and
have
all
the
services
and
all
the
stuff
back
in
your
solution
measure,
but
if
it
is
a
small
one,
maybe
this
one
is
a
better
option,
or
at
least
the
cheaper
option.
Now.
A
Paulo
I
want
to
have
a
black
and
white
recommendation.
No
there
isn't
that's
a
classic
thing.
Always
people
want
to
have.
So
what
is
the
recommend
a
thing
for
microcell?
It
depends
because
reality
is
that
there's
multiple
ways
of
achieving
and
this
and
this
end
result.
So
there's
no
black
and
white
recommendation
on
this
one,
but
anyway,
I
think
that's
pretty
clear
now
how
it
can
be
happening
and
done
and
will
reference
the
code.
A
Well,
the
code
sample
itself
and
depending
when
you
are
watching
the
video,
it
might
not
be
available
immediately
when
the
video
goal
line
goes
live,
it
will
be
available
as
part
of
a
bigger
a
sample
slightly
later.
But
thank
you
for
watching
and
please
keep
the
feedback
coming
around
this
one
and
thank
you
Paul
for
the
great
demo.
Thank
you.