The 'how to' guide for selling and managing SharePoint Apps built using AccessBob Piper, Kevin BellAccess teamMicrosoft

SPC338

Objectives Learn how to build and manage Access apps in the Store, Corporate Catalog, or on siteIntroduce Access apps in the Store

Key Takeaways Access apps are SharePoint appsUpdates to Access apps can now be developed and tested outside of productionAccess apps and can be sold via the Office Store

Session Objectives And Takeaways

Building an app See SPC204 Anyone can build a SharePoint App with Microsoft Access for

more detail

Creating an UpgradeSubmitting an app to the Store

See SPC232: Everything you need to know about the Office Store for more detail

Ask questions in Yammer!We’ll answer questions at the end (live and from Yammer)

Agenda

“Add-ins” of functionality for some Office programsPlaced within the document or in the task paneAccess apps can contain Apps for OfficeRelated session SPC335 – Rich extensions to SharePoint Apps using AccessApps for

Office

Fully functioning apps that run on the web within SharePointHosted on SharePoint sites in the cloudAccess apps are SharePoint AppsRelated session SPC204 – Anyone can build a SharePoint App with Microsoft Access

Apps for SharePoint

S

Demo

App in 60 seconds

SharePoint on premises

SharePoint on Office 365

Creates

Consumes

Architecture OverviewWeb Browser

Access Client

Access Services

Tables & DataSQL DB

Azure

Powerful SQL backendTable Templates to quickly create a functional appInstant Polished, Professional run time

Default ViewsBuilt in navigation & popupsCRUD

Easy to customizeEasy to share

Highlights

1) type in a new URL that includes /sites/appcatalog (e.g. https://companyname.sharepoint.com/sites/AppCatalog/)

2) click on Apps for Sharepoint in the left nav3) click on + new item4) Upload your app, and then you’ll see it in the “Apps you can add” section of the Site contents page.

O365 Corporate Catalog

Demo

Installing from Corporate Catalog

Why create an Upgrade?Bug fixApp enhancementsFeature Requests

Demo

Creating V2

When is an Upgrade Available?After some time… Always available

Demo

Upgrading to Version 2

Anatomy of an Upgrade

SQL DBSQL DBRead-Only

Anatomy of an UpgradeWhat happens behind the scenes Marks the current database (V1) read-only and makes a copy (V2)Applies the Schema changes in the DACPAC to V2Runs the On Deploy Macro

If all goes well:Deletes V1Renames V2 to the same name as V1

If there are any failures…Marks V1 back to read/writeDeletes V2

Demo

Creating V2 … the right way

Locking a tableMarking a table as “locked” does two thingsMakes the table read-onlyAll data in a Locked table is packed for deployment

Tables shipped with data will overwrite user tablesTables are locked even for author in development mode, they have the ability to unlockUse for sample data, informational tables, static/developer controlled tables

How to lock a tableLock/Unlock from a table setting callout

On Deploy Data Macro (ODDM)Special kind of data macro that is run onceWhen the app is first installedWhenever the app is upgraded

Intended purposesMigrating data between schema changesLoading sample or default data

Author controls ODDMYou must have logic to make sure the ODDM works on install and upgrade for multiple versionsODDM is a data macro that has no input parameters or return variablesCan call other data macros and can be called from data macros

How to add an ODDMFrom the Ribbon > Advanced

Creating a PackageSave as New AppSame behavior as RTM Save as PackageOption to include no data or all dataEach save give a version 1.0.0.0 and a new app ID (Forking the app)

Save as SnapshotComplete copy of the app including all data from all tablesGreat for creating copies of apps for testing or branching to a new version

Save for DeploymentOnly writes out data for locked tablesSets and saves the app title and versionOption to lock an appThis is the version you want to deploy to the store, catalog or side-loading

Packaging Options and Locking an AppFile > Save As

Locking an appWhat does a “locking” an app do?A locked App removed the “Customize in Access” link from the “gear”Helps ensure that an app has not been modified thus having the ability to be upgraded

*Any app that has been edited in the designer cannot be upgradedHelps protects the authors intellectual property

Byproducts of locking an appRemoves the ability to turn on external dataRemoves the ability to package an app, which means there is no way to make a backup

When to lock an app?If it is installed to the catalog or store you have to assume it will be installed multiple times

Demo

“Side-loading” an Access app and an Upgrade

Why “Side-Loading” is important Bypasses the catalog/storeThere are two distinct path for creating an appApps installed from the catalog/store can only be upgraded from the catalog/storeSide-loaded apps can only be updated via side-loading

Side loading an update by selecting Upgrade

RequirementsSP1 Client update for Office 2013Available now!http://www.microsoft.com/en-us/download/details.aspx?id=42017

Upgraded O365 ServerFeature is “dark deployed” we are working on enabling itWill not be available on an on prem server via SP1If you connect an SP1 client to an on prem server you will not see any of the new features

Store

See SPC232: Everything you need to know about the Office Store

Overview

O365 Users

Office 365 is Microsoft’s fastest growing commercial product ever.

Store visitors

Downloads

Why put your apps in the Store?MonetizationExposure

MonetizationIf end users buy your app, you get paid!

Minimum app price for paid apps: $1.50MSFT gets 20% off the top, developer gets the rest (after taxes)Maximum app price $999

Try & Buy

Per user fees have not been enabled for Access apps

Subscriptions

Not enabled for Access apps

ExposureYour apps can contain ads.

Excellent way for developers to gain organic growth for their own app building or consulting business.Nice upsell to offer your customers; place an add for their business in an app in the Store.

Placeholder: apps with ads

Process1) Sign up for a Microsoft Account and an

Office 365 subscription (you must have at least the Small Business Premium to get Access 2013 web apps)

2) Complete the checklist for creating a Seller Account http://msdn.microsoft.com/en-us/library/dn383068(v=office.15).aspx

3) Add your payout and Tax info in the Seller Dashboard https://sellerdashboard.microsoft.com/Application/Summary

Process4) Add your app in the Seller Dashboard https://sellerdashboard.microsoft.com/Application/Summary

What you’ll need:.app package96x96 iconSupport & Privacy linksShort & Long descriptionsAt least one 512x384 screenshot

Process

App Number Two

App Number Two

Objectives Learned how to build and manage Access apps in the Store, Corporate Catalog, or on siteIntroduced Access apps in the Store

Key Takeaways Access apps are SharePoint appsUpdates to Access apps can now be developed and tested outside of productionAccess apps and can be sold via the Office Store

In Review: Session Objectives And Takeaways

Come visit us at the Access booth in the Expo center

MySPCSponsored by

connect. reimagine. transform.

Evaluate sessionson MySPC using yourlaptop or mobile device:myspc.sharepointconference.com

© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.