Dynamics Community Forum Thread Details

"Outer Join" and "Next" Statement,

I have 2 AX 2012 R3 environments, with different Kernel Builds. I would like to know what is the expected behaviour of this situation:

In class FormletterJournalPost(SalesInvoiceJournalPost).post() we call selectFormletterJournalTrans():

select forupdate formletterJournalTrans
        where formletterJournalTrans.JournalId           == formletterJournal.JournalId
           && formletterJournalTrans.InternalJournalId   == formletterJournal.InternalJournalId
           && formletterJournalTrans.OrderId             == formletterJournal.OrderId
           && formletterJournalTrans.TransDate           == formletterJournal.TransDate
           && formletterJournalTrans.NumberSequenceGroup == formletterJournal.NumberSequenceGroup
        join forupdate salesLine
            where salesLine.InventTransId                == formletterJournalTrans.InventTransId
        outer join salesParmLine
            where salesParmLine.ParmId                   == custInvoiceJour.ParmId
               && salesParmLine.TableRefId               == salesParmTable.TableRefId
               && salesParmLine.SalesLineRecId           == salesLine.RecId
               && salesParmLine.PackingSlipId            == formletterJournalTrans.PackingSlipID
        outer join inventTable
            where inventTable.ItemId                     == salesLine.ItemId;

Later in the same post method, we call

protected void nextFormletterJournalTrans()
{
    next formletterJournalTrans;
}

So in one environment (kernel 6.3.1000.2457), this sets the next record for "formLetterJournalTrans" and also for "SalesParmLine". However, in the new kernel (6.3.3000.111) environment, it only sets the "formLetterJournalTrans".

I was expecting to also get the next "SalesParmLine". Any ideas on what could be causing the different behaviour?

Quick Links

Leaderboard