GDrive source data to be linked with a Parent Gsheet row

AppSheet AppSheet Q&A
1

Hello,

I recently discovered that Gdrive can be direct source for appsheet. With this source the underlying data are [_ID], [Path], [File], [CreateTime].[LastModifiedBy],[MimeType]

Is there a plausible way to REF_ROW this to a parent ID that would group them together?

Example. Spreadsheet Data are: Appliance, Consumables, Food. and i have files for Datasheet, Ingredient list, pictures etc; since this files will be stored together in one big folder. Ideally when im in appsheet I want to see in the detail view of Appliance, all related files reference to it.

I know alot of great people here have made something similar to this, care to share a similar feature?

2

The way is to create a virtual Ref column and select the correct parent table and itā€™s record with the app formula.

2 Likes
3

AFIK, you cannot add a column to a table based on a gDrive folder that references another table

As a workaround here is what you might want to try.

  1. Create a child table to the table containing the grouping items. The child should contain

child_id, parent_id (ref to the grouping items table), file_id (ref to the gDrive Folder table).

You can select/store relevant files from the grouping items tableā€™s detail view just like any parent-child tables structure works.

  1. Create an action on the child table of type ā€˜external: open a fileā€™ with [file_id].[file] (dereference is important) set as File.

  2. Set the row selected action of the inline view of the child table to the action created in step 2.

Hope this works for you.

2 Likes
4

Thatā€™s why I proposed a virtual column :wink:

1 Like
5

Are you suggesting to add a VC on the gDrive based table? How do you set the app formula? Each row should reference a different parent row and a user has no access to change the formula at run time.

Maybe I am missing something hereā€¦

EDITED: This is the strategy I have proposed.

TeeSee1_0-1673596484685.png

1 Like
6

A s it has the [FILE] column.. maybe you could use file names where it starts with the ā€œApplianceā€ etc. in the beginning and then you could read it with the app formula. Then use that as a key column in your parent table.

3 Likes
7

Right! That should work. Brilliant.

2 Likes
8

Youā€™re welcome!

1 Like
9

Thanks @AleksiAlkio and @TeeSee1

Awesome Ideas!! I think both are great in my use case. I think there are pros and cons for each.

For VC ref col: its pretty straight forward. scalibility-wise, to my undertanding VC calculate every sync. Idk if would impact sync time in the long run.

For Child table contianing file ID: theres a couple of step in the upload process. But it sounds stable(?) for the app. I wouldā€™nt mind a compromise in entry process for the sync time as this is only a sub-feature of the app.

Regardless, both ideas are solutions. Thank you!!

10

Youā€™re welcome!

If you donā€™t have a lot of file records and parent, the affect should be a little.

1 Like