I am trying to link a screen which is already completed from a second input but when I link the old datasheet to the new navigation action, it opens a blank screen. Do I just have to re-make the other page? Or is there a way link the input to the already made screen?
Can you show us some screenshots? What does the âsecond inputâ mean in this context?
Sure thing! I have attached screen shots here. Basically its an ultrasound app. Now there is overlap for certain ultrasound scans where you may use the same views when evaluating different parts of the body. I have a âSubxiphoidâ page looking at the heart in a specific view. We also use this view to evaluate trauma patients as part of the âFASTâ exam. I want to link both the cardiac section and the trauma section to the same âSubxiphoidâ information screen.
Is there a way you can combine the two conditions? Then you wouldnât need the extra Show New Screen branch.
I dont think so the options are from two completely separate data sheets
hmm, actions are attached to tables. So how is it possible for the same action to be attached to two different tables?
Well thats what im saying. Since they are two separate data sheets I dont think it would be an option to make it the same action
oh, are you using Show New Screen â This item, or Show New Screen â Some other table?
If the latter, and each is opening a New Sceen on a different table, then yes, youâd have to build each screen separately.
thank you, i am doing that. Ok I think I can fix this
Hey So it looks like when I have a list of items in a data sheet and then navigate to the details patient of âthis itemâ that is shows the same page for every single navigation. Why is each selctions details screen the same?
In order to make each item have a separate page I need to navigate to a new screen and make a new data sheet for each and every item
How do I make it so I donât have to make each screen a new table?
You can use âShow new screenâ for each action but you have to do a âCopy Allâ between all your screens to keep them in sync if they show basically the same info.
Have you considered âShow detail screenâ and use your âif name containsâŚâ logic to build visibility/filter conditions based on what you are doing to tailor the screen? In this case you have more logic in a given screen but you can re-use the screen without worrying about 'Copy All" to a new screen every time.
I used to have âNew screenâ everywhere and did the âCopy Allâ since it was so darn easy in Glide. Unfortunately any logic change had me hunting down every âNew Screenâ to update it. By building a single detail/edit screen (or a handful depending on the number of tables) it minimizes the scaling issue of managing all the âNew screensâ.
I hope this make sense - in a nutshell try âShow detail screenâ or âShow edit screenâ in place of âShow new screenâ. In the long run having logic (via Visibility and Filtering in one place (Edit/Detail screen) is much easier than âShow new screenâ everywhere. BTWâŚGlide makes it super easy and intuitive to create New Screens everywhere which is awesome but can also lead to support challenges as the App gets bigger.
BTWâŚI had the same issues using âShow new screenâ (used it everywhere) and eventually revisited what I was displaying and why so I could use Action sequences to get the desired results. I like Action sequences (which are tied to tables) because in new Glide (I started under Glide Classic) they can be re-used so I can consistently apply the correct âscreen logicâ anywhere within the App I am using the tables.
1 Like