When I change who’s using the app to complete the onboarding screen is getting to the FIRST row, and not actually to this item!
Screen is filter when email is signed-in user…
When I change who’s using the app to complete the onboarding screen is getting to the FIRST row, and not actually to this item!
Screen is filter when email is signed-in user…
This happened to mine too. I tried to make a new one, looks like works in dashboard, but when I closed and reopened, it went back to the first row of sheet.
I have many apps which I have this features, and the bug is in every single one
This is very frustating because I’ve been trying to fix it since this morning.
I have students submitting their projects and scoring to be done.
Complaints come from all users.
Happen to me too
Try, if you can, to workaround with a Link to a relation instead of This Item.
I will try too
I confirm in this way work.
I don’t like it, but to workaround I add a relation column to the same user (RowId -> Users Rowid), then Link Screen to the relation.
The deal here is that, if I use this option, We can’t use Detail screen
I have the same bug now
@Jeff_Hager is there anyworkaround that we can thing of its affecting alot of apps ?
A workaround is to link to the same sheet and make the same filter, I assume.
Can you explain more ?
In Lucas’ example, let’s say in the first screen he was pointing to the Profiles sheet. Then the button would be tied to a link to screen action, source being the Profiles sheet, and in the second screen we filter by email is signed in user as well.
Great … but if it was a product tab?
The same thing is happening in my projects.
The inlinelist component (this item) is reading only the first line of the product tab. (Bug)
The workaround I used should work for you too. That is, set a relation to the same row in the list, then point not on This Item but on the relation.
Got it. But when I create the ID - ID RELATION - and direct it (this item), it doesn’t have the “Details” style, making layout editing impossible.
Your work around seems to work fine
Thanks
@Mark this has to be fixed as in yesterday. I just emailed support directly because THIS ITEM being broken has caused data security to be breached in one of my apps which is sold to companies. This is not a workaround type of problem - it is breaking existing app functionality to the extent that it will cause me to lose business. I could be wrong and will eat humble pie if that’s the case - but in my app, you were actually the one who helped me set this condition for the component that is now broken and it was working fine until the issue was reported to me by a very upset customer calling me this morning.
Anyone using THIS ITEM should check their situation if it’s being used to wall off private data between certain users.
You are right about the exposure am working witht the team for the past 4 hours trying to rebuild screens because of it