Closed vinamato closed 1 year ago
Please find below the visual model used:
Please find below the PhysicalModel generated:
Hello,
as you can imagine it is difficult or just very time consuming for me to just look at both of your files and give you a precise answer. Please always state the used SDK version in questions. I suppose it is SDK 1.8? I see you have "value": "LOT-0001" twice in the visual model, this looks like a duplicate!? I know that there are issues in the editor demo with SDK 1.8 in the XML generation but it could be something in your data. Also note that the editor demo is just a demo, not a bullet proof application to be used in production, we try to improve it when we have extra time (outside of the work on the SDK).
Concerning the editor demo I would recommend you wait for SDK 1.9 to come out and use this branch to test this again: https://github.com/OP-TED/eforms-notice-editor/tree/feature/TEDEFO-2456-use-of-fields-attribute-information The algorithm for XML generation is better in this branch of the editor demo as it deals with attributes provided in 1.9. I had found a problem where the XML was missing something that was in the visual model, this has been corrected but in that special branch and it needs SDK 1.9, you could try the same thing with a release candidate: https://github.com/OP-TED/eForms-SDK/tree/1.9.0-rc.2 and the editor demo branch give above.
Ji @rouschr thank you so much for the answer. we will look in our data and we will let you know. In meantime, since the usage of 1.8 SDK version is mandatory, do you have a quick suggestion to fix the hierarchies in notice-type jsons? In fact, as per our understanding the issue in XML generation is related to the different hierarchies of the fields.json and notice-types. We observed that this has been fixed in 1.9 (at least for the notice 16.json).
As an esender you can adapt the SDK to your needs, as long as the produced XML is valid for your country and the EU. Perhaps you could use a copy of NTD 16 taken from 1.9 and adapt it for use inside of 1.8. There are other ways but those may involve reinventing the algorithm that generates XML to make it more tolerant of problems found in the NTDs (I have some ideas on that) but that is a lot more complex and difficult to do.
As 1.9.0 has been released, I consider this closed. Feel free to open new issues in case of trouble.
Hi, as per title, we're struggling in trying to generate a Physical model with notice subtype 16. The problem is that the final XML is loosing the "LOT-0001" references in GR-Lot group of the visual model. We're using the eforms core library and the endpoint "/xml/notice/save/validation/none" of he following demo project: https://github.com/OP-TED/eforms-notice-editor
Could you please tell if we're missing something in the visualModel?