# Request query context

**URL:** <https://community.forestadmin.com/t/request-query-context/5243>\
**Category:** Help me!\
**Created:** [September 13, 2022, 8:27am UTC](https://community.forestadmin.com/t/request-query-context/5243 "2022-09-13T08:27:00Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![kll](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/kll/32/7091_2.png) [@kll](https://community.forestadmin.com/u/kll)\
**Post date:** [September 13, 2022, 9:07am UTC](https://community.forestadmin.com/t/request-query-context/5243/3 "2022-09-13T09:07:04Z")

</div>

Hey @anon39940173

I found the answer that I used back in the day : [Relationship dropdown edit widget filter - how to filter dataset based on current entity - Help me! - Forest Admin Developers Community](https://community.forestadmin.com/t/relationship-dropdown-edit-widget-filter-how-to-filter-dataset-based-on-current-entity/3752/2).

There was indeed a `context` object on the query which contained various data about, well, the context in which the query was made. Kind of the same information you would get from the header you talk about, but already properly parsed.

I started logging crashed for this (`TypeError: Cannot read properties of undefined (reading 'record')`) in either April or June of this year, when we upgraded our `forest-express-sequelize` version.

---

_[View the full topic](https://community.forestadmin.com/t/request-query-context/5243)._