Replies: 5 comments
-
|
The warnings are for the XRechnung schema, which currently is not supported by default. If you dont require xrechnung compliance you can safely ignore this and use the |
Beta Was this translation helpful? Give feedback.
-
|
yes, XRechnung is target schema i have to achieve. <rsm:ExchangedDocumentContext>
<ram:BusinessProcessSpecifiedDocumentContextParameter>
<ram:ID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</ram:ID>
</ram:BusinessProcessSpecifiedDocumentContextParameter>
<ram:GuidelineSpecifiedDocumentContextParameter>
<ram:ID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</ram:ID>
</ram:GuidelineSpecifiedDocumentContextParameter>
</rsm:ExchangedDocumentContext> |
Beta Was this translation helpful? Give feedback.
-
|
To achieve this you'd currently have to create your own profile. For reference, you can take a look at |
Beta Was this translation helpful? Give feedback.
-
|
I've already tried that, but I'm struggling already with importing all the necessary stuff. import { createProfile } from "../factory";
import { type InferSchema } from "../../types/schema";
import { BASIC } from "../basic";
import { en16931Schema } from "./schema";
import { getAsset } from "../../utils/asset";
import { en16931Mask } from "./mask";
...
import { type Schema } from "../../types/schema";
import { dateTimeStringFormatter } from "../../utils/helper";
import { UNTDID_1153 } from "../../codelists/untdid/1153.gen";
import { UNTDID_7143 } from "../../codelists/untdid/7143.gen";
import { ISO_3166 } from "../../codelists/iso/3166";Unfortunately, I don't see a way to build this right now without a deeper understanding of your library. |
Beta Was this translation helpful? Give feedback.
-
|
The factory import is fixed in import { createProfile, dateTimeStringFormatter } from "node-zugferd/profile";
import type { Schema, InferSchema } from "node-zugferd/types";
import { EN16931 } from "node-zugferd/profile/en16931";
EN16931.schema;
import { /* ... */ } from "node-zugferd/codelist/<CODELIST>"; // See docsgetAsset is only used internally. you could use To use the mask you can simply copy it from the source code, they aren't extendable because they define the order of the fields. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
To Reproduce
I have generated an xml with ProfileEN16931 with date from your test case: en16931.ts
Here the exported XML: EN16931.xml.txt
When I validate this XML by using the KoSIT validator, several warnings are reported.
Current vs. Expected behavior
the report says:
so at the
<SellerTradeParty>is this tag missing:how can i add this required electronic address? as i can see, there is no schema available.
Do I have to create my own profile? Is anything missing there? Am I doing something wrong?
thx for your help.
What version of node-zugferd are you using?
0.0.8
Provide environment information
Which area(s) are affected? (Select all that apply)
Other, Types
Config (if applicable)
Beta Was this translation helpful? Give feedback.
All reactions