# Persist dynamic view changes

**URL:** <https://forum.inductiveautomation.com/t/persist-dynamic-view-changes/96855>\
**Category:** General Discussion\
**Tags:** perspective\
**Created:** [October 4, 2024, 9:31pm UTC](https://forum.inductiveautomation.com/t/persist-dynamic-view-changes/96855 "2024-10-04T21:31:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![LukeL](https://avatars.discourse-cdn.com/v4/letter/l/bb73d2/32.png) [@LukeL](https://forum.inductiveautomation.com/u/LukeL)\
**Post date:** [October 4, 2024, 9:31pm UTC](https://forum.inductiveautomation.com/t/persist-dynamic-view-changes/96855/1 "2024-10-04T21:31:08Z")

</div>

I want to create a dynamic page that allows a user to add an embedded view and change the position of existing views. I figured out how to change the location through a popup via parameters and messaging, but it does not seem to persist. If I refresh the page it is back to the location it originally was designed at.

By accomplishing this, there is some limited expansion of the user interface if say a new tank is added..... (assuming the I/O etc. are all connected correctly). .

Is there a call or method that can save this information back to the gateway so it is permanent?

Alternatively should I be looking at an entire load from a database of all the properties when the application is started?

---

<div class="post-metadata">

**Author:** ![ryan.white](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan.white/32/73193_2.png) [@ryan.white](https://forum.inductiveautomation.com/u/ryan.white)\
**Post date:** [October 4, 2024, 9:42pm UTC](https://forum.inductiveautomation.com/t/persist-dynamic-view-changes/96855/2 "2024-10-04T21:42:16Z")

</div>

[This thread](https://forum.inductiveautomation.com/t/save-restore-component-properties-to-db/88383/8) may be of use.  
Save the configuration to a db table (or tables) whenever it changes. Load the configuration from the db on view startup or session startup and stuff it into a custom property.

Loading it on session start and placing it into a session custom property is probably the way to go because it only runs once, versus waiting on the DB every time you open the view that needs the configuration data.