# Visibility logic seems opposite in new platform vs Legacy **URL:** \ **Category:** Ask for Help\ **Created:** [March 7, 2024, 3:55pm UTC](https://community.glideapps.com/t/visibility-logic-seems-opposite-in-new-platform-vs-legacy/71507 "2024-03-07T15:55:39Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Dan\_San](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dan_san/32/24085_2.png) [@Dan\_San](https://community.glideapps.com/u/Dan_San)\ **Post date:** [March 7, 2024, 3:55pm UTC](https://community.glideapps.com/t/visibility-logic-seems-opposite-in-new-platform-vs-legacy/71507/1 "2024-03-07T15:55:40Z")
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 ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [March 7, 2024, 4:17pm UTC](https://community.glideapps.com/t/visibility-logic-seems-opposite-in-new-platform-vs-legacy/71507/2 "2024-03-07T16:17:37Z")
> [@Dan\_San](#): > > I use the special values (UUID) to create a unique ID everytime I add a row. Why not just add a RowID to the table? Or are you already using it for something else? > [@Dan\_San](#): > > 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 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. ---
**Author:** ![Dan\_San](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dan_san/32/24085_2.png) [@Dan\_San](https://community.glideapps.com/u/Dan_San)\ **Post date:** [March 7, 2024, 5:27pm UTC](https://community.glideapps.com/t/visibility-logic-seems-opposite-in-new-platform-vs-legacy/71507/3 "2024-03-07T17:27:01Z")
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](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/0/2/028116982f9581e1b7709272dd12a66c3ef4f4cb.png) OLD one I created a ADD BUTTON and then did show FORM SCREEN ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/1/b/1b6d4e154a97415e7c56f0da315392c97c8ddd8d.png) ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/7/8/780e58bf3b0d933818b05c93094d497cdff2c553.png) > [@Darren\_Murphy](#): > > Why not just add a RowID to the table? Or are you already using it for something else? I guess I have been using UUID from before ROWID days, are you suggesting instead of using UUID, I use rowID and depricate UUID. ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [March 8, 2024, 1:18am UTC](https://community.glideapps.com/t/visibility-logic-seems-opposite-in-new-platform-vs-legacy/71507/4 "2024-03-08T01:18:35Z")
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. ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [March 8, 2024, 2:18am UTC](https://community.glideapps.com/t/visibility-logic-seems-opposite-in-new-platform-vs-legacy/71507/5 "2024-03-08T02:18:52Z")
> [@Dan\_San](#): > > I guess I have been using UUID from before ROWID days, are you suggesting instead of using UUID, I use rowID and depricate UUID. Up to you of course, but to me it just seems like extra work that isn’t really required.