# How to update Persistent Records default values

**URL:** <https://forum.inductiveautomation.com/t/how-to-update-persistent-records-default-values/88876>\
**Category:** Module Development\
**Tags:** database\
**Created:** [April 16, 2024, 11:54am UTC](https://forum.inductiveautomation.com/t/how-to-update-persistent-records-default-values/88876 "2024-04-16T11:54:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Roberto\_Neves](https://avatars.discourse-cdn.com/v4/letter/r/bbe5ce/32.png) [@Roberto\_Neves](https://forum.inductiveautomation.com/u/Roberto_Neves)\
**Post date:** [April 16, 2024, 11:54am UTC](https://forum.inductiveautomation.com/t/how-to-update-persistent-records-default-values/88876/1 "2024-04-16T11:54:29Z")

</div>

Hello,  
I want to update a persistent record table to change the columns default values, but the function context.getSchemaUpdater().updatePersistentRecords() only has any effect if I'm adding a new column, otherwise, the table just stay the same.  
Is there a way programmatically?  
Thanks!

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [April 16, 2024, 1:07pm UTC](https://forum.inductiveautomation.com/t/how-to-update-persistent-records-default-values/88876/2 "2024-04-16T13:07:48Z")

</div>

Are you expecting it to update existing instances of that record or are you looking at something else to change?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [April 16, 2024, 2:40pm UTC](https://forum.inductiveautomation.com/t/how-to-update-persistent-records-default-values/88876/3 "2024-04-16T14:40:57Z")

</div>

Defaults can only be set for a given column once, in our current ORM + SQLite combo. So either live with your choice, if it's already deployed to multiple gateways, or manually drop the table before your module recreates it (if it's a single gateway you can), or add an additional column with the new default and handle it with business logic.