Visibility logic seems opposite in new platform vs Legacy

Ask for Help
1

Just want to confirm something to make sure this is correct.

I use the special values (UUID) to create a unique ID everytime I add a row.

When I want to hide something, a component with a default value that I do not want changed, I use visibility and in the OLD LEGACY CLASSIC APP I used
Show when UUID is EMPTY
and that used to work

in the new app, I have do set it to
Show when UUID is NOT EMPTY

Just want to make sure there was a change. I assume before it was writing immediately and now its waiting till submit

2

Why not just add a RowID to the table? Or are you already using it for something else?

This doesn’t sound right to me.
Just to be clear - you are talking about hiding components within a Form Screen yes?
Are you using exactly the same type of Form in both cases? (Classic vs New).
For example, I would expect different behaviour in a native form vs a custom form vs a form container.

1 Like
3

I think it may be different forms. I am using the built in ADD screen/function from a collection

New collection is type LIST and I do this to hide it

image
image1171Ă—607 56.1 KB

OLD one I created a ADD BUTTON and then did show FORM SCREEN
image
image

I guess I have been using UUID from before ROWID days, are you suggesting instead of using UUID, I use rowID and depricate UUID.

4

I think you mean you want to hide a component that you want to set a default value to it?

Then there might be a difference between how Classic and new Apps’ form screens see “special values” like UUID.

When you add a unique value to a column in the destination table:

  • Classic: Consider it as not filled until the form is actually submitted.
  • New: Consider it as filled.

Please let me know if this looks correct to you.

5

Up to you of course, but to me it just seems like extra work that isn’t really required.