Thursday, December 20, 2018 at 10:31 AM #118958
It used to be possible to sort on a field that was not returned, for example like this:
but that no longer seems to be working. If I move the report.id into the fields list it works fine, but then it also gets returned in the query.
Thursday, December 20, 2018 at 12:05 PM #118963
I checked with team and there haven’t been any changes that would impact
.sort, which is applied on returned fields per the documentation:
Any value returned can be sorted in ascending or descending order, by adding an additional property to a field value.
Maybe the sort is on one of the
periodfields in the query you posted – ? the BS Compare template uses this:
Thursday, December 20, 2018 at 4:59 PM #118982
All right – maybe it was never meant to work. Basically, the query I posted definitely used to work, but now it doesn’t. However, it’s entirely possible that it was never meant to work.
I think my question here really is: Is there a way to sort the returned fields on a field that is not itself returned?
I agree that the documentation would seem to indicate that you can only sort on fields that are actually returned.
You must be logged in to reply to this topic.
Join XBRL US
- Individual Options - Basic, Power User & Sole Practitioner
- For Your Team - Startup, Non-Profit, Academic & Corporate options
- Member Benefits Comparison Table
XBRL API Resources
- The XBRL API
- XBRL Data Community
- XBRL API Documentation (PDF)
- Getting Started with Google API Access
- Sample Queries (Insomina REST client) - requires account provision