Open DeanFirkelj opened 8 months ago
Hi, Thanks for reporting this, we'll remove the constraint on the e-Sender
In Belgium we had the same problem. Our organisation is the national TED eSender, but at the same time it (or certain other divisions within our org) can act as a contracting authority.
We "solve" it by creating two organisations with two different company IDs. The CA org uses the regular VAT number from the national business registry as company ID, whereas the eSender org uses our TED account identifier ("eSender ID") as company ID.
Hi,
SDK v1.10
We have an issue with this case when eSender also acts as a contracting authority. If we create just one organization node, this validation rule prevents such situation: