►
From YouTube: New Virtual Table Creation Wizard in Maker Portal
Description
In this 25 minute demo, Frank Lan (Power Apps Maker Portal) and Nathan Helgren (Dataverse) walk through the new virtual table creation wizard in maker portal. We start with a description of what virtual tables are, how they work, and what life looked like before the creation wizard. Then Nathan and Frank demonstrate the creation process for SharePoint lists and SQL tables, respectively. Try the virtual table creation experience at make.powerapps.com. This video was taken from the January 11, 2023 Power Platform Integrations / Connectors LABs Call.
Nathan Helgren (Microcosft) | linkedin.com/in/nhelgren
Frank Lan (Microsoft) | linkedin.com/in/frankwlan/
Supporting materials
https://powerapps.microsoft.com/en-us/blog/virtual-tables-creation-wizard-now-in-public-preview/
https://learn.microsoft.com/power-apps/maker/data-platform/create-virtual-tables-using-connectors?tabs=sql
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/setup-virtual-table-relationships?branch=pr-en-us-7468
https://youtu.be/weyEDIKhi18
Learn more about Power Platform Connectors
https://github.com/microsoft/PowerPlatformConnectors
https://learn.microsoft.com/en-us/connectors/
A
Now,
to
jump
into
our
first
educational
session
of
the
day,
I
am
really
excited
to
announce
Nathan
helgren's
senior
PM
from
dataverse,
as
well
as
Frank
lawn
senior
PM
for
power
apps.
For
this
awesome,
really
new
I
I
think
you
guys
just
announced
it
like
yesterday
or
or
earlier
this
week
about
creating
virtual
tables
in
minutes
inside
of
the
maker
portal.
So
excited
to
have
you
guys
here
I'm
going
to
stop
screen
sharing
and
take
it
away
when
you're
ready,
hi.
C
Yeah
thanks
Nathan,
hey
everybody
good
morning,
Jocelyn
thanks
again
for
having
us
here:
I'm
Frank,
land,
I'm,
a
PM
and
maker
portal
for
powerapps.
So
basically
that's
when
you
go
to
make
that
power
app,
so
we're
looking
at
those
interactions.
I
work
really
closely
hand
in
hand
with
Nathan
on
dataverse
experiences
for
our
makers
so
making
the
table
Hub
table
designer.
All
of
these
things
better
for
makers,
I'm
going
to
be
talking
about
virtual
tables
in
the
new
creation
wizard
that
we
have
in
the
maker
portal
Nathan.
C
Great
and
so
what
are
virtual
tables?
This
is
a
way
of
creating
dataverse
tables
from
data
that
isn't
stored
in
databers.
We
can
actually
connect
to
external
data
sources
like
SQL
and
SharePoint
grab
that
data
use
it
in
memory
and
represent
that
data
in
dataverse.
So
let's
use
an
example,
let's
say
you
have
a
list
in
SharePoint
that
your
team
members
are
using
to
enter
information
every
day.
C
You
can
actually
use
that
data
in
a
virtual
table
without
migrating
that
data
over
from
SharePoint
right,
because,
presumably
everybody's
going
through
that
list
of
entering
that
information,
you
don't
want
to
just
move
it
to
dataverse,
but
now
you
can
actually
use
dataverse
to
represent
that
data.
Virtually
here's
some
of
the
features
we
can
integrate
that
data.
Once
you
make
it
a
virtual
table
with
other
tables
and
dataverse
using
relationships.
C
The
data
is
actually
accessed
through
metadata,
so
you're
not
using
meaningful
storage
space,
you're
saving
on
space
and
the
other
great
thing
is
virtual
tables.
Allow
for
crud
operations,
that's
create,
read,
update,
delete
if
the
source
allows
it.
So
it's
keeping
these
tables
in
sync
between
the
source
in
between
date
numbers.
C
You
can
think
that
you
might
want
to
use
this.
We've
we've
heard
a
lot,
for
example,
folks,
who
use
model
driven
apps
today,
model
driven
apps
are
built
off
of
dataverse
tables,
so
it's
not
very
easy
to
use
data
that's
stored
in
SQL
or
SharePoint.
Some
people
are
doing
that
by
jumping
through
a
couple
Hoops
they're,
integrating
with
power
automate,
for
instance,
now
with
virtual
cables.
Once
you
create
a
virtual
table
from
your
Source,
you
do
not
need
to
do
additional
steps
in
your
integration.
B
Sure,
and
just
before,
I
jump
into
this
for
a
moment,
I
wanted
to
throw
just
one
other
piece
of
information.
So
since
this
team
is
very
familiar
with
connectors
and
the
use
of
connectors,
sometimes
what
we'll
hear
from
people
is
well,
why
don't
I
just
use
a
direct
connector
instead
of
a
virtual
table
and
kind
of
one
of
the
things
that
Frank
talked
about
a
moment
ago
is
one
of
the
key
benefits
is
easy
integration
between
data
sources?
B
So
when
you
have
a
direct
connection
to
SharePoint
or
SQL
you're
pulling
the
data
from
SharePoint
or
SQL,
and
that's
what
you
can
do
with
it,
but
with
a
virtual
table
you're
easily
able
to
make
relationships
between
different
tables
and
dataverse.
So
you
could
have
a
single
table
in
dataverse
that
integrates
data
from
both
SharePoint
and
SQL
into
a
single
table
by
using
the
virtual
connector
providers
that
we
have,
and
that's
kind
of
the
difference
here
that
we
have
with
the
virtual
creation
experience
that
I'm
about
to
talk
about.
B
So
before
we
created
virtual
connector
providers
and
I
like
to
call
this
the
before
times
this
is
pre-october
2021.
Anybody
who
was
going
to
build
a
virtual
table
had
to
write
code.
You
had
to
basically
write
plugins
for
every
single
operation.
You
wanted
to
do
and
you
had
to
connect
the
dataverse
API
to
the
API
on
the
source.
There
was
so
many
Clicks
in
the
process.
It
was
a
long
r2s
process.
B
You
had
to
register
things
with
Azure
and
it
could
take
days
two
weeks
to
get
your
virtual
table
to
work,
and
you
know
that's
actually
what
we
people
do
today
for
all
their
manual
created
or
custom
created
connections
for
virtual
tables
as
well
about
a
few
months
ago.
Well,
maybe
closer
to
yeah.
Almost
a
year
ago,
to
a
few
months
ago,
we
had
virtual
connector
providers
launched
so
the
difference
between
a
virtual
connector
provider
and
a
standard
connector
is
that
we
do
a
lot
of
the
work
for
you.
B
So
we
handle
all
that
plug-in
creation.
We
handle
all
the
registration.
We
do
a
lot
of
that
background
work
so
that
way,
when
you're
connecting
to
something
that
has
a
virtual
connector
provider,
you
don't
have
to
take
all
the
additional
steps
in
order
to
build
the
virtual
table.
Right
now
we
have
a
SharePoint
and
SQL
available
as
part
of
our
newest
functionality.
B
Excel
also
uses
a
virtual
connector
provider,
and
but
when
we
release
this
functionality
between
October
2021
and
may
of
2022,
we
made
some
changes
number
one,
no
more
code
needed
so
you're
able
to
do
this
without
building
your
plugins.
We
remove
the
clicks
down
to
about
40
clicks
so
before
I
had
to
do
all
the
coding.
Now
you
had
about
like
40
different
clicks
across
six
different
pages,
including
the
admin
Center
to
build
these.
B
B
So
now
we
have
what
we
just
released
and
we
we
it
went
into
production
last
Friday.
It
is
announced
in
our
blog
and
other
information
yesterday,
which
is
the
new
user
experience,
so
Frank's
team
and
my
team
got
together
to
make
the
experience
even
better.
So
we
had
the
15-minute
experience
we
wanted
to
make
that
faster.
We
want
to
make
that
cleaner
and
so
again
it's
still
no
code,
but
now
you
can
build
a
virtual
table
in
as
few
as
10
clicks.
B
You've
got
a
single
wizard,
so
you're
not
going
to
multiple
different
places.
You
can
customize
your
table
and
column
names
which
you
couldn't
do
before,
and
you
can
build
this
virtual
table
in
about
two
and
a
half
minutes.
So
you
know
going
from
weeks
of
work
to
two
and
a
half
minutes
is
a
big
leap.
Excel
will
be
coming
shortly
for
this,
so
SQL
and
SharePoint
are
in
Pre
in
public
preview
right
now,
Excel
is
going
to
be
coming
up
shortly
and
then
later
we're
going
to
be
adding
additional
enhancements
to
the
experience.
B
So
two
other
things
to
note
here
before
I
jump
into
a
demo
is
two
other
things
you
couldn't
use
the
SQL
virtual
table
connections
for
easily
that
you
can
do
with
our
new
experience.
Is
you
can
connect
to
SQL
views
as
well,
so
you're
able
to
build
a
virtual
table
directly
to
a
SQL
view,
which
is
a
read-only?
Of
course,
you
don't
have
full
cred
and
you're
also
able
to
build
a
virtual
table
that
connects
to
SQL
synapse
analytical
table.
B
So
if
you've
done
any
experimenting
or
any
work
with
using
SQL
synapse
to
take
data
Lake
data
into
SQL
to
represent
it
as
a
table,
you
can
build
a
virtual
table
against
that.
So
now
you
have
a
virtual
table
talking
to
a
SQL
virtual
table
that
pulls
out
of
a
data
Lake,
and
so
it
kind
of
improves
that
process
as
well
to
make
it
easier
to
use
that
data
within
apps,
so
I'm
going
to
jump
into
a
demo
here,
and
so
this
is
my
dataverse
environment.
B
I
had
connected
to
powerapps,
and
so
what
I
have
is
a
list
in
sharepoints
we're
doing
a
SharePoint
list?
I've
got
a
list
of
all
my
customers
and
that
I
use
for
my
company
and
people
access
this
all
the
time
and
make
changes
and
edit
it.
Not
all
those
people
have
powerapps
access,
so
I
need
to
keep
the
SharePoint
site
active.
So
what
I
want
to
do
is
I
want
to
build
a
virtual
table
I'm
going
to
go
from
tables
to
build.
B
This
you
can
also
do
it
directly
from
a
solution,
but
from
tables
you'll
see
now,
when
you
click
new
table,
you'll
have
an
option
to
build
a
table
from
external
data.
So
this
means
something
that's
not
part
of
the
relational
data
of
dataverse.
So
when
I
click
this
we
get
a
nice
little
wizard.
That
appears
and
the
two
options
that
we
have
of
course
are
SharePoint
and
SQL.
As
we
mentioned
later,
Excel
will
be
here.
B
If
you
still
need
to
do
the
process
of
going
through
a
manual
process
to
build
a
custom,
we
have
a
link
that
takes
you
to
the
process
information
on
how
to
do
a
Custom
Creation,
but
this
wizard
specifically,
is
just
for
virtual
connected
providers.
I
can
pick
my
SharePoint
connection.
You
could
also,
if
you
don't
have
one
already
created,
you'll,
have
a
prompt
to
create
a
new
connection.
B
One
thing
I
want
to
call
out
here
is:
you
can
choose
to
manually
configure
your
connection
reference
so,
for
example,
if
I'm
using
SharePoint?
Oh
sorry,
okay
click!
Next
I
can
tell
it
to
use
an
existing
connection
reference
if
I
have
one
in
existence
or
I
can
create
a
new
one.
The
only
benefit
here
really
is
you're
naming
it
so
the
connection
reference
we
go
through
the
process
of
actually
creating
it.
For
you
all
the
steps
we
just
give
you
the
option
to
give
it
a
friendly
name.
B
So
if
you
wanted
to
give
it
a
more
easily
recognizable
name,
so
you
can
manage
that
as
part
of
your
Alm.
Then
you
can
come
here
and
do
that.
If
you
choose
not
to
do
that,
though,
and
you
take
that
check
box
away,
it's
just
going
to
generate
an
automatic
name
for
you,
so
the
next
step,
I
click
and
because
I'm
doing
SharePoint.
It
wants
me
to
either
paste
my
SharePoint
URL
or
through
graph.
B
It's
going
to
pull
all
of
the
recently
accessed
SharePoint
sites
that
I
have
based
on
my
aad,
so
I'm
going
to
find
the
one
I
want
to
use
here
and
just
click
it,
and
then
the
next
thing
is
going
to
do.
Is
it's
going
to
look
at
that
and
show
me
all
the
lists
I
have
access
to.
So
here
are
all
my
lists
on
this
site,
and
so
I
want
to
be
able
to
do
my
Master
list
for
customers
and
resellers,
and
then
I
have
an
option
here.
B
I
want
to
configure
my
tables
or
columns
if
I
don't
care
what
the
tables
and
column
names
are.
I
can
turn
this
off
and
it
saves
me
a
step,
but
I
want
to
show
you
the
screen,
so
click.
Next,
it's
going
to
go
back
and
retrieve
all
of
the
details
about
my
list
to
show
me
what
it's
going
to
look
like
when
it
goes
into
dataverse.
B
So
here
I
have
the
name,
the
plural
name,
the
schema
name,
so
I
can
change
any
one
of
those.
At
this
point,
I
can
go
to
the
primary
field.
I
can
pick
any
one
of
my
text
Fields
as
my
primary
field
and
then
I
also
have
a
list
of
these
are
all
the
columns
that
are
going
to
appear.
So
these
are
the
columns
as
they're
named
in
SharePoint
that
it
gives
me
what
it
thinks.
The
display
name
is,
and
the
schema
name
so
you'll
notice
here
that
you
know
the
for
the
display
name.
B
It's
calling
this
customer
email,
but
the
column's
name
field,
one,
that's
because
in
SharePoint
it
was
called
field
one
and
they
just
put
a
label
on
top
of
it
called
customer
email.
So
it
assumes
that's
what
you
want
the
display
name
to
be,
but
the
schema
name
is
just
pulling
exactly
from
the
schema
name.
So
I
can
make
any
changes
here
that
I'd
like
to
make
another
option.
B
You
have
is
quick
format,
and
this
really
is
kind
of
implements
some
changes
that,
if
you're
using
SQL
and
it
has
a
prefix
at
the
beginning
of
it-
it'll
go
and
clean
up
some
of
these
I.
Don't
know
if
it's
going
to
do
anything
here
for
SharePoint,
let's
see
yeah,
it
didn't
make
any
suggested
changes,
but
just
for
the
purpose
of
this
I'm
going
to
change
one
of
these,
so
you
can
see
that
it
makes
the
change
and
then
I
click.
B
Next
and
now
it's
going
to
show
me
the
set
so
I'm
coming
from
SharePoint
this
the
list
I'm
using
I'm
going
to
dataverse.
This
is
the
naming
I'm
using
how
many
columns
I'm
moving
over
what
my
primary
column
is.
If
I'm
great
I
can
click
finish,
if
not
I
can
click
either
one
of
these
to
go
back
steps
and
make
make
modifications.
B
So
if
I
skip
that
naming
process
and
I
look
here
and
I,
don't
like
the
primary
column
that
was
picked,
I
can
go
back
to
the
configuration
page
and
go
ahead
and
make
modifications
before
I
move
forward.
So
from
here.
I
click
finish
and
now
it's
creating
my
virtual
table.
Ironically,
this
is
the
longest
part
of
the
process
and
even
though
we
went
from
you
know,
15
minutes
or
two
weeks
down
to
two
and
a
half
minutes.
It
seems
like
this
takes
a
long
time
because
we
just
clicked
through
a
bunch
of
screens
really
fast.
B
We
are
working
on
performance
enhancements
on
this,
but
realistically
this
does
take.
You
know
very
little
time.
You
know
maybe
a
minute
to
90
seconds,
typically
for
the
creation
process
and
as
soon
as
it's
done,
creating
it's
going
to
drop
me
directly
into
my
virtual
table
and
I'll,
be
able
to
see
my
data
and
manipulate
that.
So
you
can
see
do
that
here
in
just
one
second.
So
while
this
is
finishing
up,
I'll
open
up
to
one
or
two
questions
that
was
before
I
finish
up
the
demo.
C
B
B
Okay,
so
right
now
we
the
ability
to
build
virtual
connector
providers,
is
only
internal.
However,
we
are
investigating
some
other
possibilities.
Number
one
is
we're
expanding
our
off
looking
to
expand
our
offerings,
Beyond
SQL
SharePoint
in
Excel,
but
also
there
has
been
requests
and
we
are
concerned
considering
the
ability
of
making
the
ability
to
build
these
virtual
connector
providers
open
to
isvs
as
well.
B
So
that
is
something
we're
considering
Nick
and
you
know
maybe
we'll
have
more
information
for
you
in
the
future.
Oh
thank
you.
Nathan
so,
as
you
see
here,
I
have
got
my
table.
I
got
my
data
in
it
already
so
I
can
go
here
and
just
say:
hey
I
want
to
show
some
more
of
my
data
here
and
I'm
connected
directly
to
my
virtual
table
and
SharePoint.
So
this
is
all
my
data,
and
even
here
so
now,
I'm
connected
I
can
go
make
a
modification.
B
So
let's
see
I'm
going
to
pick
Andrea
so
I'll
make
sure
I
know
who
she
is
next
time
and
come
on.
It's
gonna,
be
it's
not
a
demo.
If
something
doesn't
go
wrong,
all
right
for
right
now,
I'm
just
going
to
change
this
I
will
change
this
to
Colorado
just
for
purposes
of
this,
it's
going
to
save
and
then,
when
I
jump
back
over
to
by
list
here,
so
we've
got
Andrea
who's
in
Washington
and
when
I
refresh
this
shows.
Oh,
it's
probably
still
saving.
Oh
there
we
go
it
changed.
B
So
Andrea
is
now
from
Colorado.
So
you
can
see
that
the
data
I'm
pulling
is
directly
from
the
virtual
table.
It's
a
full
connection.
I
can
build
apps
on
this.
I
can
do
everything
else.
I
want
with
this,
has
full
connectivity
and
now
I
can
drop
this
into
any
app
I
want.
I
can
link
it
to
any
dataverse
table,
I
want
it's
ready
for
use,
and
so
that's
as
quickly
and
easily
as
you
can
make
any
of
these
virtual
tables.
Using
this
new
experience.
C
C
Okay,
so
folks
should
be
able
to
see
a
split
screen
here
between
my
sequel,
ssms
and
the
virtual
table
wizard
on
the
right,
so
I'm,
looking
at
just
a
SQL
database
here
and
I'm
interested
in
bringing
this
table
sales
LT
schema
sales
order
details
over
to
my
database
environment
and
here
are
the
column
there.
So
we'll
walk
through
a
very
similar
process.
That
Nathan
was
showing
just
going
to
go
ahead
and
connect
to
that
server
and
now
I'm
going
to
look
for
this.
C
C
Give
that
a
moment
all
right,
so
my
columns
are
coming
through,
as
folks
can
see
sales
order,
ID
order,
detail,
ID,
it's
all
here,
as
Nathan
mentioned
before,
when
you're
using
SQL.
You
know
you're
you're
coming
into
here
with
a
lot
of
schema.
Folks,
don't
want
that.
We
can
take
that
away
with
a
quick
format
of
names,
so
you
can
see
how
that's
changed
I'm
going
to
hit
next,
it's
going
to
do
a
quick
review,
we're
going
to
verify
Yep.
This
is
the
server
and
database
I'm
coming
through
and
I'm
pulling
in
these
fields.
A
C
C
Back,
oh
sorry,
you
you
switched
before
okay
yeah
I
switched
a
little
bit.
I
I
knew
we
were
going
to
have
to
wait
for
a
little,
so
here's
another
table
that
I
had
pulled
just
right
before
the
the
call.
So
this
is
slightly
different
table
sales
order,
header
which
is
down
here,
but
I,
wanted
to
show
people
this.
C
There
we
go
okay,
so
we're
pulling
our
columns.
It's
going
to
start
displaying
the
the
top
rows
here
and
we've
got
our
data
just
like
what
Nathan
was
showing
with
the
SharePoint
situation:
okay,
I'm,
coming
back
to
sales
order.
We
have
that
here
as
well.
I'm
just
going
to
show
everything
here.
We
go.
C
C
Yeah
because
I
know
we
had
a
question
on
this.
So
if
we
go
to
slide
yeah
there
we
go
so
I'm.
Just
taking
a
couple
screenshots
from
my
own
synapse
environment
in
in
synapse,
you
can
actually
have
external
table.
So
in
this
situation
my
data
engineer
has
some
data
that
are
stored
on
parquet
files
and
we
want
to
expose
that
in
SQL
and
so
he's
helping
me
to
do
that.
Based
on
this
construct
and
synapse
called
external
tables.
C
Virtualizing,
that's
parquet
data
inside
SQL,
Nathan,
Next
Step,
please
so
folks
for
folks
who
are
using
SQL
external
tables
with
synapse
they're
able
to
connect
to
those
external
tables
through
SQL,
just
like
what
I've
done
and
then
using
the
process
that
I
just
showed
with
SQL.
You
can
actually
connect
directly
to
that
data
that
you
have
in
synapse.
C
That
was
originally
a
parquet
file
yeah
and
they
said,
if
you
just
kind
of
scroll
through
the
slides
here,
I'm
going
through
the
exact
same
process
that
I
was
showing
of
setting
up
the
connection,
picking
the
right
table
and
if
you
keep
going
we're
getting
that
data
to
come
through.
So
really
there's
not
a
difference.
When
you're
doing
this,
the
SQL
process
for
the
SQL
external
tables
from
synapse
all
right.
B
C
B
You
then
great
thanks,
so
I've
got
a
couple.
Slido
questions
I'd
like
to
pose
to
you
So,
based
on
the
new
experience
we've
done,
I'd
like
you
to
use
slider,
you
can
either
go
to
slider.com
and
use
the
code
or
you
can
use
your
QR
Reader,
but
we'd
like
to
know
how
likely
you
are
to
use
or
try
virtual
tables
based
on
the
improved
experience.
So
just
take
a
moment
here
for
you
to
jump
in
and
give
your
thoughts
but
yeah.
B
B
So
let's
give
us
another
couple
moments
for
folks
to
to
provide
thoughts
on
that
I
want
to
throw
out
one
other
piece
of
information
that
we
didn't
cover
here,
while
the
slido's
being
voted
on,
which
is
that
another
thing
that
we
came
out
with
last
month
back
in
December
is
the
ability
for
users
to
use
a
custom,
multi-table,
lookups
or
polymorphic
lookups
to
include
virtual
tables
in
them.
So
in
case
you
haven't
seen
the
blog
post
on
that.
B
A
B
So
the
next
question
is:
what
do
you
feel
is
missing,
so
we
just
showed
you
how
we
made
the
experience
easier
for
SQL
and
SharePoint
and
reduce
the
time
you
needed
and
gave
you
some
new
features.
So
is
there
anything
that
you
feel
is
missing
from
this
experience
for
us
to
consider,
as
we
continue
to
look
to
improve
virtual
tables
and
the
creation
experience.
B
A
security
model
on
Virtual
tables,
oh
good
question,
so
right
now,
virtual
tables
are
still
organizational
or
organization
owned,
so
we
are
reviewing
other
ways
to
handle
security
through
token
authentication.
That
is
something
that
you
know
would
be
a
future
feature
that
we're
investigating
I.
Don't
have
a
timeline
for
that,
but
we
are
aware
that
people
have
asked
for
additional
Security.
Even
you
know
requesting.
B
Can
there
be
user
owned
or
group
owned,
so
there
are
investigations
being
done
on
Virtual
tables
for
there
creation's
cool
overall
feature
too
many
partners
are
asking
a
security
model
same
question:
I
got
that
try
for
myself
before
I
can
say:
what's
missing,
how
do
we
provide
feedback?
Okay,
so
for
feedback.
After
attempting
it
a
couple
different
ways
you
can
go
on
to
the
communities.
You
can
go
to
ideas,
you
can
just
contact
me
or
Frank
directly
with
your
feedback.
You
can
go
through.
B
You
know
one
of
the
other
various
channels
you
can
use
my
LinkedIn
I'm,
totally
open
to
any
feedback
on
the
functionality.
If
you-
and
if
you
don't
see
like
a
blog
post
or
something
that
you
want
to
comment
comment
on,
you
can
just
you
know
message
me
directly
and
Link:
it
LinkedIn
with
the
feedback,
and
we
can
discuss
it
nice
to
know
about
the
caching
and
expectations
and
data
is
available.
Data
is
real
time,
so
it's
we
don't
cache
it.
It
pulls
fresh
every
time
you
access
the
table
and
do
the
the
refreshes.
B
There
aren't
any
required
Fields,
more
sorting
and
filtering
options.
I'd
like
to
hear
more
about
that.
If
you
want
to
provide
some
more
details,
maybe
you
know
either
in
the
chat
here
or
you
can
drop
it
into.
You
know
LinkedIn
or
something
to
give
me
some
more
information
there
documentation.
Yes,
there's
a
blog
post
Frank
can
drop
that
into
the
chat
right
now.
We
recently
released
the
blog,
which
has
online
documentation
updates,
as
well
as
some
videos
and
we'll
bi-directional
ETL
be
available.
I'm.
Sorry
ETL.
B
That
is
something
that
we
would
have
to
evaluate
separately,
and
so
that
is
let's
talk
about
this
separately
said
you
can
go
ahead
and
send
some
messages
with
information.
We
can
evaluate
that.
Can
we
use
relationships
using
virtual
tables,
if
you
mean
relationships
between
the
actual
tables
like
from
two
SharePoint
tables,
if
they're,
on
the
same
at
the
same
connector
connection
reference,
you
can
have
a
relationship
between
those
tables.
B
You
can't
relate
the
different
virtual
tables
from
different
sources
to
each
other
to
each
other,
but
you
can
go
through
a
dataverse
table
as
a
local
table
and
have
relationships
that
way
would
be
a
white
paper
be
accessible
for
performance
on
scale.
That's
a
good
question.
We
don't
have
information
on
that
at
the
moment.
B
Let's
talk
offline
to
see
what
kind
of
information
you're
looking
for,
and
we
are
working
on
performance
right
now,
just
as
a
reference
point
that
overall
table
performance
and
virtual
table
performance
is
something
that
we're
focusing
on
for
sure.
I
want
to
make
sure
that
I
leave
enough
time
for
the
next
speaker.
So
thank
you
all,
please
feel
free
to
drop
more
stuff
in
the
chat.
We
can
review
that
later
and
thank
you
so
much
for
your
time
and
I'll
turn
it
over
to
the
next
speaker.
A
Awesome,
thank
you
so
much
Nathan
and
Frank
for
this
session.
This
was
clearly
very
valuable
and
I'm
so
excited
to
see
how
many
interested
questions
we
had.
This
was
really
great
engagement.
Thank
you
guys
so
much.
This
was
like
a
hot
off
the
press,
update
that
we
were.
You
know
first
to
hear
it
here.