Closed klmdb closed 1 year ago
According to Enrico this will be fixed in SDK 1.8
{
"id" : "GR-Lot-ContractExecutionRequirements",
"contentType" : "group",
"displayType" : "GROUP",
"description" : "Contract Execution Requirements",
"_label" : "group|name|GR-Lot-ContractExecutionRequirements",
"content" : [ {
"id" : "BT-736-Lot",
"contentType" : "field",
"displayType" : "COMBOBOX",
"description" : "Reserved Execution",
"_label" : "field|name|BT-736-Lot"
}, {
"id" : "BT-743-Lot",
"contentType" : "field",
"displayType" : "COMBOBOX",
"description" : "Electronic Invoicing",
"_label" : "field|name|BT-743-Lot"
}, {
"id" : "OPT-060-Lot",
"contentType" : "field",
"displayType" : "COMBOBOX",
"description" : "Execution Requirements Factor",
"_label" : "field|name|OPT-060-Lot",
"_presetValue" : "performance"
}, {
"id" : "BT-70-Lot",
"contentType" : "field",
"displayType" : "TEXTAREA",
"description" : "Terms Performance",
"_label" : "field|name|BT-70-Lot"
} ]
}
Problem
File
notice-types/16.json
doesn't containOPT-060-Lot
BUT DOES containBT-70-Lot
.Analysis
BT-70-Lot
depends onOPT-060-Lot
to create the correct xml node:BT-70-Lot
xpath expression:"/*/cac:ProcurementProjectLot[cbc:ID/@schemeName='Lot']/cac:TenderingTerms/cac:ContractExecutionRequirement[cbc:ExecutionRequirementCode/@listName='conditions']/cbc:Description"
[cbc:ExecutionRequirementCode/@listName='conditions']
to be present, in order to be able to parse it's value from the xml document.Because we build the xml document based on the xpath expressions of the nodes in the conceptual model, we need
OPT-060-Lot
to be present in the conceptual model in order to create the xml node<cbc:ExecutionRequirementCode listName="conditions">
. It is not present in the conceptual model though, because it is not part of thenotice-type/16.json
.Solution
Include
OPT-060-Lot
intonotice-type/16.json
. Check if this is a class of problems that needs to be solved generally.