Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Hey Jill, Not quite. This guide will go over a bit more on how to use collections: https://support.workfront.com/hc/en-us/articles/115000586214-Referencing-Collections-in-a-Report
The API explorer is used to understand what fields are available, what objects you can reference from that object, and what 1:n objects you can reference. 1:n = 1 to many relationship in a database. -- We use Oracle as our DB. So quick example: Look at Project in the API explorer. On the Fields tab, you'll see that you can reference ID, Name, etc. On the References tab, you'll see that you can reference Category, Approval Process, Scorecard, Group, Owner, etc. On the Collections tab, you'll see that you can reference Baselines, Documents, Expenses, hours, Tasks, Updates, etc. So, if I were to create a project report, I can see that I can reference the name in a column based on the Fields tab, the Approval Process based on the References tab, and a list of all the tasks, based on the Collections tab. Now, you might find out that sometimes something won't be listed, but it's still possible to reference. Such as a list of issues on a project report, in a collection column. Here's what it looks like for the text mode for the column:
displayname=Issues
listdelimiter= < p >
listmethod=nested(issues).lists
textmode=true
type=iterate
valuefield=name
valueformat=HTML</pre>
And when you run the report, you can see a list of issues (see the image.png I uploaded.) I hope this helps steer you in the right direction! Thanks, Dustin Martin Assigned Support Engineer Workfront
Views
Replies
Total Likes