How to gracefully handle duplicate values

[Jeff Krimmel]

Hi,

Here’s an example of a query that returns 32 instances of a repeated value:

https://api.xbrl.us/api/v1/fact/search?report.document-type=10-K,10-Q,1&entity.code=0001841666&period.fiscal-year=2020&period.fiscal-period=3Q&fact.value=303000000&fields=fact.*

I’m interested in the one that has dimension.local-name=”ProductOrServiceAxis” and member.local-name=”OilAndGasExcludingPurchasedMember”. Even then, I have 8 instances of this particular combination.

Is there a way to gracefully extract just a single instance of the value I need?

Thanks a bunch.

[david.tauriello@xbrl.us]

Hi Jeff – the 303000000 values are not identical; one is for the US and one is Egypt, so the only way to show one of these facts is to add fact.limit(1) to the fields. Depending on how you structure the query, you may get a different fact (US or Egypt).

Here’s the entire OilReservesMember ‘story’ – I’ve sorted by fact.value so you can see US and Egypt easily:

https://api.xbrl.us/api/v1/fact/search?report.document-type=10-K,10-Q,1&entity.code=0001841666&period.fiscal-year=2020&period.fiscal-period=3Q&concept.local-name=RevenuesFromCustomersAndNonCustomers&member.local-name=OilReservesMember&fields=concept.local-name,fact.value.sort(ASC),report.id,report.sec-url,dimension-pair

At this level, you’ll need to rely on your application to filter out the unwanted results, or specify additional an additional filter on the fact (fact.id, fact.xml-id, fact.hash) so you get the exact fact you intend.

The report.sec-url is included in the results for this query, so you can open the inline filing, enter ‘303’ (no quotes) in the search and see these facts in the report.

[Author]

Posts