Join Gini von Courter for an in-depth discussion in this video Launching the app, part of Creating Access Web Apps in SharePoint 2013.
- This app feature is amazing because if the tables that we have are exactly the tables that we want, we're ready to go. We don't to do anything else to tweak this. Now we could, and let me show you where we would do that. We have different forms that are available to us. There's a List Form, which allows us primarily to enter data or view records one at a time, and a Datasheet view and there's also a view here that's By Status. This Edit button allows us to edit any of those views. So those have been built. In the Customer table, again we have three views.
In the Employees table, we have three views as well. As you'll see in a moment, these two other tables, Issue Comments and Related Issues, they're dimmed out because in the app itself, they're not going to be visible as navigation choices. But they also have views. When we built this app, it built more than just these tables and views. If you click the Navigation Pane button in the Show group, you'll notice that we have a fistful of forms here that are available as well as the five tables, so By Group and so on.
It's a very complex app already. Let's launch it and see what happens. Notice that we're Working on it, but really fast, it's right here. Let's just take a quick test drive. It's here within SharePoint. It came up in my default browser. I can go back to my site and where it will actually take me is to the team site where this is located. But here I am in my Issues app. Again I have navigation for the tables that are visible, Issues, Customers, and Employees.
I have the ability to enter information. Notice that I can begin typing here if I wish. I have the ability to filter this list. I can save an item once I've created it. I can add an image here. I have Customers and I have Employees I can enter. So I have a functional app that I could begin using right now, but this isn't exactly how I want it to look. I want to do some work to make sure that this form, which my folks will be using a lot, is a little better to look at and has entire labels instead of Emergency Con....
I'll also want to make sure that I've done the same with the Issues list. In my case all of my Issues are going to be raised by Employees, so I'm not going to have Customers in here at all, and we'll be deleting that table. But notice that if what I wanted was a system where employees took complaints or issues from customers and entered them here, and we wanted to enter customers, I'd be ready to go. I've invested all the time I need to have an app that runs in a browser that quickly created in Access.
- 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
Q: The "Using the If macro action" movie seems to end in the middle of troubleshooting. What am I missing?
<div>A: You’re right—and a replacement movie is on the way. In the meantime, here is the solution:</div><div> </div><div>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. </div><div> </div><div> 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: </div><div> </div><div>If [RecordFound] =”Yes” Then</div><div> </div>