Daniel Göhler prisma informatik GmbH

If I accidentally delete the purchase credit memo created from an incoming e-credit memo in the e-documents module, it would be nice if you could recreate it as you can with incoming documents, where you can recreate deleted documents as long as they have not been posted.

Yammer: https://www.yammer.com/dynamicsnavdev/#/Threads/show?threadId=2711228532768768

The line id ../cac:InvoiceLine/cdc:ID of an Peppol BIS Billing 3.0 (https://docs.peppol.eu/poacc/billing/3.0/2023-Q2/syntax/ubl-invoice/cac-InvoiceLine/cbc-ID/) for incoming e-invoices will be converted to an integer even though it is defined as an identifier a.k.a. String (https://docs.peppol.eu/poacc/billing/3.0/2023-Q2/bis/#_identifier). It would be good if also non integer value would be accecpted.

Yammer: https://www.yammer.com/dynamicsnavdev/#/Threads/show?threadId=2711952846397440

As a Christmas present for 2023, Waldo has published a blog on how to dramatically speed up test execution (https://www.waldo.be/2023/12/28/speed-up-your-automated-tests-without-really-doing-anything/). The execution time of the vanilla Business Central ERM test suite was more than halved from 10 hours to 4 hours. It would be nice to have that kind of speed without splitting the tests into 25 codeunits per test suite.

Please add the error message to Event ID RT0010. Current I have received an "Extension Update Failed" for the BC24 update, but the message has no details:

"Extension Update Failed: exception raised in extension Base Application by Microsoft by null (updating to version 24.0.16410.18340)". 

The stacktrace (alStackTrace) is good:

"Feature - Report Selection"(CodeUnit 5409).MigrateCustomReportLayouts line 36 - Base Application by Microsoft

"Upgrade - BaseApp"(CodeUnit 104000).UpgradeReportLayouts line 10 - Base Application by Microsoft

"Upgrade - BaseApp"(CodeUnit 104000).OnUpgradePerDatabase line 12 - Base Application by Microsoft

"Upgrade Triggers"(CodeUnit 2000000008).OnUpgradePerDatabase(Event) line 2

Please add error details for failed upgrades to the Business Central Admin Centre. Currently you get "Update failed with an internal error FirstPartyUpgradeLogic and is being investigated."

That would be enough details for me. For example:

Update failed with an internal error FirstPartyUpgradeLogic and is being investigated.

Error Message:

Extension Update Failed: exception raised in extension Base Application by Microsoft by null (updating to version 24.0.16410.18340)

Stacktrace:

"Feature - Report Selection"(CodeUnit 5409).MigrateCustomReportLayouts line 36 - Base Application by Microsoft

"Upgrade - BaseApp"(CodeUnit 104000).UpgradeReportLayouts line 10 - Base Application by Microsoft

"Upgrade - BaseApp"(CodeUnit 104000).OnUpgradePerDatabase line 12 - Base Application by Microsoft

"Upgrade Triggers"(CodeUnit 2000000008).OnUpgradePerDatabase(Event) line 2

Note: I have also created an idea that shows the error message for why the data upgrade is shown for event id RT0010 (https://experience.dynamics.com/ideas/idea/?ideaid=38a15261-22fe-ee11-a73c-6045bdb93e93). This would also be nice if when details are added this should be displayed here.

It would be nice to see the concept of Runtime Packages taken to the next level. Currently, as mentioned here https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-creating-runtime-packages#create-a-new-extension-version-and-runtime-package, you need a runtime package for each Cumulative Update version and localisation if you don't want to include your source code. These runtime packages may or may not work on newer Business Central Version. For example, these runtime packages usually don't work with the next major and minor pipelines when you try to publish them to the docker container (sometimes you can't publish. Sometimes you can, but you get a runtime error in the tests).

Instead of producing C# intermediate code or the compiled assemblies - I'm not sure how this works internally - how about ether encrypting the code with a key that only Business Central knows, or obfuscating the code. For all I care, as an opt-in in resourceExposurePolicy. I would nag the ISVs where I need this new version.

The aim should be to make the runtime packages work for newer versions, if no breaking changes prevent this. It would also be nice to also remove the step of creating a docker container to create a runtime package. It takes a lot of time and resources to build a runtime package for each cumulative update version and localisation. Without Docker containers, this would be even better.

Many AppSourceCops don't make sense for OnPrem-Project, so adding the AppSourceCops disables all other rules, especially with the coming update.

To avoid collisions of object and field names, it would be nice if the AppSourceCop rule AS0011 "An affix is required" was also available in CodeCop (https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/analyzers/appsourcecop-as0011) for OnPrem-Project (ISV solutions as well as customer extensions). Just as None, so we can promote it as a Error.

It would be nice to be able to register UpgradeTags automatically when they are used, rather than having to add them via the event subscriber codeunit "Upgrade Tag" OnGetPerCompanyUpgradeTags or OnGetPerDatabaseUpgradeTags. I'm sure there's a technical reason why this is currently done, but it doesn't add any value to the development process.

Overview:

The proposed extension enables the assignment of multiple general or purchase journal lines to a single incoming document within Dynamics 365 Business Central. This functionality is crucial for organizations that need to split transactions across various accounts or dimensions from a single source document like an purchase invoice or expense report.

Key Features:

1. Multi-line Association: Enable incoming documents to be associated with multiple journal lines through the "Create Incoming Document from File..." or "Select Incoming Document" action. This enhancement addresses the current limitation where only a single journal line can be directly linked to an incoming document.
2. Automatic Row Creation: Users can create a new journal row from an existing incoming document. However, while additional journal lines can inherit details such as the posting date or document date, they currently do not inherit the associated 'Incoming Document Entry No.'. It would be beneficial for the system to automatically link these new lines to the original document to maintain continuity and traceability.
3. Improved Journal Line Usability: Upon selecting 'Journal Lines' within an Incoming Document, the Journal currently displays only related lines. However, newly created lines do not appear within this filtered view and consequently disappear from it. This feature should be enhanced so that all relevant lines, including new ones, remain visible and properly linked under the same Incoming Document.

This enhances Business Central by enabling multi-line associations for incoming documents and improving the usability of the system for its users, thereby streamlining accounting processes.

Objective:

We have a Business Central Online that has an empty record in the currency table, which is causing all kinds of problems. No one knows how it got there: By Code, by Rapid Start Configuration Package, ...?

To Ensure data integrity within Microsoft Dynamics 365 Business Central by preventing the creation of critical setup records with empty codes, such as currencies and payment terms, and making them easier to manage and correct.

Key Features:

• Validation Gatekeeper: Implement stricter validation rules in the platform that prevent the creation of setup entries with empty codes across all data entry points, including backend processes like code execution and Rapid Start Configuration Packages.

• Cleanup Tool: Introduce a user interface tool that allows administrators to easily identify and correct invalid records. This tool would list all setup entries with empty or invalid codes and provide options to either correct or delete them directly through the UI.

• Automated Correction Suggestions: When invalid setup entries are detected, the system could suggest valid alternatives or corrections, streamlining the cleanup process for administrators.

Benefits:

This extension reduces support and enhances system stability and reliability by preventing problematic record creation and offering robust tools to manage and correct existing setup entries, thereby addressing critical data integrity issues within Business Central.