"Initially Subscribe to Updates" issue

Ask the community
1

Hi guys. We have an issue which I am unsure if it is a bug or if there is something I dont understand correctly.
I have 2 separate datasources. Both subscribes to updates. The second datasource has a server side filter on it based on the content of the first datasource. When I update the data in the first datasource from the first user in the first browser(primary by inserting or deleting records), the first datasource updates in the second browser with the second user. The second datasource that are based upon a filter based upon data from the first datasource, updates sometimes, but not all the time in the second browser with the second user.
Is this a bug, or am I using the wrong approach here? Its crucial to me that both datasources are updated in both browsers.

Any comments are appreciated :slight_smile:
Øystein

2

Hi Øystein,

I have attempted to recreate this based on your desciption, with two data sources which Subscribe to Updates, using an EXISTS IN filter on the second data source. I have inserted new records into the first data source from the first session, but the objects appear as expected in the second session.

Perhaps the size of the data sources is an underlying issue, or the type of filtering used. Are you able to share some more details of the setup (perhaps over DM, if this is more comfortable)?

Rhys

3

Thank you. I will use DM :slight_smile:

4

Hi @Oystein_Selbekk,

This might not be directly related to your case, but I struggled to understand why “subscribe to updates” sometimes didn’t trigger on updates made by other users.

In my case, I had a collection of articles that should become visible once their scheduled publishing time had passed. The filter on the data source was checking if publishing_datetime <= DateTime Now. I mistakenly assumed that DateTime Now would update automatically—it doesn’t.

The suggested solution was to add a timer that updated a timestamp in an app variable and then filter the data source against that timestamp instead. However, I didn’t like that approach due to its other implications.

What I ended up doing was adding a “publisher” service that regularly checks for articles where publishing_datetime <= DateTime Now and sets a boolean published = true instead. This solved the issue, and my database-connected source with “Initially Subscribe to Updates” now works as intended.

Just my two cents!

2 Likes