Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance forum / Errors in LedgerJourna...
Finance forum

Errors in LedgerJournalHeaderEntity and LedgerJournalLineEntity after Full Build Compilation

(0) ShareShare
ReportReport
Posted on by 416

Hi all,

I have encoutered 5 errors after performing a full build compile on a Dynamics 365 for operations environment (Release 1611, Platform Update 4). The entities haven't been modified at all.

Any ideas?

Here are the details:

Severity    Code    Description    Project    File    Line    Suppression State
Error        Path: [dynamics://DataEntityView/LedgerJournalHeaderEntity]:On view 'LedgerJournalHeaderEntity', the field 'AccountingCurrency' refers to a nonexistent table or view named 'Ledger'.        J:\AosService\PackagesLocalDirectory\ApplicationSuite\Foundation\AxDataEntityView\LedgerJournalHeaderEntity.xml    0    

Severity    Code    Description    Project    File    Line    Suppression State
Error        Path: [dynamics://DataEntityView/LedgerJournalLineEntity]:On view 'LedgerJournalLineEntity', the field 'DefaultDimensionDisplayValue' refers to a nonexistent table or view named 'DimensionSetEntity'.        J:\AosService\PackagesLocalDirectory\ApplicationSuite\Foundation\AxDataEntityView\LedgerJournalLineEntity.xml    0    

Attached image with the errors:

6355.Errors_5F00_D365O.PNG

  • Suggested answer
    nmaenpaa Profile Picture
    101,158 Moderator on at
    RE: Errors in LedgerJournalHeaderEntity and LedgerJournalLineEntity after Full Build Compilation

    Dependencies are not added in project, you define them in a package. The package where the entity exists, must have proper references to other packages where the dependent data types etc are defined.

  • Community Member Profile Picture
    on at
    RE: Errors in LedgerJournalHeaderEntity and LedgerJournalLineEntity after Full Build Compilation

    Hi Boy Mancagne,

    I follow your suggestion and it also worked for me. My concern is that I was only looking at the entity using visual studio, I did not include anything from it on my project. Why would I have to now add the Ledger dependency on my project?

    Thanks for the suggestion.

  • Suggested answer
    Community Member Profile Picture
    on at
    RE: Errors in LedgerJournalHeaderEntity and LedgerJournalLineEntity after Full Build Compilation

    Hi Boy Mancagne,

    I faced the same problem And followed your suggestion it worked for me,

    Thanks 

  • Verified answer
    Boy Mancagne Profile Picture
    on at
    RE: Errors in LedgerJournalHeaderEntity and LedgerJournalLineEntity after Full Build Compilation

    Hi Guys,

    I've faced the same issue saying 

    Path: [AxView/Bash ThirdParty View/Fields/Account Name/DataSource]:Data source 'DimAttributeVendTable' does not exist or is not part of the first root data source in the query.

    The solution i've applied is to update my model by adding the "Directory" Package as a reference. 

    The fields causing the issue is from DirpartyTable (part of DimAttributeVendTable) witch belong to the "Directory" package.

    I hope this will help.

  • Community Member Profile Picture
    on at
    RE: Errors in LedgerJournalHeaderEntity and LedgerJournalLineEntity after Full Build Compilation

    Hello everyone,

    Has anyone found the solution to this? I am facing similar (if not the same) error.  I created a Data Entity duplicated from out-of-box VendInvoiceJournalLineEntity  (similar to the LedgerJournalLineEntity).  I keep getting the following 2 errors:

    Error Path: [AxDataEntityView/RHRShdbVendInvoiceJournalLineEntity/Fields/ValidTo/DataField]:'DirPartyLocationPostalAddressV2Entity' field not specified. C:\AOSService\PackagesLocalDirectory\Enhancements\RHR008 Shareholder\AxDataEntityView\RHRShdbVendInvoiceJournalLineEntity.xml 0

    Error Path: [AxDataEntityView/RHRShdbVendInvoiceJournalLineEntity/Fields/ValidFrom/DataField]:'DirPartyLocationPostalAddressV2Entity' field not specified. C:\AOSService\PackagesLocalDirectory\Enhancements\RHR008 Shareholder\AxDataEntityView\RHRShdbVendInvoiceJournalLineEntity.xml 0

  • Peter S Profile Picture
    715 on at
    RE: Errors in LedgerJournalHeaderEntity and LedgerJournalLineEntity after Full Build Compilation

    I started getting the same error on a different entity after viewing it in VS. I am still looking for a solution.

    Severity Code Description Project File Line Suppression State
    Error Path: [dynamics://DataEntityView/VendInvoiceJournalLineEntity]:On view 'VendInvoiceJournalLineEntity', the field 'ApproverNumber' refers to a nonexistent table or view named 'HcmWorker'. J:\AosService\PackagesLocalDirectory\ApplicationSuite\Foundation\AxDataEntityView\VendInvoiceJournalLineEntity.xml 0

    I can see the ApproverNumber field on the VendInvoiceJournalLineEntity view in SQL. The underlying field HCMWorker.PersonnelNumber exists. Full compile and synch still show error. Strangely the error only started appearing after I viewed the entity object in VS. 

  • Jonathancm Profile Picture
    416 on at
    RE: Errors in LedgerJournalHeaderEntity and LedgerJournalLineEntity after Full Build Compilation

    Hi, yes, it has references to ledger and dimensions models.

  • Jonathancm Profile Picture
    416 on at
    RE: Errors in LedgerJournalHeaderEntity and LedgerJournalLineEntity after Full Build Compilation

    Hi, I have performed the sync but the errors still persists. It must be something else I think.

  • Mea_ Profile Picture
    60,278 on at
    RE: D365O: Errors in LedgerJournalHeaderEntity and LedgerJournalLineEntity after Full Build Compilation

    Hi Jonathan Corrales,

    Does App Suite model have references to ledger and dimensions models  ?

  • Santosh Yadav Profile Picture
    420 on at
    RE: D365O: Errors in LedgerJournalHeaderEntity and LedgerJournalLineEntity after Full Build Compilation

    it seems, respective datasources defined on entity fields are not sync to db due to that when views are getting created in db this error was thrown.

    can you check if respective tables (like ledger in case of LedgerJournalHeaderEntity issue) exists in database. i think when you have all those tables sync to db, all these issues would be wiped out automatically.

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

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 294,259 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 232,988 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,158 Moderator

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans