Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
Hi everyone,
We have a need to clean up documents in our lower environment as it is consuming a lot of disk space. We identified two folders whose contents aren't needed currently. However, I would like to back them up just in case it's needed in the future. However, when I download the folder as a zip and subsequently unzip it, the folder hierarchy is different than how it is on Appian. It might not be a big deal for us but I did want to ask the community if they know of a way to preserve it? Following is the difference in hierarchy
Hierarchy in Appian
Hierarchy of the downloaded zip folder
Discussion posts and replies are publicly visible
Can you clarify what the difference is that you're finding to be unacceptable, like in plain speak? I notice the following highlighted difference but i'm pretty unclear so far what I'm supposed to infer from this.
One thing that does occur to me is that Appian folders and documents don't have any limitation against containing the "/" or "\" characters, even though these are strictly disallowed characters in file OR folder names in most operating systems. Thus it's probably doing some conversion (and maybe getting something wrong w.r.t. sub-paths) when you elect to "download as zip". In fact now that I think about it, it seems pretty clear that this is what it's doing - trying to change the "/" in dates into a sub-folder descriptor (and getting a bit clogged-up in the process).
What happens if you try renaming one of those folders to something conventionally filename-compatible (as well as ISO-compliant)? "9/30/2020 Report 1" would perhaps become "2020-09-30 Report 1". This uses the "correct" date format for computer usage and would have no such "folder name limitations" - and I'm curious if that would cause it to export with the folder structure you expect?
Hey Mike! Good to hear from you. Yes, so the difference is that there are 2 extra layers added to the folder structure in the zip folder. In Appian, it was "09/30/2020 Report 1" whereas in the zip folder, it turned to "12. September" -> 9 (month) -> 30 (day of the month). After reading your explanation, it does reaffirm my suspicion. I think that is what's happening too. I will try renaming it and let you know.
Good luck - let me know what you find.
Yup, you were right. When I updated the name of the report to "2020-09-30 Report 1", the zip had the folder hierarchy I desire.
Nice, thanks for confirming!