Dynamics Community Forum Thread Details

No. Series Mishap

Currently using BC 365 SaaS primarily for just financial accounting and AP. In the process of adding inventory, customers, sales, etc. While applying configuration packages into production, an errant ISV package was applied. This package reverted the No. Series back to much older Last No. Used values. The change was made after hours Monday and our accounting folks noticed the issue yesterday afternoon. When receiving errors due to document header numbers already existing.

We can sort through the various document sets to determine the true Last No. Used values, and update the document series entry in the No. Series. We did have some new documents created okay, but their posting would be affected if the posted document series was likewise reverted in the No. Series entry. Working through correcting things now.

We can always restore the production environment to the point in time before the configuration package was accidentally applied. To refer to the last correct snapshot of the No. Series table. Any other suggestions? A mess, I know!

Categories:

Business Central

Quick Links

Leaderboard