Hi,
The issue you're encountering with the Contoso Coffee Demo Dataset—specifically the codeunit 11494 binding error—is a known challenge when deploying the demo data in on-premises containers. Here's a breakdown of the situation and recommended steps:
🔧 Root Cause
The error "The binding of codeunit 11494 was unsuccessful. The codeunit has already been bound." typically occurs when the demo tool attempts to re-bind a codeunit that was already initialized in a previous session or failed run. This can also be compounded by leftover records like Data Exch. Def entries (e.g., OCRCREDITMEMO) that conflict with the demo setup[1].
✅ Recommended Solutions
The GitHub source code for the demo tool shows that the tool checks whether modules have already been generated and skips them if so[2]. To force regeneration:
- Use the
ContosoCoffeeDemoDataSetup table to reset the language and data level.
- Clear or delete entries in the
Contoso Demo Data Module table to allow re-generation.
- You may need to manually delete conflicting records like
Data Exch. Def entries using configuration packages or SQL if safe.
2. Use the CreateDemoData Procedure
The codeunit includes a method CreateDemoData that can be invoked manually via AL or PowerShell to bypass UI triggers. This method checks for language compatibility and regenerates data for selected modules [2].
3. Try a Clean Container
If the above fails, consider:
- Creating a new container with no prior demo data.
- Installing only the Contoso Coffee Demo Dataset extensions before running the demo tool.
- Avoid running the CRONUS setup first, as it may conflict with Contoso data.
4. Alternative: Manual Data Import
If automation fails, you can manually import manufacturing demo data using:
- Configuration packages from Microsoft or community sources.
- GitHub ALAppExtensions which include demo data definitions [2].
- Manually creating BOMs, production orders, and vendors based on Contoso documentation [3].
🧪 Additional Tips
- Ensure Premium features are enabled in your container setup.
- Use the latest BC artifact version compatible with the Contoso extensions.
- Monitor the ContosoCoffeeDemoDataSetup and Contoso Demo Data Module tables for status flags.
Let me know if you'd like help crafting a script to reset the demo tool state or manually invoke the CreateDemoData procedure.
Thanks and best regards,
Daniele
Note: This response was prepared with support from Copilot to ensure clarity and completeness.
[1]: https://community.dynamics.com/forums/thread/details/?threadid=b5336aa7-0c7e-f011-b4cc-7c1e521b4ace
[2]: https://github.com/microsoft/ALAppExtensions/blob/main/Apps/W1/ContosoCoffeeDemoDataset/app/DemoTool/ContosoDemoTool.Codeunit.al
[3]: https://community.dynamics.com/blogs/post/?postid=b8b9bcc2-9113-4a15-b9f6-39e859a5a61e
