I have an inline list that has about 500 entries. After scrolling down to find an entry it would be useful to go back to the top of the list without swiping a dozen times.
I want to stay on the current screen but go back to the top of the screen (which is the top of the list).
Is this possible with an action?
TIA
I believe you can only go back to the top of the screen (not the list itself) by tapping the title of the screen.
What I normally do in this situation is use 2 inline lists, and then add a floating button with an action that toggles their visibility.
Sweet workaround!
Making a IL visible/invisible means it will be “at the top” whenever it is made visible. Correct?
I am testing this after dinner! Plus another technique based on this!
Yes, that’s correct.
I have the selection (thanks) - now I want to add each selection into another table. I would typically use a loop for this but I don’t see that within Glide.
Is their some way to process a sheet/relation and insert into another sheet/relation using Glide?
Net/net: I want to merge data from one relation into another relation:
while (not at end of relation) { add row ( rel1.name → rel2.name…etc)}
BTW…nice golf app example
My question is on efficiency.
I have a large table of accounts (2,000 +) shared among a number of companies. Sales reps at these companies can select targets from this list (typically a few dozen).
I was initially going to have a separate table <security concerns, etc> with these entries but I also could employ and have each rep have their own column of “my targets” stored within the much larger table (could grow to 10,000+). I would hope this is a sparse column since if it wasn’t it would be very wasteful.
The former requires that I select data from the large table and enter it into the smaller, user-specific table. The latter means a simple (I think)
Thanks.
Not sure I’m completely following, but if I’m understanding correctly, you have an inline list of accounts. A user scrolls though and selects an account, which marks that account somehow? If so, what changes on that selected row?
The use case is:
User selects accounts to work on from a global list of account and it is now “their account” to work on and would show up on a much smaller “working” list of accounts. They would not be going to the global list very often, they would be using the smaller, “working” list all the time.
Total account list - 10,000
Local/user account list - 40
As a demo I created a sheet with user/target-accounts as an example and now I need to populate the table in real-time (it is basically user-ID/account-ID).
Or maybe using a USC in the account list (e.g. a boolean Is-Target) and creating a relation (User-Targets == Accounts where Is-Target is (true)).
Hope this captures the details.
Can an account only be claimed by one user? I guess rather than transferring all of the data from one table to another, it seems to me like it would be easier to leave it where it is, and then have an extra column in the accounta table to claim it by adding the user’s email. Then you can filter that list of accounts elsewhere where the email is the signed in user’s email.
But, maybe you have other reasons for this. In that case, maybe you have a button on account details screen with a custom action that will first Add Row, where you can add all of the details from the accounts table to another table, followed by a Delete Row action to delete it from the accounts table. If you don’t want to delete the row from the accounts table, then maybe you can use a set column action to set a flag to make it hidden from the accounts list.
Accounts can be claimed by multiple users and are the “master” table. Targets are subsets of this list which individual reps (across multiple companies) can work on.
I just prototyped this:
Added a relation in user profile called Target Accounts (Accounts->Top Target is true). I added a USC column to accounts called Top Target. I “view as” different users and selected different accounts and this seemed to work.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.