Hello. Comparing the table views in the new Hub Content Views some of our datasets do not render the table. They are okay in current views and am able to query our map services. First glance, all I see is that ObjectID is not visible in the table, but neither is it in Roadway Block and this is fine. I haven't found a pattern yet but here are some examples, including our COVID-19 testing and vaccine data. This is a mix of tabular and spatial data.
https://opendata.dc.gov/datasets/liquor-licenses/explore?location=38.893384%2C-77.008900%2C12.67&sho...
https://opendata.dc.gov/datasets/liquor-licenses/data?geometry=-77.662%2C38.800%2C-76.356%2C38.987
https://opendata.dc.gov/datasets/crash-details-table/explore?uiVersion=content-views
https://opendata.dc.gov/datasets/crash-details-table/data
https://opendata.dc.gov/datasets/76a28737a6f84b3c92a421114acccca2_5/explore?uiVersion=content-views
https://opendata.dc.gov/datasets/enterprise-dataset-inventory/data
https://opendata.dc.gov/datasets/public-bike-racks/explore?location=38.900376%2C-77.022800%2C12.67&s...
https://opendata.dc.gov/datasets/public-bike-racks/data?geometry=-77.064%2C38.895%2C-76.982%2C38.906
https://opendata.dc.gov/datasets/dc-covid-19-vaccine-coverage-by-ward/explore?uiVersion=content-view...
https://opendata.dc.gov/datasets/dc-covid-19-vaccine-coverage-by-ward/data
https://opendata.dc.gov/datasets/dc-covid-19-tested-overall/explore?uiVersion=content-views
https://opendata.dc.gov/datasets/dc-covid-19-tested-overall/data
Can you help me identify the break?
Sure, I can help Alex. We've observed issues with items based on services that don't support pagination, which appears to be the commonality for the items you reference. We're finalizing how this will be presented in the interface, but my first recommendation would be to enable pagination for these services if at all possible.
Many of our older services still point to an older Oracle stack which does not support pagination. We have begun re-pointing/migrating to a new version but we are not yet ready for a full cutover. Will all our services unable to use pagination present this issue?
We're still supporting older services with the release next week, so there's nothing you have to do to make sure your tables continue to load.
That said, to provide a better user experience for tabular data, we are removing support for services that don't allow pagination within the next few months. We will make a formal announcement about these upcoming changes soon including a cut-off date, so stay tuned!
Hey Patrick, understood. Thank you for your understanding and continuing to support this. Yes, we will carefully expedite this effort so that we can meet your cut-off date. Let us know when!