Skip to content

[Bug]: E-Document: Data Exchange Format should explicitly specify that it is a PEPPOL implementation #7304

@georgepomazkov

Description

@georgepomazkov

Describe the issue

The naming of Data Exchange E-Document Format creates an ambiguity because it does not explicitly say that it is actually intended for exporting/importing PEPPOL only e-documents.

Expected behavior

The caption of the Data Exchange E-Document Format should provide a clear indication that this is a PEPPOL-specific format.

Steps to reproduce

  1. Create a simple Data Exchange Definition for exporting posted sales invoices with no mandatory fields.
  2. Create a new E-Document Service with the following parameters:
    • Document Format: Data Exchange
    • Specify the Data Exchange Definition created on the first step as the Export Definition for Sales Invoices
  3. Set up a Workflow implementing the E-Document Service and a corresponding Document Sending Profile.
  4. Clear the Local Currency Code field on the Company Information page.
  5. Configure the Document Sending Profile as default for a Customer.
  6. Create a Sales Invoice for this Customer.
  7. Fill out the Invoice, leave the Your Reference field blank.
  8. Try to post the invoice. The system should throw an error indicating the the "Your Reference" field should not be blank, which is caused by the Data Exchange E-Document Format implementation calling codeunit 1620 "PEPPOL Validation".

Additional context

No response

I will provide a fix for a bug

  • I will provide a fix for a bug

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions