...
<EagleML xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0%22 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" eaglemlVersion="2-0" eaglemlType="ReferenceTransactionMessage" xsi:schemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0 eagleml-main-2-0.xsd" xsi:type="ReferenceTransactionMessage">
<referenceTransaction>
<header>
<objectType>ProcessCenter</objectType>
<objectId>ProcessCenter</objectId>
<action>ADD</action>
</header>
<processCenter>
<objectType>ProcessCenter</objectType>
<objectId>ProcessCenter</objectId>
<objectDescription>OBJECT_DESCRIPTION</objectDescription>
<updateSource>MCADMIN</updateSource>
<processCenterName>V9</processCenterName>
<processCenterDescription>V9 TEST</processCenterDescription>
<currentDate>2018-07-16</currentDate>
<ccCurrentDate>2018-07-11</ccCurrentDate>
<ccMonthEndDate>2018-08-31</ccMonthEndDate>
<rollPriorPeriod>Y</rollPriorPeriod>
</processCenter>
</referenceTransaction>
</EagleML>
...
Ontology files:
src/resources/ontology/definition/eagle-vocab-definition-common.json
src/resources/ontology/eagle-mashups.json
src/resources/ontology/eagle-vocab-common.json
src/resources/ontology/eagledb-vocab-common.json
src/resources/ontology/reference/fieldattribute-models.json
src/resources/ontology/reference/fieldattribute.json
SDP-
...
DictionaryId and PerfFreqCode filters were previously added for EDS ontology based extract, but the same filters still didn’t work for the Warehouse Performance EDS dataset based extract. The filters were added and the issue was fixed.
Additional supported filters:
Parameter | Type | Filter SQL statement
dictionaryid default "MASTERTABLE.DICTIONARY_ID = :dictionaryid"
endeffectivedate DATE "MASTERTABLE.END_EFFECTIVE_DATE = :endeffectivedate"
perfsummarytype CHAR(2) "MASTERTABLE.PERF_SUMMARY_TYPE = :perfsummarytype"
perffreqcode CHAR(8) "MASTERTABLE.PERF_FREQ_CODE = :perffreqcode"
perfrollupreturnsid default "PERF_SEC_RETURNS.PERF_ROLLUP_RETURNS_ID = :perfrollupreturnsid"
Files changed:
core/datasets/warehouseperformance.json
SDP-58779 EDS warehouseposition resource was updated to support additional fields for load and extract
...
Please review corresponding pages for additional details on data cache functionality : https://eagleinvsys.atlassian.net/wiki/spaces/MC2/pages/2951086081There are also updated installation steps in case of deploying to In-Market [pages for additional details on data cache functionality : https://eagleinvsys.atlassian.net/wiki/spaces/MC2/pages/3202908179/Deploying+EDS+core+code+and+Ontology+to+In-Market#4.-Refresh-Resources-Dataset-Cache-and-Cache-Policies|2951086081
There are additional post-install steps for existing EDS clients: [https://eagleinvsys.atlassian.net/wiki/spaces/MC2/pages/3202908179/Deploying+EDS+core+code+and+Ontology+to+In-Market#4.-Refresh-ResourcesResource-Dataset-Cache-and-Data-Cache-Policies|smart-link ] .
Files changed:
src/eagleinvsys/mc2py/idsdataframe.py
...