App maintenance/Clutter clean-up

[MattLB]

In this very recent thread I asked the same question since I have wondered about this.

@MattLB

Now that you brought this up, from a design perspective I read (thought I read/thought I understood) that you should not use the ‘user profile’ table except for ‘user’ info from a security perspective.

But the user profile is the one table that is accessible in actions, visibility and filters so it has become a very wide row with lots of USC/xxx columns with many templates/filters plus relations and is the source for four of my five TABs and many ‘New Screens’,

Is this a reasonable/usual best practice? I especially needed access to data within actions which have a very limited scope.

TIA

@Jeff_Hager replied with good insight. Hope this helps.

Table relations & choice as filter

Hi there, I am struggling to use a choice as a filter with following structure. I have TOPICS SUBTOPICS CONTENTS The properties relate like this: A TOPIC HAS MANY SUBTOPICS A SUBTOPIC CAN BELONG TO MANY TOPICS A CONTENT CAN BELONG TO MANY TOPICS A CONTENT HAS MANY SUBTOPICS The target UX is like this Step 1 User chooses one TOPIC only Step 2 User is shown a list of CONTENTS & can filter the CONTENTS with the “choice” component according to the SUBTOPIC (the “chips” are SUBTOPICS). …