Closed rkottmann closed 3 months ago
This is not a bug.
The problem with the non-working example is that it omits the id
on the second fx-instance
.
However it's only allowed to omit the id
on the first fx-instance
in document order. The reason is that the first instance is usually the payload instance holding the data you actually want to edit. Therefore there's the concept of the Default Instance
to reduce the typing effort in binding expressions or in cases where only a single instance is used.
As this confusion emerged from missing documentation i added a paragaph in the docs of fx-instance - i hope this does the job.
Thx. That really clarifies this issue :)
If I have two instances e.g. one local and one remote, then I can not use the default "id" (by not assigning an id attribute), but have to give an id to the fore-instance. This seems to be an unexpected behaviour for newbie-user like me. Is it a bug? If not, it needs documentation.
Below I try to show case the issue:
the referenced source xml
invoice-ubl.xml
: