Deliberatly freezing UI

Ask the community
1

Hi all.
I am trying to speed up a particular function that requires creation of hundereds of records. To make it run faster, I’ve moved the function to a service. That works well and its faster than the client side processing. However, I need to update 3 datasources afterwards. I can set the datasource to “Initially subscribe to updates”, but as far as I can see, it fires an update many times for some reason. The manual approach as far as I can see, is to disable the datasource and then reenable it afterwards. That works, but the frontend flickers which is not good.
Any suggestions on how to achieve this in a better way?
I guess I could run every datasource “Runtime only” and then return the three datasources through the result of the service call, but I would very much like to keep the datasources online.

Any feedback is appraciated :slight_smile:

Øystein

2

Hi Øystein,

I am unsure if this will work with initially subscribe to updates and services in combination, but “Pause render” works great for this purpose in App

image
image530×300 12.5 KB

Another option is to put the page in a loading state and ensure the Action in client waits for the service and then toggling the view on again.

If you have multiple updates and on the 3 sources that needs to be updated I am i would consider running the service using batched persists if you not already are. That usually helps on “update spam” from Subscribe to Updates :slight_smile:

Sondre

2 Likes
3

Hi Sondre and thank you for the reply. Totally missed the “Pause Render” feature. Works better now.
Øystein

1 Like