维度查找挂起 AX 客户端？

Question

I have an import interface (not coded by me) that imports XML data and creates LedgerJournalTable (1) and LedgerJournalTrans (1..n) records.

When handling LJT dimensions, the code first checks that the dimension exists in AX, then inserts the data in the dimension[x] field. However, in the case that the dimension doesn't exist, a warning is shown to the user after the import run ends, but the data is still inserted as is .

And when the user goes to the LJT line after the import is complete, the erronous value is shown in the dimension field. When the lookup/drop-down of this dimension is clicked, the lookup does not open and AX client hangs. Ctrl+break will recover it, but the lookup never opens. You can delete the value, save, and the problem will still persist. You can manually enter an existing value and save, and the problem will still persist. Problem extends to the table browser also.

Any idea why this is happening and how can it be fixed, other than not saving the erronous value in the first place (I have no idea why this is done this way in the first place)?

Thanks in advance.

Answer 1

Let me know if I'm reading this correctly.

1. User runs some process to import LJ table/trans records from XML.
2. If a bad dimension is inside XML, it shoves the data into the LJ trans dimension[x] field even though it's invalid, and presents a warning to user.
3. User views the journal and sees the bad data and attempts to use the lookup to correct it, but the lookup hangs/crashes.

Seems to me the issue may be that you've been shoving a bunch of bad data into AX and the lookup is trying to use table/edt relations that are invalid.

If I'm right, you need to go to SQL directly and query the ledger trans table and look for any bad dimension data and correct/remove it.

I suspect existing bad data is causing the lookup to fail and not merely whatever bad data you imported and are looking at.

Perhaps what caused the problem is, a user imported bad data, received a warning, ignored warning , clicked "post" as-is (with bad data) and now it's in AX? And now when you do a 2nd import, and try to use the lookup, it's crashing on that bad-data-relation.

Answer 2

Edited: So, while there was an corruption in the DB, the actual culprit was found: the standard AX code creating temp data for the dimension lookup - there was a mod code in Dimensions.insert() that wrote an XML file every dimensions were updated or inserted. This took so long in this case that it hang up the client. I put the code inside an if clause like so:

if(!this.isTemp())
{
  // offending code
}

Problem solved.