OPT-200-Organization-Company wrong position in XML structure

[user6330]

Hello,

Looking at the notice-editor demo, when I compile this

It returns in the Physical Model a.k.a XML structure as

But looking at the fields.json, the xpathAbsolute is
/*/ext:UBLExtensions/ext:UBLExtension/ext:ExtensionContent/efext:EformsExtension/efac:Organizations/efac:Organization/efac:Company/cac:PartyIdentification/cbc:ID

so it must be under ext:UBLExtensions/ext:UBLExtension/.. and not under root.

I've tried some custom implementation, and I arrived to this structure

But when I try the asserts condition to validate, I found out that is missing
efac:Organizations, parent of efac:Organization.

Is It possible that the problem it's in the missing "nodeId" in hierarchy of the field "" inside the notice-subtype .json (in my case 1.json, but I think all the other notice-subtype)?

{
"id" : "GR-Organisations-Section",
"contentType" : "group",
"displayType" : "SECTION",
"description" : "Organisations",
"_label" : "group|name|GR-Organisations-Section",
"content" : [ {
"id" : "GR-Organisations-Subsection",
"contentType" : "group",
"displayType" : "SECTION",
"description" : "Organisations",
"_label" : "group|name|GR-Organisations-Subsection",
"content" : [ {
"id" : "GR-Organisations",
"contentType" : "group",
"nodeId" : "ND-Organization",
"displayType" : "GROUP",
"description" : "A Party involved in the Competition from either side (Buyer or Tenderer) with a Legal Entity (Company) and possibly additional Contact Points (touchpoints)",
"_label" : "group|name|ND-Organization",
"_idScheme" : "ORG",
"_schemeName" : "organization",
"_identifierFieldId" : "OPT-200-Organization-Company",
"_captionFieldId" : "BT-500-Organization-Company",
"_repeatable" : true,
"content" : [ {
"id" : "OPT-200-Organization-Company",
"contentType" : "field",
"displayType" : "TEXTBOX",
"description" : "Organisation Technical Identifier",
"_label" : "field|name|OPT-200-Organization-Company",
"_idScheme" : "ORG",
"_schemeName" : "organization",
"hidden" : true
}
.............

[elerik]

Hi
well check xmlStructure in field.json. This might to help you and eventualy you will get correct xml nodes.
Anyway 1.json or X.json I avoid them for this. What i understand its more like visual map for us how to provide fields to our users in logic way and how to visualize requested data (for that they are pretty good). There can be differences (now or in future) for final xml (i think thay call it physical model)

[AlexAS81]

Has this problem been fixed in any of the newer versions of the SDK?