-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rule BR-CO-19 not working correctly #219
Comments
@oriol the "DescriptionCode" element is a requirement from BT-8. You change for 1.3.3 somehow broke InvoicePeriod that contains StartDate, EndDate and DescriptionCode... |
Reverting to the previous Xpath as it correctly implemented the rule plus the effect of mapping the DescriptionCode to BT-8. exists(cbc:StartDate) or exists(cbc:EndDate) or (exists(cbc:DescriptionCode) and not(exists(cbc:StartDate)) and not(exists(cbc:EndDate))) This checks positive when any of StartDate and EndDate are in the InvoicePeriod and the case where the InvoicePeriod is used just to carry information on the DescriptionCode to support BT-8 |
Did you test with the example above: <cac:InvoicePeriod> </cac:InvoicePeriod> |
Great thanks :) |
The test case might also include as success test
|
Added the test |
Requester name
Henry Buck
PEPPOL member company
MBIE
PEPPOL Area / components
POACC (PostAward) Ex: e-Ordering, e-Invoicing
Description
I have been creating test files to trigger the errors when a file fails the tests in the A-NZ schematron.
Rule BR-CO-19 is a PEPPOL standard, and the only way I could trigger this error was to
have nothing within the invoice period as follows:
The problem may be that the condition is missing parentheses and should read as follows:
Issue orignitated from Peppol https://openpeppol.atlassian.net/browse/PEPPOL-2857
The text was updated successfully, but these errors were encountered: