# \[Solved\] PageData in Custom Experience Views

**URL:** <https://forums.losant.com/t/solved-pagedata-in-custom-experience-views/1453>\
**Category:** Help\
**Tags:** experience, dashboard\
**Created:** [January 17, 2019, 8:00pm UTC](https://forums.losant.com/t/solved-pagedata-in-custom-experience-views/1453 "2019-01-17T20:00:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kevin\_Jordan](https://avatars.discourse-cdn.com/v4/letter/k/8491ac/32.png) [@Kevin\_Jordan](https://forums.losant.com/u/Kevin_Jordan)\
**Post date:** [January 17, 2019, 8:00pm UTC](https://forums.losant.com/t/solved-pagedata-in-custom-experience-views/1453/1 "2019-01-17T20:00:53Z")

</div>

Over the past few months I’ve come to understand Experience Views using Dashboards but I’m attempting to create a device list using the Custom view and a Data Table where I am adding additional info to the device. The Workflow looks good as far as I can tell:

 ![37%20PM](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/1X/c3810314c6bb871e62835845bb73d8eddbbf38cb.png)

If I understand correctly, the Data Table info I’m putting in data.devices should be exposed by putting that in the Page Data Source.

However, when I go to the Experience view and refresh the actual page I’ve created, the context PageData is empty. Why?

 ![56%20PM](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/1X/b768ac41247fb2a33d49aa9883ea79265803bd88.png)

---

<div class="post-metadata">

**Author:** ![Brandon\_Cannaday](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/brandon_cannaday/32/14_2.png) [@Brandon\_Cannaday](https://forums.losant.com/u/Brandon_Cannaday)\
**Post date:** [January 17, 2019, 8:18pm UTC](https://forums.losant.com/t/solved-pagedata-in-custom-experience-views/1453/2 "2019-01-17T20:18:24Z")

</div>

The reason you’re not seeing the payload data is because you have the endpoint `/devices-custom` configured to render the `List Device (Custom)` page as a static reply. That option will override the workflow that’s also attempting to render the same page. You’ll need to change the `Reply Type` option to `No Static Reply (use experience workflow to reply)`.

The configuration you have (render a static page and also trigger a workflow) allows users to quickly return static content and then use a workflow to do any other processing required for that request.

---

<div class="post-metadata">

**Author:** ![Kevin\_Jordan](https://avatars.discourse-cdn.com/v4/letter/k/8491ac/32.png) [@Kevin\_Jordan](https://forums.losant.com/u/Kevin_Jordan)\
**Post date:** [January 18, 2019, 1:55pm UTC](https://forums.losant.com/t/solved-pagedata-in-custom-experience-views/1453/3 "2019-01-18T13:55:04Z")

</div>

Thank you Brandon! Seems obvious now.