Join Gini von Courter for an in-depth discussion in this video Software needed for this course, part of Creating Access Web Apps in SharePoint 2013.
- You will need some software for this course. You'll need both SharePoint Server and Microsoft Access and you'll need to have the 2013 version of Microsoft Access. So make sure you have that installed on the machine that you'll be using. Then you need to have SharePoint Server. Either SharePoint Server 2013 or SharePoint Online as part of Office 365. This can also be hosted SharePoint Server. That works fine. But it's important what SQL Server is sitting behind SharePoint as a back end.
Although you can use SharePoint Server with older versions of SQL Server, like SQL 2008, you need to have SQL Server 2012. Now if you want to have very specific information about exactly what you need so that you can hand this off to somebody in your IT department and say, "Hey, is this what we have?" Then I would recommend that you go to the Microsoft Tech Net site. And here's a link for where you can get the information about exactly how you should configure your environment.
Having said that, if you have an Office 365 subscription, if you're using Office Online, SharePoint Online, you're all set up and won't have to do anything special. You can just jump in and start working in that particular environment. But, again, if you have SharePoint on premises and if you're concerned at all about what the requirements are, if you're asked what the specific requirements are, this is where you would find them.
- 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>