> 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/udp-marts-release-notes/1.0.42.md).

# 1.0.42

## LMS and LTI Tool Mart Fix, Student Activity Score Mart, and Tool Usage Metrics Mart

| Version      | 1.0.42           |
| ------------ | ---------------- |
| Release Date | January 19, 2024 |

## Key Features

The [LMS tool mart](/products/data-and-analytics/unizin-data-platform/data-stores/data-marts/lms-tool-use.md) and [LTI tool mart](/products/data-and-analytics/unizin-data-platform/data-stores/data-marts/lti-tool-use.md) now employ LMS IDs as join keys instead of UDP IDs. The [Student Activity Score](/products/data-and-analytics/unizin-data-platform/data-stores/data-marts/student-activity-score.md) and [Tool Usage Metrics](/products/data-and-analytics/unizin-data-platform/data-stores/data-marts/tool-usage-metrics.md) marts are released to all tenants

## Known Issues

* The code for the LMS tool and LTI tool marts originally used the UDP course and person IDs for joins between the Caliper events and the context store tables. If the UDP ID associated with the LMS ID changed in the context store, but the change was not reflected in the event store, this could result in null context data populating the mart fields. By using the LMS ID as the join key instead, we make sure that the context information in the mart is up to date.


---

# 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/udp-marts-release-notes/1.0.42.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.