Check out the latest Business Central updates!Learn about the key capabilities and features of Dynamics 365 Business Central and experience some of the new features.
Download overview guide | Watch Business Central video
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
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 | Upcoming TechTalks
Has anyone done this part of submitting an app to app source ? https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-extension-advanced-example-test
How long does it typically take to build something out to meet the requirement? It seems like something like this could be a ton of work
You need to declare the parts of your extension that mst be tested automatically and for these parts you need to create automated tests and submit them to AppSource as a separated app, together when submitting your main app. For every test scenarios you need to provide also a manual for the tester (step by step instructions for manually executing the functionalities).
How long does it take? it depends from your application, but normally not too much.
How do we include the test libraries from docs.microsoft.com/.../devenv-extension-advanced-example-test in an app,json file for an extension for a Business Central 15.0 SaaS instance? In the current documentation, it says to add a "test" field with value of "184.108.40.206" to the app.json file. In BC 15.0, this is not working.
You need to import the AL Test Tool. I suggest to use Docker containers for creating tests.
The Test Toolkit Test Libraries consists of 5 apps, which are included on the latest Docker images in the C:\Applications folder:
Why do have to build against an on premise build if we are building for SAAS? That doesn't make any sense
With Docker you can create a container with the same image as the SaaS environment (image called bcsandbox) and this is the recommended way when developing for the SaaS. Working directly on the cloud sandbox has lots of disadvantaged compared to a Docker-base SaaS image.
Thanks. Are you available for remote support? What is the best way to contact you?
Business Applications communities