You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the data exploerer to filter a dataset, the columns in the output do not match what was presentied inthe data explorer. Equally, the order is random each time.
What is affected?
Downloads from the data exploerer after filtering.
Timeframe of solution
2024/2025 Quarter 1
Resolution date
Solution Details
What went wrong?
Why did it happen?
The solution implemented
How are we ensuring this does not happen again
The text was updated successfully, but these errors were encountered:
@NHSBSA-Open-Data this issue has been discussed in the past. Data Explorer displays in a random order (it's not a bug). It is not possible to define the order in BigQuery and that's how it works. We had also suggested some an alternative solution back in 2023:
In case we want to have another view in Data Explorer we can embed an extra column like "sr_no_for_order" while loading the data into the big query and remove that field while showing the data in preview. It will require some changes and development time and also if the user runs the query directly from the explorer or via API he will be able to see that column.
@Daniellappv The fact that November 2024 Contractor Details data uploaded not in a random order was what confused me the most - aware that the order is usually completely random but that this file didn't reflect the norm. Did I do something different with that file that I can replicate again, perhaps, please?
Overview
When using the data exploerer to filter a dataset, the columns in the output do not match what was presentied inthe data explorer. Equally, the order is random each time.
What is affected?
Downloads from the data exploerer after filtering.
Timeframe of solution
2024/2025 Quarter 1
Resolution date
Solution Details
What went wrong?
Why did it happen?
The solution implemented
How are we ensuring this does not happen again
The text was updated successfully, but these errors were encountered: