Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
We have written about Marketing requirements for publishing your app on AppSource in our previous blog post here. Now we would like to introduce our Dynamics Partners about technical requirements for publishing your app on AppSource. If you do not have enough resources in-house, Simplanova offers our services: Add-on migration to AppSource, Add-on Development, Upgrades for Add-ons to Extensions and much more. Contact us and get a free project evaluation.
You can bring two types of offerings to Microsoft AppSource:
There are several things to keep in mind in when building an Add-on App. The following checklist sums up all the technical requirements that you must meet before submitting an Add-on app for validation. If you do not meet these mandatory requirements, your app will fail validations. We are sharing the information from Microsoft and what our team learned during Directions EMEA 2018.
The following is a checklist of all requirements that you must meet before submitting an extension for validation. If you do not meet these mandatory requirements, your extension will fail validation.
Visual Studio Code and the AL Language extension lets you do the following tasks:
In an AL project there are two JSON files; the app.json file and the launch.json file. These files are generated automatically when you start a new project. The app.json file contains information about extension that you are building, such as publisher information and specifies the minimum version of base application objects that the extension is built on. Often the app.json file is referred to as the manifest. The launch.json file contains information about the server that the extension launches on.
The settings in the app.json file
More settings in the app.json file you can find here.
The following table describes the settings in the launch.json file. The launch.json file has two configurations depending on whether the extension is published to a local server or to the cloud.
Publish to local server settings
Publish to cloud settings
Marketing requirements for publishing your app on AppSource we have published in our previous blog post and Technical requirements we have listed above are just the few parts you need to know to make your app live in AppSource. Before publishing it, there are many things to know and learn in the development phase. Simplanova has 6+ years experience delivering successful upgrade and development projects to Dynamics Community (100+ customers worldwide). Become a successor with your project and get a free quote on Add-on Upgrade to Extensions, Dynamics NAV Extension Workshop, Extension /AL Development, Add-on Development, Add-on migration to AppSource.
The post What are the Technical Requirements for Publishing your App on AppSource? appeared first on Simplanova.
Business Applications communities