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

Notifications

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, ... / BYOD data issue
Finance | Project Operations, Human Resources, ...
Answered

BYOD data issue

(0) ShareShare
ReportReport
Posted on by Frank Bruemmer 354

Hello D365 community,

I have set up a working BYOD job that transfers data from a custom LedgerJournalEntity to the BYOD. I recently added the LedgerJournalTrans.TransactionType to the data entity as well as to the staging table.

I refreshed the data entity list, renegerated the mapping, regenerated the staging to target BYOD mapping and everything looks ok.

However, when I execute my job, all ledger transactions (thousands) end up as (LedgerTransType) 36, which is some sort of Russian amortization type. I was expecting a variety of types such as 15 for payments.

Any idea what I'm missing ?

Thanks

Frank

I have the same question (0)
  • Suggested answer
    Sergei Minozhenko Profile Picture
    Sergei Minozhenko 23,093 on at

    Hi Frank,

    Are you sure that 15 is Payments and 36 Russian amortization type? In my case 36 is General ledger. LedgerTransType is an extensible enum and the number in the list of values in AOT is not always equal to the number in the database.

    Try to run the next code to check values.

    static void main(Args _args)
{
    DictEnum d = new DictEnum(enumNum(LedgerTransType));
    
    int i;

    for (i = 1; i <= d.values(); i  )
    {
        Info(strFmt("%1 %2", d.index2Value(i), d.index2Symbol(i)));
    }
}

  • Frank Bruemmer Profile Picture
    Frank Bruemmer 354 on at

    Sergey,

    thanks for your help.

    You are right, 36 is General Journal. 15 is still Payments though. Looking at my ledgerJournalTrans table I have records with 36, 15 and many others. However, when they are copied to the BYOD, these all turn to 36.

    Best regards

    Frank

  • Verified answer
    Sergei Minozhenko Profile Picture
    Sergei Minozhenko 23,093 on at

    Hi Frank,

    Could it be that you export only transactions with type 36? Do you have ranges on entity? Filters in data project?

  • Frank Bruemmer Profile Picture
    Frank Bruemmer 354 on at

    I'm don't think so. I assume the problem relates to duplicating the original data entity and making it work by the person who developed it. Further investigation revealed that there were also records missing.

    I gave up and went and extended the GeneralLedgerJournalLineCDSEntity to include the transaction type, build, synced, remapped and it worked right away.

    Thanks for your time anyways.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

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

#1
Martin Dráb Profile Picture

Martin Dráb 544 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 450 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 250 User Group Leader

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans