I have groups within the ‘mobile’ page of my app where rather than navigating to different pages instead it just shows and hides groups as required. I am finding that some of the time when a value is updated in one group, that in turn updates the database, when navigating ‘back’ to another group which summarises that data by calling on it from the database, the rules behave as if the database is empty and display error messages I’ve added. However when I check the database the new entry is there as required, then refreshing the whole page restores the group and the data is shown. One fix is to refresh the page each time one of these events happens but playing around with this idea just now the user experience is not good. Does anyone know of a way to trigger a specific input to re-check the data when it’s parent group becomes visible? Or any other solution which could work? Many thanks
Just a prompt please, if anyone can offer any suggestions it will be greatly appreciated. thanks
Interesting.
So, you are using states to collapse the various ‘views’ and when you explode them you get something other than what is in the database at that very moment? Is this what you are trying to say?
DB queries are dinamically updated when data changes in DB, so there should be more to what you are describing if such problem exists.
Could you share more details about how you retrieve that summarized data, the root cause of the error messages etc.?
Thanks. I am not using states, perhaps this would help? I am not familar with them if so, any material you could guide me to please? Currently I set workflows to show and hide groups in a given situation.
Thanks. A value input when changed will trigger a workflow to update the relevant database (which it is doing each time). Occasionally (say 1 in 20) this triggers a conditional rule on another element reliant on the database being populated, when if not populated it shows a specific text message. If I refresh the page then all is right again. It feels like the elements reliant for rules and values on the database in groups other than that being updated need a trigger to refresh?
This is the root of the problem in my opinion. Could you share more details about this conditional?
Information about this workflow is also relevant. Is it a frontend workflow or a backend workflow?
Does not the DB change affect the displayed data even if you wait for a certain amount of time, without refreshing?
No, unfortunately not. I spent ages yesterday testing it and to begin with the chance of it happening was about 1 in 5 however after about 3 or 4 errors it started to take longer and longer until it just didn’t seem to happen anymore. It doesn’t appear to have any pattern.
Can you confirm via Editor → Data tab → App data that the DB record has been effectively changed while no effect happens in frontend?
I guess yes, just wanted to confirm. If so, this escapes my understanding of how server-side should be automatically updating client-side. There should be some caching that’s preventing the update to be noticed by the client-side, but that’s not what should be happening as per my understanding of Bubble inner mechanisms.
Is there any other conditional worth mentioning? I see you have two of them
I’d also try show/hide the group by placing the conditional throttling an action inside a Do when condition is true workflow, rather than placing it in the group’s conditionals tab, just to see if the behaviour is the same.
Sorry, where do I find the editor tab? When I check the database it is updated, I have it open on one screen and on a preview screen or the phone when I change the value in the input screen the database updates live so no problem there I think. The field reliant on that updated data though doesn’t see it.
Thanks, I will try this. I’ve started removing conditions and testing to see if it is a specific condition or order of conditions.
This topic was automatically closed after 70 days. New replies are no longer allowed.