# Record changes using JSFoundSetUpdater are not broadcasted

**URL:** <https://forum.servoy.com/t/record-changes-using-jsfoundsetupdater-are-not-broadcasted/21155>\
**Category:** Questions\
**Created:** [February 5, 2024, 12:05pm UTC](https://forum.servoy.com/t/record-changes-using-jsfoundsetupdater-are-not-broadcasted/21155 "2024-02-05T12:05:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bodnarescu.diana](https://avatars.discourse-cdn.com/v4/letter/b/87869e/32.png) [@bodnarescu.diana](https://forum.servoy.com/u/bodnarescu.diana)\
**Post date:** [February 5, 2024, 12:05pm UTC](https://forum.servoy.com/t/record-changes-using-jsfoundsetupdater-are-not-broadcasted/21155/1 "2024-02-05T12:05:37Z")

</div>

Hello,

I am using Servoy 2022.3.4.3746\_LTS and I notice that record changes done using JSFoundSetUpdater are not broadcasted.  
So if I am doing:

```auto
updater = databaseManager.getFoundSetUpdater(fs)
updater.setColumn('has_updates_chk',1)
updater.performUpdate()

```

The other active clients are not seeing this change (has\_updates\_chk = 1) on the respective records.  
I understand that changing data using JSFoundSetUpdater is ment for quick updates, and it skips table events, that is why i use it. And that it does the update directly in the database, but I would expect these updates to be broadcasted.  
Am I wrong?

Thank you,

---

<div class="post-metadata">

**Author:** ![jcompagner](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.servoy.com/jcompagner/32/4889_2.png) [@jcompagner](https://forum.servoy.com/u/jcompagner)\
**Post date:** [February 5, 2024, 4:01pm UTC](https://forum.servoy.com/t/record-changes-using-jsfoundsetupdater-are-not-broadcasted/21155/2 "2024-02-05T16:01:54Z")

</div>

that is never how it worked i see (when the foundset updater really is just doing a single update statement call)  
it does flush the current client, but it doesn’t flush for that datasource all clients…  
We should have mentioned this in the doc. you can make a case for that.

We could also potentially do it for you, so trigger a flush for that whole datasource over all clients… but that is quite a heavy operation.