For some reason, I am now plagued with “Current User” throughout many screens in my app. I don’t have a clue how they got there, but it seems the only way to remove them is to completely delete and rebuild each screen.
Has anyone else had this issue?
Hi @ThunderBlade,
If you delete & re-build, did you also meant you linked to that screen from other required screens back also? I guess it would be that, if screen B linked to screen A where no user data but there’s also a screen C which is linked to screen B that is passing user data, then screen A also gets user data. @Victor, what do you think?
Thank you and have a great day!
@ThunderBlade my opinion - if it doesn’t hurt your app’s logic, you can simply ignore it.
So here is the thing.
Let’s say my app has around 50 screens. Of all of those screens, only about 6 of them us the [Current User] function.
Where I am currently seeing [Current User] are on screens that have no connections to the actual screens that need [Current User].
That being said, on the screens that worked with no issues before I noticed this [Current User] thing, all screens functioned properly (as in the screens would capture the [Logged In User], which is what is supposed to happen).
With this [Current User] problem, I couldn’t create a new record at all….clicking the create button would produce no result.
I actually had to recreate every screen to wipe out the [Current User] anomaly…..now I can create records again, but I don’t think it is capturing the [Logged In User], so I added a property for the User ID. At least I can track that the records are being created and filed by the user that way.
This is really late in the game for me as the App was very close to beta testing when this happened.
And I have no clue as to why the [Current User] was tagged for pass through on every screen.
I am tying to ignore it, but I sometimes wonder if it is causing a problem when creating new records.
There really needs to be a way for a designer to remove unwanted property connection such as [Current User], from this list of passable connections when linking to another screen.
@ThunderBlade I absolutely agree that data flow should be configurable. But it sits in the core functionality of Adalo and I doubt this will be changed anytime soon.
Long time ago (2020) I noticed a “remnants” of visual settings somewhere, which looked like a “data access” configurations; it looked like you could add some data source to be sent to a screen. But they never worked and were removed eventually. So there was an idea but it was never implemented.
Maybe it could be a good idea to create a feature request for better data management / flow between screens.
Best,
Victor.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.