Home › Forums › The XBRL API › Repeating facts from different documents
- This topic has 4 replies, 2 voices, and was last updated 9 months, 3 weeks ago by David Tauriello.
Monday, May 30, 2022 at 3:45 PM #201030
Some facts are repeating when extracting several documents in a single call. I can see the reason (tag/concept change), but don’t know the solution. Is there any way to remove those duplicating values, but keep the two tags/concepts in a query?
Here is my API call with row 2 and 3 being similar:
Tuesday, May 31, 2022 at 5:18 AM #201041
Just a little update: Missed part of my query that refers to a named range “CIK”.
In this very case it should stand for “0000789019” (for MSFT).
Tuesday, May 31, 2022 at 11:58 AM #201056David TaurielloKeymaster
Hi Timur – thanks for writing. I’m not sure what additional parameter you’re using from C6 on the Legend worksheet (?). If I remove that and update ‘fiscal’ to be the parameter ‘period.fiscal-period’ I don’t see any duplication:
Drop the query in A1, and use =XBRL.showData(A1,””,””,”1″) in A2
Let me know if there’s something else I’m missing.
Wednesday, June 1, 2022 at 12:10 PM #201080
Thank you very much for your reply. I forgot to fully correct my query for named ranges, hence the error.
But your correction is exactly what my query should have looked like. I have done exactly what you showed above and I DO get duplicating values – see D4 and D5 of the output (if xbrl.showData is in A2), which is $17,236,000,000 for 3Q of FY’2021.
So my question here is whether it is possible to introduce any parameter that would remove those duplicates (sort of a “unique” function maybe, but on the query level so that the per query limit is not effected that much).
Wednesday, June 1, 2022 at 9:42 PM #201099David TaurielloKeymaster
Hi Timur – these are different facts appearing in different reports. Look at the full concept.local-name for rows 4 and 5. Further, if you add
report.sec-urlto the fields to be returned, you can browse to the EDGAR entries and confirm the values are different.
IncomeLossFromContinuingOperationsBeforeIncomeTaxesMinorityInterestAndIncomeLossFromEquityMethodInvestments – https://www.sec.gov/Archives/edgar/data/789019/000156459021020891/0001564590-21-020891-index.htm
IncomeLossFromContinuingOperationsBeforeIncomeTaxesExtraordinaryItemsNoncontrollingInterest – https://www.sec.gov/Archives/edgar/data/789019/000156459022015675/0001564590-22-015675-index.htm
When you review the face of the report these fact values do have the same label – https://api.xbrl.us/api/v1/label/search?dts.id=456408,583061&concept.id=27969523,31293140&fields=concept.id,concept.local-name,label.role-short,label.text – it may be that the company’s external reporting team reconsidered the definition it had been using, and decided to transition to a new concept.
The XBRL API does not currently normalize facts with a mechanism as you describe that would evaluate and eliminate facts with duplicated labels like this.
- You must be logged in to reply to this topic.
Can the API be expanded to include DEF-14A (Proxy) Statements? 22 hours, 56 minutes ago
How to gracefully handle duplicate values 1 week, 4 days ago
Dictionary of concepts 1 month, 3 weeks ago
NAICS CODE 2 months, 1 week ago
Lists of similar concepts 2 months, 2 weeks ago
Documentation & Discussion
- Get started with Google Sheets OR
- Get started with Microsoft Excel OR
- Get access to as-filed data from us for other tools or your own app
- XBRL API Interactive Documentation
- The XBRL API
- XBRL Data Community
- 2022 US GAAP Taxonomy Viewer
- Live support - Monday, 3:30 - 4:30 PM ET
Who's using this free data?
API Use 2022 || API Use 2021
API Use 2020 || API Use 2019
API Use 2018
Join XBRL US
- Individual Options - Basic, Power User & Sole Practitioner
- For Your Team - Startup, Non-Profit, Academic & Corporate options
- Member Benefits Comparison Table
Using the XBRL API with the Public Filings Database
Unless otherwise agreed to in writing, any and all use of the XBRL API to authenticate and retrieve data from the XBRL US Database of Public Filings implies user consent and agreement with the XBRL US API Agreement. If you are unable to agree to these terms, do not use the XBRL API.
To use the XBRL API outside of Google Sheets, your account needs to be provisioned for OAuth2 access.
You must be logged in to post a comment.