►
From YouTube: Latest on Microsoft Graph Explorer
Description
In this 14-minute developer-focused demo, Kristen Womack and Vivian Adhiambo highlight 3 new MGT features - Pagination (with odata.nextLink- ability to efficiently navigate through large collections of paged data), Expand Window (view more content in UI as needed) and Resource Explorer (access Graph resources more easily – select API nodes and see underlying API query options). See where to report a bug or suggest a feature. Q&A. This PnP Community demo is taken from the weekly Microsoft 365 Platform Community call recorded on October 5, 2021.
Demo Presenters:
• Kristen Womack (Microsoft) | @kristen_womack
• Vivian Adhiambo (Microsoft)
Supporting materials:
• Repo - Microsoft Graph Explorer V4 | https://github.com/microsoftgraph/microsoft-graph-explorer-v4
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
B
You
for
that
kristen
and
thank
you
so
much
sebastian
for
the
invitation,
so
my
name
is
vivian
adiambo
and
I'm
one
of
the
engineering
managers
in
microsoft,
graph,
developer,
experience
team
and
I'm
actually
super
thrilled
to
be
joining
this
session.
Actually
it's
my
first
session,
so
I
was
actually
caught
by
surprise
yesterday
when
sebastian
you
tweeted
about
it.
B
A
But
we
want
to
leave
time
for
community
conversation
about
things
that
you
really
love
about
graph
explorer
places.
There
are
friction
things
that
you
think
are
needed
in
graph
explorer
and-
and
we
want
to
leave
this
as
really
like
an
open
conversation,
so
first
we'll
start
with
pagination
and
so
we're
gonna
flip
over
to
the
demo
in
graph
explorer.
A
If
you
were
to
select
a
sample
query
on
the
left
like
get
mail,
something
that
has
a
long
collection
that
you
would
need
to
go
through
several
pages
of
results
set
in
the
past.
What
would
happen
is
you
would
have
to
if
you
want
to
go
ahead
and
click
get
my
mail,
then
you'll,
see
at
the
end
of
the
query,
parameter
there's
parameters
that
are
added
that
show
going
through
each
of
those
and
right
now.
What
we've
added
is,
if
you
click
the
link
to
follow
this
link.
A
We've
added
odata
next
link
properties
in
the
query
response,
and
this
is
to
improve
the
navigation
experience
when
moving
through
large
collections.
So
some
queries
will
return
multiple
pages
of
data,
and
this
is
either
due
to
service
side,
paging
or
use
of
the
top
query
parameter,
and
this
will
specifically
limit
the
page
design.
So
this
is
really
by
design,
but
how
you
move
through
it
now
is
a
little
bit
more
automated
in
graph
explorer.
A
So
when
the
result
set
has
multiple
pages
now
graph
returns,
the
odata
dot
next
link
property
in
the
response,
and
that
contains
a
url
to
the
next
page.
So
this
will
save
a
lot
of
manual
construction
of
graph
queries
on
graph
explorer
by
just
clicking
the
link
property
right
there,
all
right
and
next
we
are
going
to
show
you
the
expand
window.
A
So
we've
given
an
option
here
where,
if,
for
example,
you're
on
modify
permissions,
you
can
expand
that
window
and
vivian
is
going
to
pull
it
up
and
down
a
few
times
to
show
you
that
it
you
get
more
space
to
use
that
real
estate
as
you're
working
with
either
the
request
body
request,
headers
or
modifying
permissions
or
the
access
token.
So
you
can
yeah
give
yourself
a
little
bit
more
real
estate,
then
close
it
back
up
when
you're
done,
giving
more
flexibility.
A
B
Thank
you
so
much
kristen,
so
resource
explorer,
as
christine
has
mentioned,
is
one
of
the
latest
features
that
we're
trying
to
add
to
graph
explorer
so
what
resource
explorer
entails,
as
the
name
suggests.
Of
course,
it's
it's
one
of
those
functionalities
that
will
provide
the
different
graph
explorer
users
with
a
different
access
in
terms
of
resources
of
graph
api
itself.
So
so
what
I'm
showcasing
right
now,
as
christian
mentioned,
is
what
we
have
on
preview
and
we
are
planning
to
have
it
as
one
of
the
tabs
where
the
sample
queries
are.
B
So
when
you
look
at
this
the
left
side
of
the
graph
explorer
window,
you
can
see
the
resources
part
and
then
it's
going
to
be
something
like
a
tree
like
this.
So
I
know
a
lot
of
people
may
be
asking
so
why
resource
explorer
right
so
currently
on
graph
explorer
in
terms
of
when
it
comes
to
accessing
the
different
queries
on
graph
itself.
B
So
in
this
particular
case
of
resource
explorer,
what
you're
trying
to
achieve
is
showcase
the
different
nodes
under
graph
api
itself
and
then,
once
you
are,
you
are
able
to
select
the
specific
nodes
you
are
interested
in
as
a
user.
It
will
generate
a
request
url.
So
let's
say
if
we
selected
alice,
if
I
can
find
a
proper
node,
let's
see.
B
Yeah
so
basically,
let's
say
you've
selected
one
of
the
notes
here,
the
general
idea
is
once
you
select
this.
It
will
auto
generate
a
query
which
will
be
you'll,
be
able
to
see
on
the
run,
query
text
area,
and
then
I
should
be
able
to
run
that
particular
query.
So
the
other
thing
that
you
want
to
capture
on
resource
explorer
is
once
you
select
a
specific
node
or
query.
You
should
be
able
to
see
the
different
api
changes
for
that
specific
apis.
I
know
that's
something
we
currently
don't
have
on
graph
explorer.
B
So
what
we
have
in
terms
of
the
change
log
only
captures
what
has
generally
changed
on
graph,
but
with
resource
explorer.
To
some
extent,
you
will
be
able
to
access
what
has
specifically
changed
for
a
specific
api
and
also,
as
you
continue
as
a
user,
to
explore
the
different
nodes
under
resource
explorer.
You
should
be
able
to
see
what
are
the
different
query
options
that
map
to
this
particular
graph
api,
so,
for
example,
you'll
be
able
to
see
for
this
particular
node,
which
maps
to
this
specific
api.
B
These
are
the
different
query:
options
that
you
can
use
to
run
the
query,
so
I
believe
we
can
take
questions
in
terms
of
what
we
just
presented
so
far.
So
this
is
something
we
are
planning
to
roll
out
the
resource
explorer,
at
least
within
the
next
two
or
three
months,
and
I
hope
everyone
will
be
really
really
excited
and
be
able
to
see
the
value
in
terms
of
being
able
to
access
all
the
different
resources
on
graph
using
graph
explorer.
C
B
B
B
Yeah,
the
other
thing
I
want
to
add
is
we
try
as
much
as
possible
also
to
label
some
of
these
tickets
as
good
first
issue,
so
that
whoever
is
interested
in
contributing
to
graph
explorer
repo,
especially
when
you
know
you
don't
have
let's
say
much
time,
but
you
really
really
want
to
contribute
to
graph
explorer.
You
will
just
come
to
graph
explorer
and
filter
by
good
first
issue
and
see
some
of
the
tickets
we
have
in
that
space
and
just
get
started
right
into
it.
A
Oh,
I
see
one
other
question:
when
is
graph
api
beta
going
to
the
next
stage.
Can
we
use
beta
api
endpoint
for
production
use?
So
we
put
newer
things
on
to
beta
and
then
v1
is
sort
of
our
feature.
That
is,
production
ready.
You
can
trust
it.
You
can
build
on
it
and
you
have
the
option
to
toggle
between
the
two
when
you're
building
and
trying
new
features,
so
there
will
always
be
a
beta
endpoint.
C
We
have
two
other
questions
that
I
think
are
super
interesting
for
graph
explorer.
First,
one
is:
is
it
possible
to
set
up
variables
or
parameter
in
graph
explorer
like
we
can
do
in
postman
today,
a
channel
like
the
user
id
or
whatsoever?
So
we
can
reuse
it
is
that
something
that
is
considered
for
graphing
explorer.
C
A
Yeah,
so
this
is
something
we
talk
about
and
think
about.
A
lot
is
like
what
is
the
value
of
graph
explorer
and
where
do
the
edges
of
graph
explore
meet
the
edges
of
postman,
because
there
are
some
reasons
and
some
preferences
and
using
each
of
the
tools
for
different
things,
and
so
that's
something
that
yeah
we
we
are
thinking
about
and
we
do
talk
about
vivian.
Were
you
going
to
add
to
that
as
well?.
B
Yes,
so
as
part
of
adding
into
resource
explorer
in
terms
of
the
work
we're
doing
in
resource
explorer,
once
a
user
is
able
to
select
the
different
nodes
that
can
turn
into
different
api
queries.
One
of
the
things
we
are
trying
to
work
on
is
the
capability
to
be
able
to
export
these
queries
into
a
postman
collection
or
be
able
to
just
save
them
and
use
them
for
future
use.
C
That
is
awesome.
I
think
that
answers
the
the
question
here
and
the
last
one
that
we
have
is
is
the
graphics
floor,
a
pwa,
a
progressive
web
app
that
could
be
installed
locally.
Like
you
know,
postman
you
can
do
it
on
the
browser
or
locally
is
graph
export
right
now,
a
pwa,
or
is
there
any
plans
on
on
making
it
the
pwa
in
the
future.
C
Awesome,
well,
I
don't
see
any
other
question,
but
we're
coming
at
time
anyway.
So
I
wanted
to
thank
you
so
much
for
for
your
time
today,
kristin
and
vivian,
and
feel
free
everybody
in
the
community
to
start
continue
providing
the
feedback
on
on
the
chat,
vivian,
kristen
myself,
a
bunch
of
people
will
be
looking
at
it
and
bringing
it
back
to
to
to
the
team
to
make
sure
that
we
have
the
best
graphic
store
possible.
C
The
graphic
explorer
makes
my
work
like
so
much
easier
that
it's
definitely
something
that
I
I
want
to
be
able
to
to
see
improvements
and
we're
gonna
follow
these
improvements
to
kristin
vivian
and
our
new
pm
that
actually
started
a
couple
of
days
ago,
specifically
for
graphic
explorer
awesome.
Well,
kristin!
Vivian!
Thank
you
so
much
for
being
here
today.