Hi Sonny and Darius...

Later i posted this message, i checked the create method in my datasource (LedgerJournalTrans),  and realized the that the error was caused by a line code:

void create(boolean append = FALSE)
{
    ;
    ledgerJournalEngine.precreate(ledgerJournalTrans);
    element.setDebCredProposal(true);
    super(append);
    virtualCashDiscDate    = datenull();
    virtualCashDiscAmount  = 0;
    //LedgerJournalTrans.xar_TipoRegistro = "1";  This is guilty line...
    cashDiscChanged        = false;
}

I am a begginer axapta developer and i don't know if this is a best practice (to set a default value to a field), but i'll find another way.

Thanks.

Sonny Wibawa Adi <[EMAIL PROTECTED]> wrote:
Hi, Roberto Pineda,

I have encountered a similar problem. But, I don't know if the problem is the same with yours, because my problem will resulting a jumped number sequence, not duplicate number sequence.
My problem is jumped number sequence when user tried to create a new record in two different ways. The first way is by pressing down arrow (��) and the second way is by clicking new toolbar button or by pressing Ctrl+N key. The second way will result a jumped number sequence.

This is the call stack from each way of creating new records:

1. Use Down Arrow and Set Datasource Property "InsertAtEnd" to "YES"

(C) \Classes\JournalFormTrans\datasourceValidateWritePost - line 5

(C) \Forms\InventJournalMovement\Data Sources\InventJournalTrans\Methods\validateWrite - line 7

(C) \Classes\FormDataSource\Next

(C) \Classes\FormRun\task

(C) \Classes\SysSetupFormRun\task - line 20



2. USE New Button on Toolbar

(C) \Classes\JournalFormTrans\datasourceValidateWritePost - line 5

(C) \Forms\InventJournalMovement\Data Sources\InventJournalTrans\Methods\validateWrite - line 7

(C) \Classes\FormRun\selectControl

(C) \Classes\FormDataSource\create

(C) \Forms\InventJournalMovement\Data Sources\InventJournalTrans\Methods\create - line 5

(C) \Classes\FormRun\task

(C) \Classes\SysSetupFormRun\task - line 20


So, this is my solution:

- Add a new condition at Create method of the datasource.



void create(boolean append = false)

{

;

if (!MyTable.RecId) // issue about create new line in different orders.

{

MyTable_ds.research();

}

//�c

super(append);

//�c

}




Regards,

Sonny Wibawa Adi


[EMAIL PROTECTED] wrote:

Delete that voucher list - set the the next number to higher that was used. I think this should help - as fa as I know this voucher problem hasn't been solved even in SP3...:(

Darius

>Hello to all...
>
>Recently i have experienced a problem with the number sequence for
>vouchers. I entered a line in a journal and set up all data like
>taxes, the line entered is valid, so the next line voucher to add had
>to be next, but it was not working.
>
>I am using citrix to access the axapta server, i suppose it is a
>determining factor but not sure.
>
>I have checked the number sequence list, and sometimes it stores the
>voucher like it was free.
>
>Does someone know which could cause it?
>
>Thanks.... if the question is not understandable, let me know.
>Any help will be appreciated.
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>





Yahoo! Groups Links









---------------------------------
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!

[Non-text portions of this message have been removed]






Yahoo! Groups Links









Roberto Pineda
           
---------------------------------



[Non-text portions of this message have been removed]



Yahoo! Groups Sponsor
ADVERTISEMENT
click here


Yahoo! Groups Links

Reply via email to