LotResult EED fileds are missing in the generated pdf

[tompeeszter]

We are implementing the new EED fileds according to SDK 1.13.0.

Despite the fact that all EED (both LOT and LotResult) fields are filled in according to the existing rules, the data associated with the fields do not appear in the generated pdf.

              <efac:StrategicProcurement>
                <efac:StrategicProcurementInformation>
                  <efac:ProcurementDetails>
                    <efbc:AssetCategoryCode listName="energy-efficiency-item">el-mo-vsd</efbc:AssetCategoryCode>
                    <efbc:LegalFrameworkCode listName="energy-efficiency-basis">eed-spec</efbc:LegalFrameworkCode>
                    <efac:AssetMetric>
                      <efbc:AssetMetricCode listName="metric-type">nrg-sav-yr</efbc:AssetMetricCode>
                      <efbc:AssetMetricNumeric>12111</efbc:AssetMetricNumeric>
                    </efac:AssetMetric>
                    <efac:AssetMetric>
                      <efbc:AssetMetricCode listName="metric-type">nrg-con-yr</efbc:AssetMetricCode>
                      <efbc:AssetMetricNumeric>121</efbc:AssetMetricNumeric>
                    </efac:AssetMetric>
                    <efac:StrategicProcurementStatistics>
                      <efbc:StatisticsNumeric>8</efbc:StatisticsNumeric>
                    </efac:StrategicProcurementStatistics>
                  </efac:ProcurementDetails>
                </efac:StrategicProcurementInformation>

We have noticed the issue in notice subtype 29. According to29.efx, the data sould appear in section 6.1.4.

I send you an xml example.

Could you please invetigate the issue?

Thanks in advance! notice.pdf ted.txt

[pdonohoe]

Thanks for pointing out this issue. There is a bug in the EFX code which causes this, but to fix it requires a change to the EFX toolkit. This is unlikely to be changed until January.

[omrzljak]

We have this issue too. Generated XSLT contains no selector for EED. It has selector for CVD <xsl:for-each select=".[(efac:AppealRequestsStatistics[efbc:StatisticsCode/@listName='review-type']/efbc:StatisticsCode) or (efac:AppealRequestsStatistics[efbc:StatisticsCode/@listName='irregularity-type']/efbc:StatisticsCode) or (efac:ReceivedSubmissionsStatistics/efbc:StatisticsCode) or (cbc:LowerTenderAmount) or (cbc:LowerTenderAmount) or (efac:StrategicProcurement[efac:StrategicProcurementInformation/efbc:ProcurementCategoryCode/@listName='cvd-contract-type']/efac:StrategicProcurementInformation/efbc:ProcurementCategoryCode)]"> <xsl:call-template name="block051008"> <!-- fragment_invocation--> </xsl:call-template> </xsl:for-each> the last "or" wil output "StrategicProcurement" only if there is "ProcurementCategoryCode/@listName='cvd-contract-type'" present. So if xml also contains CVD details than EED and CVD will be in output.

Is there any news about progress of this issue?

[pdonohoe]

I'm sorry, I have no news about a date for when this bug will be fixed.

[pdonohoe]

@tompeeszter , @omrzljak I'm pleased to say this issue will be fixed in the SDK 1.13.2 release due in the next week or so.