Sorry come up with a bad news, but Girish's crossed fingers didn't
stop Axapta from assigning duplicate voucher. :-)
Here's how to reproduce :
1. In Account payable menu, make sure there's no opened journal
in invoice journal or payment journal.
2. Open payment journal. A new record will automatically
created and journal id will be reserved.
3. Show all journal by selecting "Open" in the comboBox "Show".
If you look at the journal that was "standing by" (not saved but
created), it's now saved. But if you go look in the number sequence
table, you'll see that this journal Id is now free!
4. Now open invoice journal form and see a brand new record
being created with the same journal id as the payment journal one.
To make it short, what I've found is that you have to comment line 4
of executeQuery() (this.returnJournalNum()) of the DataSource so that
the journal id is not freed when the filter on the form is changed.
The line was useful before HF30SP3_008 but with this fix it's causing
a problem.
Hope that help some of you!
Regards,
Steeve...
--- In [EMAIL PROTECTED], "Girish Bhatkal"
<[EMAIL PROTECTED]> wrote:
>
> Hi ,
> We have Axapta version 3 SP2 and a fix is provided for SP3 "
HF30SP3_008".
>
> Corrections made for:
> With this HotFix installed a user can't draw a journal number
without either
> saving or delete it. This correction prevents the system from
assigning 2
> journals with the same number.
>
> When I checked for the changes done in this hotfix I found that
only the
> form "LedgerJournalTable" was changed.
> In the form
LedgerJournalTable/datasources/ledgerJournalTable/methods/create
>
>
> After the line " journalFormTable.datasourceCreatePost();" a new
line is
> added " ledgerJournalTable_ds.forceWrite(true);"
>
> So I just added this line in the above method (in the live system)
and until
> now its going fine (fingers crossed).
>
> I think its working and in future if there comes any duplicate
problem I
> will let you know.
>
> Have a nice week end.
>
> Cheers,
> Girish
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 29 October 2004 17:27
> To: [EMAIL PROTECTED]
> Subject: Re: AW: [development-axapta] Duplicate voucher Numbers
>
>
>
> Hi,
> I have a similar problem. We are using Ax3.0 with SP3. May be
Giresh or
> Harry help us sharing their exp....... or can walk through the
steps....
>
> The problem is when a user tries to craete a Journal , its trying
to use
> already used Numbser sequence number.
> The error message say " The error message is "Journal name may not
been
> changed when vouchers have been Created""
>
> For example:
>
> A user in Germany created a Journal , 137 was used and the next
number was
> set to 138 .
> Now another user in US tries to create a new journal , its gain
trying to
> use the old number 137.
>
> Do you think the FIX can solve the problem?.
>
> Your help will be highly appreciated.
>
>
>
> [EMAIL PROTECTED] wrote:
>
>
> Hi Girish, hi Harsh
>
> I think, this is what you are looking for...
>
> "HF30SP3_008, Hot Fix
>
> Corrections made for:
> With this HotFix installed a user can't draw a journal number
without either
> saving or delete it. This correction prevents the system from
assigning 2
> journals with the same number.
>
> Affected objects:
> Forms: LedgerJournalTable
>
>
>
> HF30SP3_008.exe (83 Kb)"
>
> regards,
> Tom
>
>
>
>
> -----Urspr�ngliche Nachricht-----
> Von: Harry Deshpande [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 29. Oktober 2004 00:50
> An: [EMAIL PROTECTED]
> Betreff: RE: [development-axapta] Duplicate voucher Numbers
>
>
>
>
> hi Girish
>
> The number sequence bug is in existance since Version 2.0, I have
given up
> any hope that the problem will ever be fixed.
>
> to answer your question..no surprises here..the bug is still there
>
> regards
>
> harsh
>
>
> -----Original Message-----
> From: Girish Bhatkal [mailto:[EMAIL PROTECTED]
> Sent: Fri 29/10/2004 3:28 a.m.
> To: Axapta developers
> Cc:
> Subject: [development-axapta] Duplicate voucher Numbers
>
>
> Hi ,
>
>
>
> Earlier these was a bug in axapta number sequence because of which
the
> vouchers were some times duplicated. It was to be fixed in version
3, SP3. I
> have not yet upgraded to SP3 so wanted to understand from the
people who
> have already upgraded , has there any changes made in SP3 to fix
this
> duplicate problem?
>
>
>
> thanks,
>
> Girish
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
> Yahoo! Groups Sponsor
>
>
> Get unlimited calls to
>
> U.S./Canada
>
>
>
>
> _____
>
> 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 .
>
>
>
> Harry Deshpande
> Senior Consultant
> CGNZ Middle Market Solutions
> Website: www.middlemarketsolutions.com
> Ph +64 29 277 5133
> Fax +64 9 358 1018
>
> CGNZ Limited and its predecessor organisations (Cap Gemini Ernst &
Young,
> and Ernst & Young Consulting) have a proud track record of market
leadership
> and excellent service delivery in all areas of systems delivery
both for New
> Zealand clients and in supporting regional and global projects.
CGNZ is a
> licensed affiliate of Cap Gemini S.A. (one of the world's leading
management
> consulting and IT services companies), wholly owned by NZ
> employee-shareholders, with over 150 IT professionals in our
Auckland and
> Wellington offices. Middle Market Solutions specialises in the
> implementation of business solutions for small corporate and middle
market
> companies. The core activity of our team is the implementation and
support
> of Enterprise Resource Planning (ERP), Customer Relationship
Management
> (CRM), E-Business solutions and related technologies from Microsoft
Business
> Solutions. Find out more about what we do at
> http://www.middlemarketsolutions.com/
>
> CGNZ DISCLAIMER: This email and any attachments are confidential and
> intended exclusively for the person to whom the email is addressed.
If you
> are not the intended recipient, do not read, copy, disclose or use
the
> contents in any way. Please notify us immediately by return email
and
> destroy the email and attachments. CGNZ does not accept any
liability for
> any changes made to this email or attachments after sending by
CGNZ. You
> must scan this email and attachments for viruses. The opinions
expressed are
> not necessarily those of CGNZ.
>
> CGNZ accepts no liability for any loss, damage or consequence,
whether
> caused by our own negligence or not, resulting directly or
indirectly from
> the use of this email and attachments
>
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Mail Address AutoComplete - You start. We finish.
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
>
>
> Yahoo! Groups Links
| 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.
