LinkedIn
Twitter
This looks amazingโฆ
- Are all the images related to the same table?
The table isnโt created as of yet, the images are in folder structures on our server for the time being. I havenโt moved them. The table should consist of a [Key], [JobID], [ImageURL]
The structure of the files is:
Each folder is named after the [JobID] which is unique.
They would only need to be accessible by the App.
I hope this is what you meant.
Cheers
Hi Scott.
My App shows all vehicles within our workshop, each vehicle has a unique ID via JobID which canโt be duplicated. For each vehicle having a repair done there are a set of images take whilst in-progress.
So from your comments No 2 'Show me all the images for the JobID 1234.
Ideally for simplicity I would want a gallery, so it should be โShow me a gallery for images beginning with JobID 1234โ
All images are in one Google Drive folder called \ImagePath I changed how the upload structure works so all images are in one location and each set of images are altogether. So there is not a separate folder for each JobID:
The images are uploaded once each day by an access database running in the workshop which is totally automated. The images are selected for upload via a csv file and that csv file should be the table for the gallery.
We donโt need any fancy bells and whistle such as Doc AI or Google AI, we simply just need to show a basic gallery. So if I select the row which contains JobID 244786, then allow me to see a gallery where the filename (before the โ-โ character) = JobID from the row.
Does this make any sense?
Cheers
I almost overlook this important announcement! Better to push to new thread with other category rather than Quesion.
I wish to try this new feature as well
ID 473552
Im curious if this new feature enable us to access property of saved files, such as meta data, size, file ID (Google Drive assigned file ID), etcโฆ Any quick list for the available property is there to share?
Thank you.
โโ
Well I have this working, but it is very slow. Google script:
*/
function listFilesInFolder(folderName) {
var sheet = SpreadsheetApp.getActiveSheet();
sheet.clear();
sheet.appendRow([โNameโ, โDateโ, โSizeโ, โURLโ, โDownloadโ, โDescriptionโ, โImageโ]);
//change the folder ID below to reflect your folderโs ID (look in the URL when youโre in your folder)
var folder = DriveApp.getFolderById(โGoogle Folder ID Goes Hereโ);
var contents = folder.getFiles();
var cnt = 0;
var file;
while (contents.hasNext()) {
var file = contents.next();
cnt++;
data = [
file.getName(),
file.getDateCreated(),
file.getSize(),
file.getUrl(),
โhttps://docs.google.com/uc?export=download&confirm=no_antivirus&id=โ + file.getId(),
file.getDescription(),
โ=image(โhttps://docs.google.com/uc?export=download&id=โ + file.getId() +โ")",
];
sheet.appendRow(data);
};
};
Which populates a column in your Google Sheet (used as the table)
But it is painfully slow on loading the image.
It has been really difficult to figure out, but I got there.
Populating the sheet is not too bad as it happens once every hour and there are (now) usually only 500 or so images. But the slow issue is that the column I take the image from is still a URL:
So Appsheet has to try to change that to an Image. Iโm sure the guys at Appsheet will soon have an update so we can just load images direct from Google Drive.
Question: Can an array be built in Appsheet before the URL is converted to an image?
Ok so Iโve changed the URL in the script (Removed some characters from the folder ID for security):
If I have understood the recommendation, does this look correct to you guys?
The script returns this in the Google Sheet (Notice the column [Download] and [Image] both have data):
This is the structure of the table in Appsheet:
So if I look at the table data in Appsheet notice what happens in the [Image] column, it is empty but the [Download] column still has the URL. The column [Image] also returns nothing in a view:
Changing both URLโs to:
Does allow the Gallery and Images to load slightly faster thoughโฆ
Update
As my images are exported via a workshop TV (linked to a PC) into the local (C:\users\dave.willett\Google Drive\ImagePathโฆ) via Microsoft Access, I am able to utilise the WIA - Windows Image Acquisition Library to reduce the imge size before it gets to the Google Drive and therefore a 737kb file is now approx 45kb and they load much quickerโฆ 
Happy new year once again @Scott_Haaland
Yes, appsheetโs โrelative pathโ to the target file should be the most shortest way to reach out to files rather than Google drive file ID based URL. I m not checking from technical aspects, but it should make sense.
Google drive โDriveAppโ Class is providing the methods to get the folders name where the target files are sitting in. So I believe your engineering team can relatively easily add this property to the new table feature. 
I could not loacate your previous post, but I remember the new feature yet able to get the nested folders and tree structure to get the meta data. However, as you can imagine, the most of the practical use case of the drives are using tree structured folders system to store the required data. I hope the application to the tree folder system to get meta data even from the child folders is on the scope for the further development.
Thank you.
Hi Mike @Mike_Procopio
Thank you for your response and advice.
Most importantly, welcome to Appsheet community place,
Out of my own opinion, the issue, i.e. the difference in the speed to render image through the different URL is purely because of Appsheet image rendering system rather than Google Drive and file APIs.
The url is captured on the data source, and required URL should be in place.
I did a bit of investigation.
Lets say we have two different set ups.
Set up 1. URL to image file using google drive, which looks like something like https://drive.google.com/uc?export=view&id=xxxxxx
Set up 2. URL which Appsheet natively provide, which looks like something like /appsheet/data/myimage/dummy.jpg
Based on the setting, go to the app and get and copy the image URL by hovoring over the image and usual right click technique.
Naturally and interestingly, each set up returns the URL like this.
Set up 1 image full path url - https://www.appsheet.com/remote/https://drive.google.com/uc?export=view&id=
Set up 2 image full path url - https://www.appsheet.com/template/gettablefileurl?appName=
Both image url is starting with the same domain of www.appsheet.com, regardless of the difference of the set ups, but the rest of query strings are different. (naturally)
As a result, what is happning is set up 2 is rendering image far more faster than set up 1.
For now, to give the best tuned app set up to minimize the rendering speed on the app, my app stays with the set ups 2, as I recapped in my previous post, rather than using https://drive.google.com/uc?export=view&id=xxxxxx.
For me, it looks like the difference should be coming from Appsheet backend server logics and set up, in terms of how to reach to the target file , alghough it is entirely out of my guess work.
