Explore Dynamics 365 Business Central on Microsoft LearnDiscover features, benefits, and examples of Dynamics 365 Business Central in action in this short training module.
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
I have know MS suggested to use different appID for custom extension each project that we has. But i missed this one due to i was copied from the workspaces folder of another project, so everything copied for my other project including "id" on app.json file. I was changed only for the name, forgot to considering for the ID. This one was tested on the sandbox for every project we have and there's no problem so i deploying into production.
Until today, we only has 1 packages only for each project customer. Currently my senior realized that i should be not using same id on app.json file even for different project customer since MS suggested that. The problem is, if i changes the id on app.json...it will ask current installed extension need to be unpublish first and this one will erase the existing data on fields customized.
Question is,since actually there's no problem on live one even using same id in app.json with other different project. Should i keep it as it is for the project that already on production live ?
Or there's another way to changes the id in app.json without erased existing data ?
e.g : project ABC & XYZ has same id
Business Applications communities