We would like to display a parent Folder name of the document in the Proof Approval report. Does anyone help us on this?
Many thanks,
Karthick N
Solved! Go to Solution.
Views
Replies
Total Likes
Sven, you shouldn't need to -- as long as you use collections, which I know you try to avoid!
I suppose you could do some sort of "if parent.parent.parent.parentID is blank" cascading valueexpression, which I know I try to avoid.
You would just start with that collection and move forward.
listdelimiter=<p>
listmethod=nested(documentVersion.document.folders).lists
type=iterate
valuefield=name
valueformat=HTML
You can't - traversing from the docVersion to the document works but you cannot go further.
That means you can get folderIDs and other properties on the document, but cannot follow the reference to folders to get the name.
You shouldn't use folders to "tag" or classify documents - use custom fields instead.
Hi @KarthickNa1!
Unfortunately no, from a proof approval report I tested many possible connections on this from the documentVersion, nested(document.folders).lists, docfdr, folderIDs, and more without avail.
@Sven-iX is onto something though for using a custom form / field that could be attached at the document level (and filled through Fusion) that could pull in that identifying information along with additional metadata.
Ping back if you have any additional questions around that!
I don't think you can get the parent (the top most folder)? As far as I know, it's only possible to get the folder that contains the file. So if you have a structure like this:
Folder 1>
Folder 2>
File
You can only get "Folder 2"
Views
Replies
Total Likes
From a DOCU object you can get up to 4 levels folders:parent:parent:parent:name
Bummer is I can't do that (not even the immediate folder) in a calculated field
Views
Replies
Total Likes
Sven, you shouldn't need to -- as long as you use collections, which I know you try to avoid!
I suppose you could do some sort of "if parent.parent.parent.parentID is blank" cascading valueexpression, which I know I try to avoid.
You would just start with that collection and move forward.
listdelimiter=<p>
listmethod=nested(documentVersion.document.folders).lists
type=iterate
valuefield=name
valueformat=HTML
@skyehansen I'm going to mark this as the correct answer because that's what @KarthickNa1 originally asked for.
And without fusion or calculated fields huzzah!
I'm curious - any idea how to get to the folder above it? I can't get that to work.
listdelimiter=<p>
listmethod=nested(document.folders).lists
type=iterate
valuefield=name
valueformat=HTML
Views
Replies
Total Likes
that's personally what I thought Karthick was asking for, and the part I'm too lazy to nail down. My guess/thought is that the "parent" folder is the parent.name, so the valueexpression should go something like "if parentID is blank, then give me the folder name, otherwise give me the parent.name" -- as a basic example of how to get to the upper level of folders.
Now, you mentioned you could get 4 levels, so it should start out with if parent.parent.parent.parentID is not blank, give me that name. Otherwise, if parent.parent.parentID is not blank, then give me that name instead. And so on. But you see how aggravating is can be to put together a bunch of if/then statements -- and also they never mentioned how many levels deep it was.