I have built a great database of companies (complete with filtering and adding to user lists) all thanks to the community here.
I was intrigued at the idea of taking this one step further, and letting users select companies (Add to shortlist) using the Trebuchet method, and then taking their outputs and pushing them into a user specific google sheet?
So the process would look like ( = completed already):
Go to company database
Add company to ‘shortlist’
Shortlisted companies appear on user profile
User specific G-Sheet created (manually)
Shortlisted companies are populated into the user specific g-sheet
Can you elaborate a little on what you mean by “User Specific G-Sheet”?
For example, do you mean a separate G-Sheet for each user?
If yes, my question would be - why?
What will you do with this? Will you use it inside your App, or is it for some other purpose?
My gut feeling is that you’re making this more complicated than it needs to be, but I think I need to understand what the end goal is before I could say for sure, or make any suggestions.
So it is a sheet that i make for each user, and we use it as a way to track relationships with customers (sort of like a pipeline). As far as I’m aware the tables in Glide apps would be too inflexible so I’d rather link out to this sheet and work from there.
It should be findable via the app, and people should be able to add ‘opportunities’ to the gsheet from the App. Maybe I am making it too complex but all the users will use a sheet for a pipeline and it makes more sense for us that way
Will your users have direct access to these G-Sheets?
If they won’t, then I would discourage you from taking this approach. And even if they do, I’d still discourage it.
But anyway, lets assume that you continue down this path, you’d have to do something like the following:
When a user favourites a company, you’d need to modify your existing custom action so that a row gets added to their “Personal” table (which is linked to their “Personal” G-Sheet.
The problem with this is because every user has a different sheet, you can’t just configure the action once and make it work for all users.
You’d either have to setup a separate companies screen for each user, or have some crazy custom action with a conditional branch for each user. Either way, it would be an absolute nightmare to maintain. Especially if your user list changes.
I suppose another approach could be to send a webhook to Make, and then let Make figure out which sheet to update. But that’s just shifting the nightmare elsewhere.
Honestly, there are better ways to approach this. If your users need their Company list in a spreadsheet outside the App, I think what I would be inclined to do is give them a CSV export option.
I think you’d be surprised. I think you’re still fairly new to Glide, yes?
As you learn more about it, you’ll find that is quite possible to build some very complex workflows. Something like managing a pipeline would definitely be quite doable.
= completed already):