Skip navigation

Start your free trial now, and begin learning software, business and creative skills—anytime, anywhere—with video instruction from recognized industry experts.

 Start Your Free Trial Now

Saving your app as an app package

Saving your app as an app package: Creating Access Web Apps in SharePoint 2013
Saving your app as an app package: Creating Access Web Apps in SharePoint 2013

Join for an in-depth discussion in this video Saving your app as an app package, part of Creating Access Web Apps in SharePoint 2013.

Resume Transcript Auto-Scroll
Author
Skill Level Intermediate
2h 8m
Duration
159,172
Views
Show More Show 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:
 
If [RecordFound] =”Yes” Then
 

Continue Assessment

You started this assessment previously and didn't complete it. You can pick up where you left off, or start over.

Start Your Free Trial Now

Start your free trial now, and begin learning software, business and creative skills—anytime, anywhere—with video instruction from recognized industry experts.

Start Your Free Trial Now