FrontAccounting forum — Reference auto changing to Legacy

Re: Reference auto changing to Legacy

null@example.com (apmuthu) — Sun, 24 Apr 2022 16:34:27 +0000

Try using {YY}-{MM}/{0001} so that it is sortable and properly incrementable.

Re: Reference auto changing to Legacy

null@example.com (dz) — Thu, 21 Apr 2022 15:16:13 +0000

Yes it happens with me aswell. Sometime when in the new month when we change the date, the reference field does not gets updated. I thought its may be due to slow internet at the user end

Reference auto changing to Legacy

null@example.com (boxygen) — Thu, 28 Oct 2021 18:01:38 +0000

I am using the references as {0001}/{MM}{YY}

It works perfectly but sometimes (not always) the reference is auto updated to Legacy values. For e.g at times I see that the new month is started but it is continuing the sequence of old month. Upon checking the transaction references I found that the pattern was auto set to Legacy.

I tried to debug the issue but since it is not doing all the time I could not catch it.

Any idea how to catch and fix the bug?