- [Instructor] If you have existing Access web apps…that you need to migrate from Access to PowerApps,…then you'll want to be able to export…the Access web app tables,…so that they become SharePoint lists,…because PowerApps work with SharePoint lists,…PowerApps don't work directly with Access tables.…I'm going to walk you through the process,…and again, this is a process for folks…who are using SharePoint online.…Here's the app that we created previously.…I'm going to open the app here in my browser.…

And when the app opens,…I'm going to click on the settings gear.…And we'll find a choice to export to SharePoint lists.…And we will need to confirm this.…It says that we will be creating a subsite…with a SharePoint list for each table in our app,…do we want to continue?…Now, you need to have permission to create a subsite.…If you don't, you won't be able to proceed past this step.…

You'll need to talk with your SharePoint admin…and make sure that you have the ability to create a subsite.…And that's not something that they can do for you,…

Resume Transcript Auto-Scroll

Author

Updated

8/25/2017

Released

3/4/2015

Learn the no-code way to create powerful browser-based SharePoint apps that let users view and enter data from many sources: Access, Excel, and even SharePoint lists! Gini Courter walks through creating a simple Access web app with data imported from Excel, linked via SharePoint lists, or even from tables you create from scratch. She also shows how to define relationships between the tables in the database, create a user interface from views, use macros to automate events and calculations, and bundle your app in a package that can be installed on another SharePoint site.

Topics include:

Creating a new app

Building tables from different sources

Creating relationships between tables

Working with views

Using macros for automation

Saving your app in an app package

Skill Level Intermediate

2h 16m

Duration

107,477

Views

Show MoreShow Less

Q: The "Using the If macro action" movie seems to end in the middle of troubleshooting. What am I missing?

A: You’re right—and
a replacement movie is on the way. In the meantime, here is the solution:

The IssuesNext30Days
data macro sets a local variable, originally named ApplyFilter, equal to RecordFound.
During troubleshooting we change the name of the ApplyFilter variable to TurnOnFilter
but the name doesn’t matter. Our problem is that ApplyFilter is a local variable, so it only has value in the
IssuesNext30Days macro. We can’t use this variable in the IF condition of our
web macro.

We do, however, have a value that we can use:
the value of RecordFound. To complete debugging on this macro,
change the condition in the web macro to: