Download Files bugs using file IDs

 

@Adam-google @Arthur_Rallu @wabrian 

 I have been reporting "BUG" in download file action which is not working properly, but the support desk (both Japanese / English) not understand what the problem is. Again, I can t spend my precious time to educate and coach your help desk personnel's, so let me post here.

There are two bugs. (Dont ask me when it started , as I m utterly no idea)

1) First bug

We can set the value for File type column with the strings like "DocId=xxxxx" to access to the file saved in the app owners Google Drive.  xxxxx stands for the file ID for the target file. It has been working fine for years. However, now once we hit the action on file type column, it initiates the download and the file is saved in the local drive. However, the file name of the downloaded file is "DocId=xxxxx", while it was before downloaded in the name of the original/source file with the proper extension.  So now, the downloaded file name does not carry the extension, unable to open those file completely. Perfect and beautiful bug.

Koichi_Tsuji_0-1736400708184.jpeg

 

2) Second bug.

I personally suspect this may share the same root cause as bug 1.   Once we hit action for file type column the download start (for excel and others file type).  Before we observe this bug, the downloaded file name is the same file name as the original/source file in google drive. However, strangely now the downloaded file name carries the FOLDER NAME _  (folder name + under score) .  The downloaded file can be opened so someone else may call this is not a bug. However, obviously the behaviour of the app action is completely changed.

Thanks for taking action to bridge this to dev team for immediate corrective action. BUG 1 is serious as the app action is not working to access to the files saved from App...... 

Hope you share our frustrations.

 

4 2 321
2 REPLIES 2

So in both cases the saved file name is not what you expect, but in the first case there is no extension while in the second case it does have the expected extension, is that right? Does it seem like whether you get behavior 1 or 2 depends on the type of the file involved, or something else? Can you tell me what specific file extensions the original files have in both cases?

I assume I have already answered to your similar question in the different thread or is this new question?

Regardless of type of extensions, we are not able to download any file to the local. The file is downloaded actually, but the file name is always missing the extension as well as the original file name, as you see in the screenshot above.