Daniel Göhler prisma informatik GmbH

If you have an error in an object, for example in a field, you'll get more errors than if the field didn't exist.

For example table 30102 "Shopify Shop" of the Shopify Extension (https://github.com/microsoft/ALAppExtensions/tree/main/Apps/W1/Shopify/app):

• Error in field Test[250] instead of Text[250] in "Shopify URL" results in 116 errors. (https://pastebin.com/PqPpnSt0)
• Removing the field results in 29 errors. (https://pastebin.com/EtYEhv2U)

My suggestion would be that if the field has an error, just ignore it if the AL field is correctly formatted.

It would be nice if "Explore page in Visual Studio Code" in the page inspection would put generate a correct when you using Traefik.

Instead of

{

    "name": "AL: Generated Download Symbols request",

    "request": "launch",

    "type": "al",

    "server": "http://test",

    "serverInstance": "BC",

    "authentication": "AccessControlService",

    "port": 7049

}

it should be like this:

{

    "name": "AL: Generated Download Symbols request",

    "request": "launch",

    "type": "al",

    "server": "https://dockerhub.company.com",

    "serverInstance": "testdev",

    "authentication": "AAD",

    "port": 443

}

There are still a lot of SOAP web services out there. So it would be nice to see codeunit 1290 SOAP Web Service Request Mgt. upgraded to universal code. At the moment, the key procedures have OnPrem Scope and therefore can't be used in Business Central Cloud Environments, and only OnPrem if the customer pays the punishment fee for non-universal code.

It would be nice if vendors could send me a consolidated e-invoice, for example, for everything I ordered last month, and I could match that invoice with my multiple purchase orders on the Purchase Order Matching page in the new e-documents module.

It is a common scenario in many industries and is also possible paper base with the use of purchase invoice to import shipped non-invoice lines into on invoice. However, this functionality is currently not available in the new e-document module.

Yammer discussion about this: https://www.yammer.com/dynamicsnavdev/#/Threads/show?threadId=2711225746505728

I played around with this Peppol Validator (https://ecosio.com/en/peppol-and-xml-document-validator/, which uses https://github.com/phax/phive) and found out that the tax category for reverse charge in the CRONUS DK may not be correct.

In my option the tax category should be AE (https://docs.peppol.eu/poacc/billing/3.0/2023-Q4/codelist/UNCL5305/). If so, this applies also to other EU CRONUS Databases like DE.

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

It would be nice to be able to validate incoming and outgoing e-invoices against their schema definition XSD.

There is a good C# example from Microsoft on how to do this:

https://learn.microsoft.com/en-us/dotnet/standard/data/xml/xml-schema-xsd-validation-with-xmlschemaset#validate-xml-documents

I have adapted it to be valid against the PEPPOL Bis 3.0 UBL definition:

static void Main(string[] args)

{

XmlReaderSettings xmlReaderSettings = new XmlReaderSettings();

xmlReaderSettings.Schemas.Add("urn:oasis:names:specification:ubl:schema:xsd:Invoice-2", "https://docs.oasis-open.org/ubl/csd02-UBL-2.4/xsd/maindoc/UBL-Invoice-2.4.xsd");

xmlReaderSettings.ValidationType = ValidationType.Schema;

xmlReaderSettings.ValidationEventHandler += SettingsValidationEventHandler;

var fileStream = new FileStream("Cronus - Inovice 688001360.xml", FileMode.Open);

XmlReader xmlReader = XmlReader.Create(fileStream, xmlReaderSettings);

while (xmlReader.Read()) { }

}

static void SettingsValidationEventHandler(object sender, ValidationEventArgs e)

{

   if (e.Severity == XmlSeverityType.Warning)

   {

       Console.Write("WARNING: ");

       Console.WriteLine(e.Message);

   }

   else if (e.Severity == XmlSeverityType.Error)

   {

       Console.Write("ERROR: ");

       Console.WriteLine(e.Message);

   }

}

Currently, when processing an e-invoice in the new e-document module, you can only select Items and G/L accounts on the purchase order matching page. It would be good to also be able to select resources and item charges, basically all line types of the purchase order.

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

When I import a new incoming purchase invoice as PEPPOL BIS 3.0 into the new e-document module, the list of purchase orders opens, even though the OrderReference (https://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cac-OrderReference/), 106013, contains the information that this is my purchase order, and this purchase order has been shipped but not invoiced and has no other e-invoice link. It would be nice if the matching order was automatically selected.

Yammer: https://www.yammer.com/dynamicsnavdev/#/users/1562480739

In the e-documents module with outgoing PEPPOL BIS 3.0 Invoice the BuyerReference (https://docs.peppol.eu/poacc/billing/3.0/syntax/ubl-invoice/cbc-BuyerReference/) comes from Your Reference in the Sales Header/Sales Invoice Header. It would be nice if you could also use a fixed BuyerReference value from the customer card, because e.g. in the German XRechnung implementation why adds rules to PEPPOL invoice it is used for internal routing purposes like Leitweg-ID (https://de.wikipedia.org/wiki/Leitweg-ID).

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

If you have selected the wrong order in the Purchase Order Matching Page, it would be nice to be able to correct the mistake and change the associated purchase order to an e-invoice.

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