You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the update to version 1.12, I have been experiencing difficulties with the XML transformation of the BT-127-notice and BT-728-Procedure fields.
Context
After analyzing this commit: 315a03a, I noticed two changes that seem to prevent the correct generation of XML files.
Identified Issues
BT-127-notice:
A nodeId "ND-ProcedureProcurementScope" was added to the "GR-Procedure-Description" level.
If I remove this nodeId (as in SDK version 1.11), the XML generation works correctly.
BT-728-Procedure:
"GR-Procedure-PlaceOfPerformance" underwent a nodeId change. Previously, it was "ND-ProcedurePlacePerformanceAdditionalInformation," but now it has been replaced by "ND-ProcedurePlacePerformance."
This change seems inconsistent to me because, according to the fields.json file, BT-728-Procedure has a parentNodeID = "ND-ProcedurePlacePerformanceAdditionalInformation."
I have noticed these inconsistencies across all subTypes:
Hi,
The group association shouldn't have changed and it should remain associated to ND-ProcedurePlacePerformanceAdditionalInformation,.
We will fix this in a next release
KR
Thank you for the clarification regarding the BT-728-Procedure.
However, I would also like some clarification on the BT-127-notice. As mentioned above, adding the nodeId "ND-ProcedureProcurementScope" to "GR-Procedure-Description" prevents the XML from being generated correctly. If I remove this nodeId (as was the case in SDK version 1.11), the XML generation works correctly. Could you clarify whether this is a bug as well?
Additionally, could you provide an estimated release date for the fix? Will it be addressed in a 1.12.1 update?
Hello,
Since the update to version 1.12, I have been experiencing difficulties with the XML transformation of the BT-127-notice and BT-728-Procedure fields.
Context
After analyzing this commit: 315a03a, I noticed two changes that seem to prevent the correct generation of XML files.
Identified Issues
BT-127-notice:
A nodeId "ND-ProcedureProcurementScope" was added to the "GR-Procedure-Description" level.
If I remove this nodeId (as in SDK version 1.11), the XML generation works correctly.
BT-728-Procedure:
"GR-Procedure-PlaceOfPerformance" underwent a nodeId change. Previously, it was "ND-ProcedurePlacePerformanceAdditionalInformation," but now it has been replaced by "ND-ProcedurePlacePerformance."
This change seems inconsistent to me because, according to the fields.json file, BT-728-Procedure has a parentNodeID = "ND-ProcedurePlacePerformanceAdditionalInformation."
I have noticed these inconsistencies across all subTypes:
Code Used
I am using the XML generation code from the following branch:
https://github.com/OP-TED/eforms-notice-editor/tree/feature/TEDEFO-2456-use-of-fields-attribute-information
Could you please clarify these changes and explain how to ensure the correct XML generation for these fields?
Thank you in advance for your help.
@rouschr @bertrand-lorentz
The text was updated successfully, but these errors were encountered: