> For the complete documentation index, see [llms.txt](https://resources.unizin.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.unizin.org/products/data-and-analytics/unizin-data-platform/release-notes/2.0.71-event-store-expanded-table-historical-backfill.md).

# 2.0.71

## Event store expanded table historical backfill

| Version      | 2.0.71       |
| ------------ | ------------ |
| Release Date | May 21, 2021 |

## Key Features

The complete breadth of historical event data is now backfilled into the recently developed [expanded events table](/products/data-and-analytics/unizin-data-platform/data-stores/data-lake/udp-event-store/expanded-table.md) in the UDP Event store.

## Details <a href="#id-2.0.71eventstoreexpandedtablehistoricalbackfill-details" id="id-2.0.71eventstoreexpandedtablehistoricalbackfill-details"></a>

Unizin has completed backfilling all historical event data from an institution’s production event store into the recently developed [expanded events table](/products/data-and-analytics/unizin-data-platform/data-stores/data-lake/udp-event-store/expanded-table.md). This enables institutions to completely migrate their use of event data from the events table to the [expanded events table](/products/data-and-analytics/unizin-data-platform/data-stores/data-lake/udp-event-store/expanded-table.md).

There are many advantages to the expanded table over the events table. Please consider reviewing our [guide to help you make the most of the expanded table](https://gitlab.com/unizin/products-docs-site/-/blob/master/docs/products/data-and-analytics/unizin-data-platform/release-notes/broken-reference/README.md).

{% hint style="danger" %}
**IMPORTANT:** **Unizin intends to retire the events table on August 1, 2021. Please ensure updates are applied to your queries to the new expanded table by this date.**
{% endhint %}

## Known Issues

None.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://resources.unizin.org/products/data-and-analytics/unizin-data-platform/release-notes/2.0.71-event-store-expanded-table-historical-backfill.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.