Button from related tables don't show for some users

[Mônica]

I'm facing a problem that has no logic and I count with your help to solve it!!
In this print shared here we have this button "Adicionar", that is generated by a relation with another table, the problem is that some users see it and some don't!!
Anyone here already faced it?? Maybe the relation between the tables have something wrong... I really don't know and will really apprecciate if some of you could help me.

Thank's in advance!!

[WillowMobileSys]

Can you show an example of where a user DOESN'T see the button? 

[Mônica]

Here's the example

[WillowMobileSys]

It is best, in these cases to show the complete view.  Apps could have two near identical views but with different criteria.  We would need more details to determine if that was the case here.

For now, I'll assume that these two are the same Form view from two different devices.

With the assumption above, there are two things that come to mind that could cause the differences you are seeing between two different users :

1) Do you have some condition applied to the Add action on that inline table?  See image below.

2) Is there some expression at the TABLE level that might disable Add capability for a user?  See second image

Any Add action criteria inserted?

Any Table level expression to control Adds?

[Mônica]

Yes, I have one "Add" action criteria

[WillowMobileSys]

Ok.  This makes me believe then that there are 2 nearly identical Forms.  Your criteria is only allowing Adds in that one particular Form View.

Try changing the CONTEXT() function to this instead:

CONTEXT("ViewType") = "Form"

[Mônica]

I tried this and sadly doesn't worked.

[WillowMobileSys]

Since it seems like you could have two different views involved, the only other thing I can think of is that one view is based on a Slice and that Slice does not allow Adds.  See example of Slice specific definition below with Adds disabled.

Beyond this we woul dneed to dig deeper into you specific app details to pinpoint the problem.

[Mônica]

Two of the app slices allows "Adds".
If we could dig deeper into this I'll appreciate you a lot! Because this is an important app for my company, and without this button the app is basically useless

[WillowMobileSys]

Ok sure!  We need to determine , first, if the views are actually different and if so what datasources they are using.  

Can you replicate the issue in the Editor - one case showing the button and another case NOT showing the button? 

If you can then please provide a full image of the editor from each use case like that below.  This will show some View details in the lower left.  NOTE: if you are not aware, you can use the Preview As option to view the app as a different user

[Mônica]

I tried the "Preview As" option, and the view shows the button for me.
I shared here my view in the first image.

Running some tests, in "Share app" I turned his user to "Edit definition" and the button appear.
Here at the company we are investigating if's some problem with the browser or something related to the machine used.

This second image, shows the view from the user who doesn't see the button...

In another test the user who doesn't see it, logged in from another machine and could see the button... It is possible that the Appsheet has incompatibility with some versions of Chrome? Even if it doesn't make sense since they are two Google products...

[scott_robinson]

Are all the users on the same version rollout of your app?

[Mônica]

I guess so...

Is this where I can check it?

[Mônica]

Guys, I came back to say that apparently we found the problem, like I said we're investigating at the company and my gestor suggested to update the chrome version on the user's machine who wasn't seeing and this was what make the button show for the user!
Looks like Appsheet doesn't works with old versions of Chrome

[WillowMobileSys · Accepted solution]

The problem user was on a desktop?  You probably didn't know but that is important info to have upfront as desktop version of the app runs in the browser and not in a mobile app container like on mobile devices.

For future reference, the first thing to try on a desktop is to refresh the browser page.  If that doesn't work then clear the browser cache on that machine.

Probably more likely is that there was a cached version of the app that for some reason wasn't getting updated and all the user needed to do was to clear app related data.

[Mônica]

Yes, the user was on a desktop.
Thank you @WillowMobileSys, one more learning!!