Sorry Campbell needed to go off and do something else. Back on it now.
The fact.ultimus sounds fabulous, a boolean flag to filter in only the most up to date version of a value. I assume it hasn’t quite been implemented yet as its returning the same values as the fact.ultimus-index? And from the values I’ve looked at – examples below – an index of 1 would be the original or first reported value and does an index of 5 mean that, in its reporting life time, it has had five unique values or its just been reported 5 times (been in 5 filings of whatever type)?
{
“concept.local-name”: “Assets”,
“fact.value”: “241086000000”,
“fact.has-dimensions”: false,
“report.id”: 191866,
“period.instant”: “2017-07-01”,
“report.period-end”: “2017-06-30”,
“entity.name”: “MICROSOFT CORPORATION”,
“report.type”: “10-K”,
“period.calendar-period”: “2Q”,
“period.fiscal-period”: “Y”,
“period.year”: 2017,
“period.fiscal-year”: 2017,
“report.restated-index”: 1,
“report.restated”: 1,
“fact.ultimus-index”: 5,
“fact.ultimus”: 5
},
{
“concept.local-name”: “Assets”,
“fact.value”: “250312000000”,
“fact.has-dimensions”: false,
“report.id”: 218986,
“period.instant”: “2017-07-01”,
“report.period-end”: “2018-06-30”,
“entity.name”: “MICROSOFT CORPORATION”,
“report.type”: “10-K”,
“period.calendar-period”: “2Q”,
“period.fiscal-period”: “Y”,
“period.year”: 2017,
“period.fiscal-year”: 2017,
“report.restated-index”: 1,
“report.restated”: 1,
“fact.ultimus-index”: 1,
“fact.ultimus”: 1
},