Finance | Project Operations, Human Resources, ...

How to change forced voucher on LedgerJournal

(3) Share

Report

Posted on by RadekM

174

HI,

I have a problem with voucher numbers. Whenever I create a new journal and try to add lines in it sometimes I get a voucher number that is already in use and I cant proceed with it.

The only workaround I found is to manualy delete the voucher from the NumberSequnceList so it will generate me a new one.

Is there any way to make it work? So it doesn't give me used vouchers?

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (4)

Answers (0)

Frank Hamelly | MVP... 46,627 Moderator on at

Like (1)

Report
Copy link

Link copied!

Can you provide a screenshot of the number sequence settings for the voucher. It could be related to the NS configuration.

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 303,669 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Radek,

Can you tell us how journal lines are entered in your environment? Is it manual entry only? Is data management used? Is there a customization that creates or imports journal lines?

I have seen this behavior in case of a wrong usage of number sequence calls in customizations. So, if there is a customization, ask the developer to check if a call numberSeq.used() is executed. The developer can also change the behavior of getting a new number from the number sequence by NOT enabling the parameter MakeDecisionLater. If the parameter is set to make the decision later and number sequence is not finalized with the used() method, the numbers can hang in the status list giving you the current experience.

Was this reply helpful? Yes No
RadekM 174 on at

Like (0)

Report
Copy link

Link copied!

As far as I know there is no modification for this. THe journals are added manually. When I hit the New button it gives me a voucher that I can't edit.

Where can I find these parameters?

Was this reply helpful? Yes No
RadekM 174 on at

Like (0)

Report
Copy link

Link copied!

Okay so I think the problem lies within the cleanup.

So since we run problems with AX we need to do at least 1-2 AOS restarts a week and that might cause a problem when somebody is working and the sequence might get in the limbo. Any idea where it might be stored of flagged? Since the sequences pop up days after the journal is closed.

Was this reply helpful? Yes No