Just adding this as a resource that can be linked to.
The below template demonstrates the basic technique that was described by @Jeff_Hager in this thread.
The concept Apps in that thread are all legacy Apps which cannot be copied.
7 Likes
Thanks for sharing Darren 
2 Likes
Hi @Darren_Murphy, I am unable to copy this template. Is there any other way to get this template? 
1 Like
It works for me. What happens when you try?
1 Like
It worked now. Sorry 
2 Likes
Copying templates seems to be a bit hit and miss lately 
2 Likes
@Darren_Murphy is this still the way to do it (if you don’t use server side workflows). Would you have a new template which can be copied? Trying to figure it out - but seems a bit complicated 
1 Like
I think it depends on the actual use case.
There are cases where server side workflows (or the Glide API) could/should be used, but this technique still has it’s uses. Certainly if you are working with User Specific columns, then this is still really the only option.
Which specific bits of it are you struggling with?
1 Like
@Darren_Murphy actually understanding which columns to create and how to set up the logic. Haven’t figured it out
1 Like
Do you need some help?
If you tell me more about your use case I might be able to help.
1 Like
@Darren_Murphy I have a table with user specific column where the user selects which items that are favorited/selected. The table has 10 rows which pulls same json from other table and each row is populated with data from the json file by query json column like suggested[0], suggested[1] etc for row 1,2,3. The user can select which of the rows that must be copied to third table based on the user selection/favorites. But then the first table is changed and therefore the json file will change and the user should consider which of the items that now should be selected/favorited. Makes sense?
1 Like
Kind of makes sense, but I don’t understand this part:
What causes it to change?
Can you show me some screen shots?
1 Like
@Darren_Murphy I show a table where the “favorites” are selected by the user
Different suggestions for places to go on holidays are found in “jsoninput” as json-object
number is used to pick the different indexes
nameForLIne is the path for the key in the json-file
name is the value of the key
favorite (USC) is the user selection
When I ask AI (for other places I could visit) I will get another json-file - and I can select those as favorite.
The favorites are copied to another table before a new json file enters this table
It would be cool to have access to a template with the setup - but maybe it is a hassle to do a copy of the legacy app?
1 Like
@Darren_Murphy oh - I now see that I have the template downloaded. I’m having a look
@Darren_Murphy The template gave the understanding of what was going on. Nice idea.
So you were able to apply it to your use case?
@Darren_Murphy yes - it did work. And it is a clever idea.
I would have liked that I could select all favorites and then add rows equal to the favorites in another table. I don’t see a possibility to do that without the new automation in workflows. (Well, actually you could use callApi I suppose)
At present I add/remove the favorite selected row in the other table but it is kind of slow. The selection is not instant as the add/remove row takes time