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
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 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
Changing a field number is considered a breaking change and this is not possible on D365BC.
If you need to do so (from version 1.0 to 1.1 of your extension) you need to:
1) if you're on SaaS, you need to declare field 1 as obsolete (ObsoleteState = Removed property) and then create field 2
2) On-premise, you can do as described in point 1 but you can also use SchemaUpdateMode = Recreate and force the modification (with data loss).
Thank you so muck. If I forget to declare field 1 as obsolete and change field Id from 1 to 2, is there a way to automated detect that error in my local?
If you change a field Id VS Code permits this. Check is controlled during publishing.
Thank you, is it possible let VS code does't allow this field change?
Business Applications communities