> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/user-collections/user-collection-service-in-unreal/user-collection-views.md).

# User Collection Views

{% hint style="danger" %}
Due for Removal, please speak to support for further info.

**09/06/2025:** MSquared will no longer be supporting "user collections" as a concept (or datasources). If you want similar functionality, it will need to be implemented via an alternative storage system, e.g. the [KV Store](/platform-documentation/creation/unreal-development/features-and-tutorials/online-services/kv-store-service.md).
{% endhint %}

Typically when working with user collection, we want a filtered list of objects. An example of this might be a "picture frame" interactable object that allows the player to select an image to display from the user's user collection. This feature would like to filter the user collection for objects that have images. To do this, user collection views are the right way to go.

## How to Implement a User Collection View

To user user collection view, you will first need a view class (a class derived from `UM2_UserCollectionsView`). Ideally you should reuse a view that has already been defined the suit your needs. There is no point to defining two different view classes that both filter for images. This would only cause inefficiancies.

View classes need to override `IsObjectRelevantToView`. This function should return true if the input object meets your filter condition and false if not.

<figure><img src="https://970394512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft3SBfOIsRz4GCNFFpae7%2Fuploads%2Fgit-blob-07131e5a85aaaf1bad649ad9a91a2ccb80387297%2Fimage%20(93).png?alt=media" alt=""><figcaption><p>Example of overriden <code>IsObjectRelevantToView</code> that filters for objects with images.</p></figcaption></figure>

Once you have your user collection view class configured to your liking, you can call `GetUserCollectionsViewObjects` on your user collection service to grab a list of relevant objects. You should provide your view class as an arguemnt. Additionally you can specify if you want to include any updates to the user collection since the function was last called with a given view by setting `UpdateIfDirty`.

<figure><img src="https://970394512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft3SBfOIsRz4GCNFFpae7%2Fuploads%2Fgit-blob-b91f868ea6f1a8687c611447090f106a72b533ba%2Fimage%20(92).png?alt=media" alt=""><figcaption><p>Example of using <code>GetUserCollectionsViewObjects</code>.</p></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/user-collections/user-collection-service-in-unreal/user-collection-views.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
