AppSource App Previews
Installing preview versions of AppSource apps in Business Central: how publishers set a preview key in Partner Center and share an install URL, and how administrators install, update and monitor previews. Covers sandbox-only installation, the highest-version rule, breaking changes between previews, and telemetry.
- Introduction to AppSource Preview Versions
- Overview for Publishers and Administrators
- Setting Up Preview Keys and Installation URL
- AppSource Publishers - Preview Version Behavior
- Publishing Options and Breaking Changes Policy
- Administrator Capabilities and Environment Restrictions
- Telemetry and Closing Remarks
Overview
The video explains how AppSource publishers can make preview versions of their extensions available to selected customers before public release. Publishers specify a preview (hide) key in Partner Center, or get one generated automatically if they do not set one during submission. They then build an installation URL that contains the tenant ID, app ID and preview key.
It also covers the administrator side. Previews can only be installed on sandbox environments and can be updated to higher previews or to public versions. Operations on extensions are logged to telemetry, including whether an installed app is a preview or public version.
Key points
- Publishers set a preview (hide) key in Partner Center; if none is given at marketplace submission, one is generated automatically and the publisher is opted in.
- The install URL contains the tenant ID, app ID and preview key, and customers use it to install a preview.
- Only a preview that is the highest version of the extension can be installed. If a public version is higher, the public version is installed even when the link has a preview key.
- Previews install only on sandbox environments, not production. Sandboxes with preview versions cannot be copied or restored to production.
- Publishers can run simultaneous previews for different offers with different preview keys, even when the offers contain the same apps.
- Breaking changes are allowed between preview versions, but must not be introduced to the latest public version.
- A preview submission must include all required dependencies, otherwise the Partner Center submission might fail.
Features
| Feature | Status | At |
|---|---|---|
| Preview Key for AppSource Apps | status not stated, demoed | 0:34 |
| Preview Version Installation URL | status not stated, demoed | 0:48 |
| Automatic Preview Key Generation | status not stated | 1:52 |
| Simultaneous Preview Versions | status not stated | 2:02 |
| Breaking Changes in Preview Versions | status not stated | 2:15 |
| Sandbox-Only Preview Installation | status not stated | 2:49 |
| Preview to Public Version Updates | status not stated | 3:05 |
| Automatic Public Version Promotion | status not stated | 3:20 |
| Preview Version Telemetry Logging | status not stated | 3:30 |
Quotes
- 0:03 “We will explore today the capabilities of installing preview versions of AppSource apps in Business Central and see how you can leverage this to”
- 1:30 “We are currently only supporting to install preview versions which are the highest version of your extension”
- 1:41 “If you have public version that is higher, even if you’re giving a link with a preview key to your customers, this public version”
- 2:15 “You will be allowed to perform breaking changes between preview versions of your extensions”
- 2:32 “when you’re submitting a preview version of your app, you should include all the required dependencies as needed.”
- 2:49 “previews can only be installed on sandbox environments. You cannot install them on production environments”
- 3:20 “Installed preview versions are automatically updated to higher public version with app update guidance setting”