Dear Palle,
Hope this explanation is not too long to understand.
Please check the create method in LedgerJournalTable
form, LedgerJournalTable datasource. Is it the same
with this? (Axapta 3.0 SP3)
void create(boolean append = FALSE)
{
if (comboAllOpenPosted.selection() !=
AllOpenPosted::Posted)
{
if (! journalFormTable.datasourceCreatePre())
return;
if (ledgerJournalTable.recId ||
!ledgerJournalTable.journalNum)
super(append);
journalFormTable.datasourceCreatePost();
ledgerJournalTable_ds.forceWrite(true);
}
}
The code:
if (ledgerJournalTable.recId ||
!ledgerJournalTable.journalNum)
before calling super is important.
It is because Axapta has a number sequence flow that
is very strict when that number is commited used or
canceled.
But, axapta kernel has a contradiction condition with
that flow. Because, axapta kernel will not call
validateWrite and Write method of datasource if the
kernel find no fields are filled (all fields are empty
or not modified after calling initValue event). So,
number sequence flow will take this case as uncommited
number sequence, so it is stored in number sequence
list as 'Activated'. Until, that number sequence is
cleaned up, usually after 24 hours. After cleaned up,
that number's status will change into 'Free'. So, it
will give error message 'The number is already used.'.
So, try to check create method with above method (it's
important to check line above calling super method).
Then, clean all number sequence list, and delete all
number sequence that can make an error or delete all
of them if you are sure that number will not be used
again. Then, set 'next number' of that number sequence
to the desired number.
Regards,
Sonny Wibawa Adi
--- pallegude <[EMAIL PROTECTED]> wrote:
>
>
> When we create a new journal, it sometimes get a
> number that is
> allready used. When we look in the numbersequence
> free list, the
> number is in the free list, but looking in posted
> journals, shows it
> has allready been used for another journal.
>
> We have downloaded and installed the Hotfix from MS,
> which SHOULD have
> solved the problem, but it didn't !! It is still
> there.
>
> The error is not replicable, we et it with random
> users, random
> journaltypes, and random interval. Only thing we can
> be sure, it will
> occour again very soon in the future.
> Both we, and the customer, are quite frustrated.
> Please suggest
> whatever that MIGHT help us solve.
>
> Best regards
> Palle
>
>
>
>
>
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
| Yahoo! Groups Sponsor | |
|
|
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
