Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested answer

How to automatically test field identifier changes between two different extension version in D365BC?

(0) ShareShare
ReportReport
Posted on by
Hi Expert,
 
We have an extension which version is 1.0 and have a table test:
 
table 1 test
{
field(1; ItemID; code[20])         { DataClassification = CustomerContent;         }
}
 
Now, we develop an extension for version 1.1, and change table test as below (changed field ItemID identifier):
 
table 1 test
{
field(2; ItemID; code[20])         { DataClassification = CustomerContent;         }
}
 
So is there a way that I can test this change between version 1.0 and 1.1 automatically (if field identifier is different, then error out )?
 
Could anyone shed me some light on it?
 
Thanks,
Ming
  • Community Member Profile Picture
    on at
    RE: How to automatically test field identifier changes between two different extension version in D365BC?

    Thank you, is it possible let VS code does't allow this field change?

  • Suggested answer
    Stefano Demiliani Profile Picture
    37,166 Most Valuable Professional on at
    RE: How to automatically test field identifier changes between two different extension version in D365BC?

    If you change a field Id VS Code permits this. Check is controlled during publishing.

  • Community Member Profile Picture
    on at
    RE: How to automatically test field identifier changes between two different extension version in D365BC?

    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?

  • Suggested answer
    Stefano Demiliani Profile Picture
    37,166 Most Valuable Professional on at
    RE: How to automatically test field identifier changes between two different extension version in D365BC?

    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).

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Congratulations to all our community participants!

Adis Hodzic – Community Spotlight

We are honored to recognize Adis Hodzic as our May 2025 Community…

Kudos to the April Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
YUN ZHU Profile Picture

YUN ZHU 628 Super User 2025 Season 1

#2
Mansi Soni Profile Picture

Mansi Soni 495

#3
Sohail Ahmed Profile Picture

Sohail Ahmed 415

Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans