I’m experiencing an issue with updates that are not reflecting in the app outside the builder. Trying 3 separate devices, including on the same device I’m using the builder. Also tried in 3 different browsers.
Two data points i’ve noticed existing in different data tables, a boolean field, and a text field. When in the app.
The fields in question are used through the app so it’s obvious it isn’t reflected.
Anybody else experiencing the same issue?
Weird question, but an issue happened in the past for app created from templates. Does your app come from a template?
No I started it from scratch and have been using it for about 2 years. It’s a business critical app and has had probably 1000’s of hours of development time.
I’ve experience slow fetching from devices before but after a few refreshes it will update. At this point i’ve been waiting an hour. None of the instances mentioned are reflected what was done in the editor (and what I can see in the datables).
Can you make a loom to show how to reproduce the issue please ?
These are live records so don’t really want to be doing too much with them. But here you can see that in the editor a lookup value is empty as I deleted the ID reference that the relation uses.
However in the live app it is still showing the lookup value, which means the Slot ID must still be in the datatable.
Similar thing happening in a complete different DT with a boolean field.
Did you publish changes manually? I see that you are in manual publishing
What do you mean did I publish changes manually? I do when I want to release an update to the system.
I don’t think that’s the issue here. At the end of the day, there is data, and there is not data. I’m stumped at what else I could have done.
Could it have anything to do with the fact that this app is absolutely massive? 
I don’t think this is the issue… Are you using big tables ?
I’m not using big tables.
If you refresh the builder, does your change persists or does it revert back?
I’ll update my experience, today I tried something and it seems to have worked - although I can’t really explain why it had the effect it had.
It’s worth noting the the text field (Slots ID) that makes the relation through which I display the lookup field in the data grid in my video is used elswhere in the app that also reflected the field to contain a Slot ID unrelated to the lookup and relation that is being displayed in my video.
So, the data grid in my video is an old one, for some reason when I quickly created a new collection with the latest data grid layout and linked the lookup field, my live apps suddenly started to recognise the updated blank Slots ID as it correctly displayed a blank value because the relation is broken.
So I can sort of see how an old unsupported component might not display data correctly, but I don’t understand how it can affect the columns text field to literally be represented as something else in other parts of the app that uses the Slot ID field in separate relations/lookups/components.
I’m finding this all awfully difficult to describe 
That’s truly odd.