sometimes I want to search by person, find a person, and add some notes
OR sometimes, I might want to add or view related files
OR sometimes I might want to find a person and add or view the jobs they have applied for
I have created 3 “people list” screens and each time tried to add a different collection at the bottom (Notes, files and jobs) but they all change to become the same as the one I have just changed
It is as though they all change at once to the same as the last one I create
I don’t understand exactly what you are explaining. It seems you might be on one screen S1 with a collection of people (let’s say) whose data source would be table A, and you also have two other screens S2 and S3 with collections whose data sources would also be table A.
When you change data on S2 for example, you are surprised to see the data also changes on S1 and S3. Is this the issue?
What you see in the layout editor, the user interface of your application, is akin to viewing tables in your database, it just so happens that the information is displayed nicely in the layout editor and displayed as tables in the data editor. But in the layout editor, you are looking at tables that look pretty.
So if three screens S1, S2 and S3 have the same data source table A, then when you change the data in table A, changes by and large will be reflected on screens with that data source, in this examples screens S1, S2 and S3. I say by and large, because it depends on which columns you chose to display. If you choose to display data that wasn’t changed in the first place, well then logically that data will remain the same on all three screens.
Hopefully this might clarify what you are experiencing in your app.
Change the Item Click action on your second and third collections to ‘Show New Screen’ instead of ‘Show Detail Screen’. Detail Screen layouts are inherently linked to their source table. Show New Screen will give you a new independent screen.
Thank you @nathanaelb - I am sorry I did not make my description clearer.
I have three screens with Table A (S1,S2 and S3) .
The issue is not changing Table A as this would naturally reflect the changes made to Table A in any other representation of data FROM table A (as would be seen in S1, S2 or S3)
The question is not actually about the data - the question is how can I have three separate screens like this
Collection People - Search - edit individual people record and a see a list ( related collectio) of linked Note records
Collection People - Search - edit individual people record and below that a list of related collection of adverts that the person has applied for
Collection People - Search - edit individual people record and below that see a list of related collection of all files that are related to that person
The issue is not the data - The issue is being able to configure there screens which each show a different relationship collection
Yes, I just wanted to clarify the issue for @nathanaelb
But I am not sure what @Jeff_Hager means
Change the Item Click action on your second and third collections to ‘Show New Screen’ instead of ‘Show Detail Screen’.
Am I on the worng track thinking I would have three separate menu items
People search and manage notes
People search and manage adverts
3People Search and manage files
When I say manage..
I mean that when a person is chosen and the details of the person is displayed, the relatiomnship between the person and the required related collection (either notes, adverts or files) are displayed and can be added to or deleted or edited
Let me try and restate this so I’m sure I’m clear:
You have a single collection of people
You want to search for a person, and then view the details of that person, and then see one of 3 separate details screens:
– Notes
– Adverts
– Files
Does that sound about right?
One way to do this would be to use a table collection, and then add 3 button type columns. One each for Notes, Adverts & Files. The action on the first button would be Show Detail Screen->This item, and the actions on the other two would be Show New Screen->This item (as Jeff described). This will give you 3 different and independent screen layouts.
Personally, I would take a different approach. What I would do is just use a single details layout, and then use a choice component to drive visibility conditions to expose each of Notes, Adverts & Files.
@Darren_Murphy
Exactly that is what I am trying to do.. well almost
You want to search for a person, and then view the details of that person, and then see one of 3 separate COLLECTION LISTS initially and then be able to choose a related recrod from teh collection list and THEN see a detail screen of the related row for
– Notes
– Adverts
– Files
I was just coming back to document my latest thoughts after playing with the Item Click parameter (which I have not used before) and “discovering” all the actions (which I have not been using so far) and realised that three buttons would be a way to go
But when I tried to put a button I could not see the relationships that I needed
Just now looking at your suggestion - what would the single details layout be - not a collection/list of people but just a search that goes straight to the detail screen for the person?
And I can see what you are saying in terms of using a choice component to orchestrate the display of the various related collections BUT how do you have a field (the choice field) that is a filed that does not exist in a table row??
Thank you, Darren! That is such a leap forward in what I could ever imagine - That is awesome
Thank you so much for going to all the trouble to create the video
So many new concepts here - I will be studying this video and “unpacking” all the (new to me) concepts for at LEAST the next 3 days!!1
I love it when I can learn new features and methods!"
Sounds like The user profile becomes like a “backpack” of miscellaneous fields - a bit like the old “Working storage Section” in COBOL
A place to shove all the flags and switches and random data that was needed between file accesses?
Do you have a methodology for a standard way of setting up your user profile miscellaneous storage?
The other question I have is this…
what is the way to display a related list aafter displaing the details screen of an “owner” or master record - (for soime reason it was not showing any of the relationships to the people records in the Actions section ..any idea why that would be?
You don’t want to use the relation for the button. The goal is to use ‘Show New Screen’ to link to ‘This Item’, which is is just a fresh version of the current screen, but can be designed independently. You would then use your relation on the new screen as the source of a collection.
PS, this is not related to Darren’s suggestion. Just want to clarify since there a couple of ideas floating around.
Thank you @Jeff_Hager I am following your thread and understand it is separate to the method being proposed by @Darren_Murphy - both approaches are brand new concepts for me and are both incredibly exciting - I love doing this..thank you also to @Darren_Murphy@nathanaelb for all your interest, time, effort and assistance - it is keeping the flame of passion alive and making sure it doesn’t get “snuffed out” in a vacuum of no rapidly and real time available help and support!!
Until I saw @Darren_Murphy’s Loom video I thought he was a child prodigy!! For the last few months that i have been on this support community, I have been beating myself up and thinking how slow I was …given here was this young person (@Darren_Murphy ) who is a master of Glide and providing incredible support and insights - at the age of 12 or 14!!
Ok I am happy for now
Not going to win any design or Ux/Ui awards but I now have solved my immediate need
Very open to hear how this can be iomproved using the method of buttons
MattLB I would really love to understand to what you are referring in this comment, and what it was that you meant by this comment "…and doing this for UI used up all your updates so you had to reduce/stop doing this flow).
There was a time not too long ago where updates were also counted against data changes within Glide Tables. Today, updates mostly occur when an action outside of Glide occurs: a data sync, a data exchange with a 3rd-party integration, an AI actions which too is a data exchange with 3rd-party AI models.
Updates were counted when data was written to a cell. User-specific columns are used extensively to build UI, such as using button as menu or tab items, or hiding and displaying components or containers. One single user could display and hide a screen item 100s of times just for the fun of it and that would eat through updates.
Nathan is exactly correct. For example, I would have a table and within the table would be User-specific columns to store user ‘choices’. A table used for reporting would store the last report setting each user selected. User-specific choices would be used to store UI settings for a specific screen (I had a calendar that showed different views and used these settings to remember each users’ view). Lots of examples.
The challenge was each of these ‘micro-updates’ cost a penny. And there was no way to model how many times a user would switch from one view to another or run one report or another. So re-designing the UI to limit choices was required or, as Nathan said:
" One single user could display and hide a screen item 100s just for the fun of it and that would eat through updates."
That is such a leap forward in what I could ever imagine - That is awesome
