OK long story, but I promise this is kind of related and I can't avoid telling the story because we're still in Classic and as I mentioned, not using Proofs. So I am zero help to anyone using Proofs in NWE.
About your comment about understanding Exists filters -- So my goal for the year is to hammer EXISTS into someone else's head. With that in mind, I'll let you know I'm not good at them either, and I carry the following around with me at all times and amend it as necessary. (I got it from wf-pro.com)
In the project report you are making, show projects that:
- here's my Without line, in case I need one: EXISTS:a:$$EXISTSMOD=NOTEXISTS
- What's the collection I'm grabbing from? Tasks -- EXISTS:a:$$OBJCODE=TASK
- On the Project [this is my equating line] EXISTS:a:projectID=FIELD:ID
- sample mod line goes here, Task named “test” EXISTS:a:name=test
4a. EXISTS:a:name_Mod=eq
(I am good at projects and tasks and that's about it, so this is my cheat sheet that I use to translate with.) With that, I got:
In a docu report, show docu's that:
- Skip line 1, we're looking for stuff that exists.
- I'm looking for proof approvals. Pull up 2 copies of the API Explorer and put them side by side. On one side, pull up the Document section, and on the other side pull up the Proof Approvals section. API explorer says you are looking for PRFAPL, so put that on this line.
- The equating line is the hardest for me. I don't even know why. Look at both lists and look for the ID line that connects the two. To prep for line 4, or just in case you're still stuck on line 3, pull up a document report and a proof approval report side by side. Start plugging in all the ID lines into each view, until you get 2 reports where both columns are showing the same answer. That's it, you found the connection between the two. This is where my crib sheet always comes in handy: it's a mnemonic that "projectID" is something on the task's side, and I never think too hard about it. Put the Proof Approval one on the left and the Document one on the right.
- (and 4a.) What are we looking for? Plug it into your proof approval report -- we're looking for approvals that haven't been completed from a specific user. Once you have that filter, you can copy the text mode into your document exists filter. Append it with exists:A:, and so on. Now, if you run your document report, you should get the exact results of your proof approval report.
Back to your question: all of the sudden your text mode for generating a link directly to the proof doesn't work. Not surprising, since you're in a whole other type of report.
Pointing at the obvious: the "documentVersion" part is from your proof approval report -- and you know this, because it's on the API listing for proof approval and we already know it's not in the document API listing. We also learned that the currentVersionID was a direct equivalent, when we did our exists statement, so at the very least, we need to make that switch.
So I would probably try that first. It begs the question -- is this ALL we need to change? Fingers crossed... I would love to hear if just this one switch works.
