Could this be a bug?

[AlamBique1]

If I hadn't seen it with my own eyes, I wouldn't have believed it.

It's been three days since a software with several co-owners had an update on the DisplayMode event of the form's submit button. The condition of the text field called XX01 not being blank for the button to be editable was set.

If(Not(IsBlank(XX01.Text)), DisplayMode.Edit, DisplayMode.Disabled)

It worked fine and the app was published.

But another user claimed that the button was never editable for him.
As this other user was also a coownner, I asked to open the App for editing and navigate to the screen. The new code was right there on the button. And even then in editing mode for him the button really didn't enable.
When I checked more closely I saw that the component that for me was called XX01 for him appeared as XX05. Well, it's unbelievable.

The if tested the component XX01 which is correct when I open the App for editing. But for the other user XX01 did not exist.

Has anyone ever experienced this?

I renamed the field to txtXX01 and I still haven't been able to test it with the specific user, I hope this solves it, but... I never imagined that such an error was possible. Has anyone seen anything like this?

[narayan225]

@AlamBique1 

I have never seen such issue. You can check the Tree View of the screens and check if the component name is correct.

It could be that there are two components that both of you might have been seeing.

If you are sure that it is the same component, you might need to report this to Microsoft.

Hope this helps.

Cheers!

[Uditha_ISH]

Hi

Try with this formular,

If(IsBlank(XX01.Text), DisplayMode.Disabled, DisplayMode.Edit)

Thank you

UdithaIsh