web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Deployed a new develop...
Finance | Project Operations, Human Resources, ...
Suggested Answer

Deployed a new development server - Customized Table fields not found

(0) ShareShare
ReportReport
Posted on by Willem van Duren 230

Good afternoon,

I have a strange error. I deployed a new Development server from LCS with Test (Contoso) data. I connected to team server, and got all my customizations as I do every time. I have mapped the Metadata folder to the 'K:\AosService\PackagesLocalDirectory' folder and I see all the files in the folders. My custom model is on the disk and contains all the expected files.

However, when I do a full build of all models and a database sync, I get 623 errors on tables and table fields that are missing:

pastedimage1648564673416v2.png

When I run 'Database Sync' seperately it  gives no errors, however: when I build I get the errors. Also the fields are not in the Dev environments' User interface.

pastedimage1648564463232v3.png

Does anyone has an idea what could be the issue here? This is my third Dev server and I never had any issues.

I have the same question (0)
  • Gunjan Bhattachayya Profile Picture
    Gunjan Bhattachayya 35,429 on at

    Hi Willem,

    Can you go to the source of the error from if you double click on these errors? Do these fields belong to your Development model?

    When you setup your new environment, do you perform a build  and DB sync on Contoso data or after you have refreshed your DB from Sandbox?

  • Willem van Duren Profile Picture
    Willem van Duren 230 on at

    Hi Gunjan!

    When I double click it just opens the classes (extensions) that contain a reference to the table fields.

    All the fields that have errors are in my custom models. ISV models do not generate errors it seems. 

    I also did a build and sync the contoso data together with my custom models. Same errors.  Afterwards I have refreshed the database and did the build and sync again. Same result.

  • Gunjan Bhattachayya Profile Picture
    Gunjan Bhattachayya 35,429 on at

    If you open SalesTable or SalesLine extensions from your custom model, can you see these fields that are throwing an error?

  • Willem van Duren Profile Picture
    Willem van Duren 230 on at

    Opened the inventtable extension which gave an error. I opened the extension. It contains the customized field. Then I did a build: lot of errors. 8077 errors (I had 675 earlier) , a lot of double error messages.

    Part of the Output of build:

    K:\AosService\PackagesLocalDirectory\bin\XppSource\LCwvd365\AxClass_ELCAgreementConfirmationDP_Extension.xpp(693,60):  TableDoesNotContainField: Table 'AgreementLineQuantityCommitment' does not contain a field named 'ELCShippingDateConfirmed'.

    K:\AosService\PackagesLocalDirectory\bin\XppSource\LCwvd365\AxClass_ELCAgreementConfirmationDP_Extension.xpp(726,52):  TableDoesNotContainField: Table 'AgreementLineQuantityCommitment' does not contain a field named 'ELCReceiptDateConfirmed'.

    K:\AosService\PackagesLocalDirectory\bin\XppSource\LCwvd365\AxClass_ELCAgreementConfirmationDP_Extension.xpp(764,55):  TableDoesNotContainField: Table 'AgreementLineVolumeCommitment' does not contain a field named 'ELCExternalItemId'.

    K:\AosService\PackagesLocalDirectory\bin\XppSource\LCwvd365\AxClass_ELCAgreementConfirmationDP_Extension.xpp(770,55):  TableDoesNotContainField: Table 'AgreementLineVolumeCommitment' does not contain a field named 'ELCShippingDateConfirmed'.

    K:\AosService\PackagesLocalDirectory\bin\XppSource\LCwvd365\AxClass_ELCAgreementConfirmationDP_Extension.xpp(771,55):  TableDoesNotContainField: Table 'AgreementLineVolumeCommitment' does not contain a field named 'ELCShippingDateRequested'.

    K:\AosService\PackagesLocalDirectory\bin\XppSource\LCwvd365\AxClass_ELCAgreementConfirmationDP_Extension.xpp(772,62):  TableDoesNotContainField: Table 'AgreementLineQuantityCommitment' does not contain a field named 'ELCShippingDateConfirmed'.

    K:\AosService\PackagesLocalDirectory\bin\XppSource\LCwvd365\AxClass_ELCAgreementConfirmationDP_Extension.xpp(773,60):  TableDoesNotContainField: Table 'AgreementLineQuantityCommitment' does not contain a field named 'ELCShippingDateConfirmed'.

    K:\AosService\PackagesLocalDirectory\bin\XppSource\LCwvd365\AxClass_ELCAgreementConfirmationDP_Extension.xpp(781,52):  TableDoesNotContainField: Table 'AgreementLineVolumeCommitment' does not contain a field named 'ELCReceiptDateConfirmed'.

  • Gunjan Bhattachayya Profile Picture
    Gunjan Bhattachayya 35,429 on at

    Are you missing a model reference in the custom model by any chance? From the first error -

    K:\AosService\PackagesLocalDirectory\bin\XppSource\LCwvd365\AxClass_ELCAgreementConfirmationDP_Extension.xpp(693,60):  TableDoesNotContainField: Table 'AgreementLineQuantityCommitment' does not contain a field named 'ELCShippingDateConfirmed'.

    There an extension to the DP class - ELCAgreementConfirmationDP in your Dev model. Does your Dev model have a reference to the package which contains ELCAgreementConfirmationDP class?

  • Willem van Duren Profile Picture
    Willem van Duren 230 on at

    Yes it does. It is the same as on my second dev server, which works fine for more than a year now.

    I will deploy a new one and check if that solved it.

  • Willem van Duren Profile Picture
    Willem van Duren 230 on at

    Deployed a new server. Did not refresh the DB, only add the team service branches, did a build and compile, and exactly the same errors:

    pastedimage1648630874365v1.png

  • Martin Dráb Profile Picture
    Martin Dráb 239,634 Most Valuable Professional on at

    How did you verify the relation between packages?

    It's possible that it works on your other DEV server because you have some extra local changes there that haven't been added to source control.

  • Willem van Duren Profile Picture
    Willem van Duren 230 on at

    Hi Martin,

    I verified the descriptors, which are the same as on our other dev machine.

    Our IT partner checked it and let me know that the DB sync is failing on standard objects an that therefore the custom fields are not created.

    We are doing extra research, but it might have something to do with the 10.0.25 version of the Dev deployment.

  • Willem van Duren Profile Picture
    Willem van Duren 230 on at

    Also after extra tests the sync of the standard keeps giving issues. It appears that it is related to the v10.0.25 software with which I deployed the dev server. I am now deploying another server based on v10.0.24 to see if it has the same issues. If not then I will manually update it to v10.0.25.

    I will let you know if this worked.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 802

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 636 Super User 2026 Season 1

#3
Subra Profile Picture

Subra 534

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP
License usage reporting (in-app and PPAC) with Entra dynamic groups

Product updates

Dynamics 365 release plans