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, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
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 | View virtual launch event
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
Hello.I am trying to get through the process of publishing custom modification for Dynamics 365 F&O to AppSource and I will be grateful for your help.
Let's assume a simple scenario in which the modification consists in adding a new functionality - a new menu item after selecting which the request is sentto some WebService and an infolog is displayed (text with the answer from this webservice).
I have deployable package, which contains everything needed for action (in the margins this modification is implemented in one customer).
In LCS I created a new project that is to be used to handle modifications that will be published in the AppStore.If I understand correctly now I should create Soluton Package in LCS and then publish it globaly to receive an id which I will need to create an offer in Appsource.
And now some questions:
1. Will all solution package components be required in my case ?In particular, will I need :- DATABASE BACKUP - BPM ARTIFACTS- PROCESS DATA PACKAGE ?2. What means here Database backup ?3. What are BPM Artifacts and Process Data Package ?4. I know that the deployable package must be installed earlier in the test environment, can the DEMO version be such a test environment?
Maybe you have some detailed instructions on how to get through the process of publishing the 'Solution Package' step by step?
Do you want to sell your modification or do you plan to enhance the standard functionality for free?
If you want to sell it then the Appsource is the right place.
If you want to enhance the standard functionality for free to help not only your company but also others then you have to look at community driven engineering.
For the latter, you can find some information here: kurthatlevik.com/.../
Hi Ludwig, thank you for the answer. I am interested in selling on AppSource.
Here are my two cents:
@1: You indeed have to fulfill all requirements.
@2: A database backup could be used for e.g. a demo database. You have to create a bacpac from an environment including your solution and demo data.
@3: Please have a look at the documentation.
Process data packages are comfiguration data packages with best practices.
@4: You should prove that a new fresh installation can uptake your deployable package without any issues. Then also prove that the process data package can be imported without issues.
Do you have contact with someone from Microsoft which are there to help you with all these questions?
Thank you for the answer Andre.
Regarding points 2 and 4. What environments should I use for this?
Can I use a demo environment?
I installed a demo environment in my project, but I don't see it in the details of the Solution Package ('Trial environments' section is empty).
I have not contacted Microsoft about this matter yet.
Related to point 2 and 4 : You can indeed first deploy a fresh demo environment. Then install your solution and add some demo data using packages. This would be sufficient for the PDP files. When this is complete, you can create a bacpac as backup database.
Thank you Andre.
I have one more question.
How should I add demo data? By consuming 'Process data package' in LCS or simply importing data packages in 'Data management' in a test/demo environment?
I'm sure you already checked the official documentation: docs.microsoft.com/.../lcs-solutions-app-source
It contains description how to add either a database backup, or data packages for the solution.
Business Applications communities