There are a few things to look out for – things not that obvious.
Look at the extension settings in my Source Control.
the “appName” must match the name in Azure Publishing.
The “appPublisher” must match the publisher short name.
The “appVersion” must be in this format and identical to the version of you app in Azure Publishing.
Also make sure to only select Canada and US even if your app can support more. Also make sure to only select English as the language. There can only be two industries and sub-categories.
There must be a web site for the extension. The “appHelp” Url needs to land in a place where it is easy for the user to find help.
“We would recommend to make the videos more prominent on the top of the side. The help link is intended to provide online customer help.”
Now, when you follow the help link you will see a video that will show the benefits of installing this Extension.
Also make sure to have a proper page for privacy, terms and conditions and the publisher website.
All videos must be Dynamics 365 only, both in speech and image. Never mention Dynamics NAV nor NAV. Using the Dynamics 365 shell or the upcoming Dynamics 365 for Financials testing environment to make your screenshots and videos.
The documentation must include a user story for the testing team to follow. The testing team must be able to follow a guided path to test the Extension with new releases of Dynamics 365. The user story should also show the gains by installing the extension.
Then there is the Lead Management.
There is a document describing how to do this. You can download it from here, but this is a static document and will not be updated by Microsoft. AppSource Publishing Guide for Dynamics CRM Solutions.
I am using Azure Table. Sample final connection string:
After correcting all my issues I have restarted the request approval to push to production process…
4 Replies to “My first Dynamics 365 Extension – Mistakes I made”
Hi I am also working on a extension for D365 and had some queries.
1. Do we need to add our pages and reports inside menu suite in order for them to be displayed in D365?
2. Can we edit existing role centers and add our own pages to them or do we have to create every role center from scratch?
3. Permission sets and how to work with them in extensions?
4. Are assisted setups a compulsory requirement
1. You need to create your own menusuite object with all your object that must be available in the department menu.
2. You can edit existing rolecenters the same way you can edit a normal NAV/D365 page with an Extension. You can’t create a role center in current version but that is in the to-do list for Microsoft to support.
3. Must have permission sets for all your objects. There are new tenant tables for tenant permission handling. The appId (guid) is always used in these tables to link permission sets to extensions.
4. Notifications and Assisted Setup is recomended for the solution, both by me and Microsoft. Not a requirement.
Thanks for the reply, just need a bit more clarity on:
1. All the objects? You mean just my own custom objects or Do I modify the menusite that is standard in NAV 2017 and add my objects in the departments there.
3. I have created 4 different permission sets for each of my user and then I will export the XML and then put them in the folder while I generate my Navx. Is there any other input needed from me?
1. I looked into menu suite and Understand what you meant. The query I have now is which MenuSuite Design Level do I choose and Does this menusuite has to be in the custom range MS provided us.
I am asking this because by default Menu Suite is getting a object id automatically (1080)
Really appreciate your help here