Repository navigation
[Bug]: Error on new company with demo data: "‘Document record ID’ must contain a value in ‘E-document’" #8707
Description
Describe the issue
German error text:
'Belegdatensatz-ID' muss in 'E-Beleg' einen Wert enthalten: 'Belegpostennr.=7'. Der Wert darf nicht null oder leer sein.
English translation:
‘Document record ID’ must contain a value in ‘E-document’: ‘Document item no. = 7’. The value must not be null or empty.
CallStack:
PostPurchaseInvoice (\BE-Fashion-Demo.app.source\Codeunit\5429\Contoso Inbound E-Document.dal:149) Generate (\BE-Fashion-Demo.app.source\Codeunit\5429\Contoso Inbound E-Document.dal:81) GenerateContosoInboundEDocuments (\BE-Fashion-Demo.app.source\Codeunit\11370\Create Demo EDocs DE.dal:56) OnRun (\BE-Fashion-Demo.app.source\Codeunit\11370\Create Demo EDocs DE.dal:26) EDocumentModule (\BE-Fashion-Demo.app.source\Codeunit\11374\E-Doc. Demodata DE.dal:29) LocalizationContosoDemoData (\BE-Fashion-Demo.app.source\Codeunit\11374\E-Doc. Demodata DE.dal:21) OnAfterGeneratingDemoData (\BE-Fashion-Demo.app.source\Codeunit\5193\Contoso Demo Tool.dal:297) GenerateDemoData (\BE-Fashion-Demo.app.source\Codeunit\5193\Contoso Demo Tool.dal:205) BuildDependencyAndGenerateDemoData (\BE-Fashion-Demo.app.source\Codeunit\5193\Contoso Demo Tool.dal:96) CreateNewCompanyDemoData (\BE-Fashion-Demo.app.source\Codeunit\5193\Contoso Demo Tool.dal:53) OnRun (\BE-Fashion-Demo.app.source\Codeunit\5382\Company Creation Contoso.dal:53) OnRun (\BE-Fashion-Demo.app.source\Codeunit\5279\Generate Contoso Demo Data.dal:27)
Expected behavior
the background job task for creating a new company with Contoso demo data should execute without any interruption and errors.
Steps to reproduce
- Use the German Localization
- Create a new Company on
Companies (357, List) - use Contoso Demo Data;
Evaluation - Contoso Sample Data - use all Contoso Demo Data Modules
- wait until the error occurs (see call stack)
Additional context
As far as I know, this happens every time, but not if i create an empty company and create the demo data afterwards over the contoso demo tool page.
Version: 27.3.44313.45104
I will provide a fix for a bug
- I will provide a fix for a bug
Activity
github-actions commentedon Mar 5, 2026
This issue has been approved for contribution ✅ Thanks for contributing.
ventselartur commentedon Mar 17, 2026
Hello,
Thanks for reporting this. I was not able to reproduce this on the latest:
Version: DE Business Central 29.0 (Platform 29.0.47575.0 + Application 29.0.47676.0)
I can create a new company from CRONUS DE following your repro steps.
May i ask you to try on the latest?
SchulzOli commentedon Apr 27, 2026
i try to do it on 29.* but i can say that we have a bug on 28.0 as well.
jeffreybulanadi commentedon May 5, 2026
Looking at this further, the error trace points to two separate problems that were introduced in v28.
The primary issue:
EDocDemodataDEwas callingCreate Demo EDocs DEat the Transactional demo data level. That codeunit calledContosoInboundEDocument.Generate(), which ran only the "Finish draft" import step. TheCreateEDocSampleInvoicesevent subscriber was not bound at that point, so the purchase header update event did not fire. Without that event, the "Finish draft" step failed to setDocument Record ID, and the subsequentTestField("Document Record ID")inPostPurchaseInvoicesurfaced the validation error you saw. The call toCreate Demo EDocs DEwas removed fromEDocDemodataDEas part of the v29 work, which is why the issue cannot be reproduced on v29.A secondary problem in the same codeunit:
WorkDate()was modified before theGenerate()calls and only restored at the very end of the procedure. If any call threw an error,WorkDatewas left permanently modified for the rest of the session. This is the secondary fix in PR microsoft/ALAppExtensions#30006.Since the main crash is already resolved in v29, the PR addresses the remaining WorkDate state leak, which could still affect any environment where the obsolete codeunit is invoked directly.
SchulzOli commentedon May 5, 2026
thanks a lot for your answer and the provided informations.
jeffreybulanadi commentedon May 5, 2026
Oliver Schulz (@SchulzOli) no worries, mate. let's wait for the reviewer to review my code.
JesperSchulz commentedon Jun 22, 2026
Transferring this issue to BCApps. Repo migration to BCApps will complete next Monday. Jeffrey Bulanadi (@jeffreybulanadi), could you recreate the PR here when the repo migration is complete, please?
JesperSchulz commentedon Jun 22, 2026
🤖 AI triage completed. Product group, please validate the triage report (Microsoft internal access only, use Ctrl+Click to open in new tab).
Was this triage helpful? React with 👍 or 👎 on this comment to provide feedback.
Aleyenda commentedon Aug 26, 2026
ventselartur can you take a look at the latest comments?