how was it resolved? in case others have this issue? i found the following so sharing as well.
Recommended solution
Replace the Workfront Search — Journal Entry module with:
Adobe Workfront → Custom API Call
Configure it as follows:
| Field | Value |
|---|
| Method | GET |
| URL | JRNLE/search |
| API version | Use the version selected by your Fusion connection |
fields | ID,entryDate,editedByID,objObjCode,objID,projectID,topObjID,fieldName,changeType |
objObjCode | PROJ |
objID | Map the project ID |
editedByID | Map the project ownerID |
entryDate_Sort | desc |
$$LIMIT | 1 |
The Workfront API supports sorting search results by appending a field sort parameter such as entryDate_Sort; use desc for newest first. The $$LIMIT=1 parameter ensures that only the first record after sorting is returned. Sorting query results in the API API basics
Query-string version
If your Fusion module allows you to enter one complete query string, use:
fields=ID,entryDate,editedByID,objObjCode,objID,projectID,topObjID,fieldName,changeType
&objObjCode=PROJ
&objID={{Project.ID}}
&editedByID={{Project.ownerID}}
&entryDate_Sort=desc
&$$LIMIT=1
If Fusion displays Query String as individual rows, create one row for each key/value pair instead of including the ampersands.
Important field mapping
entryDate is the date and time of the journal entry. editedByID is the user who made the change. ownerID is the project owner. Map the project's ownerID into the Journal Entry filter editedByID. objObjCode=PROJ and objID=<project ID> restrict the search to changes made directly to the project.
Workfront's Journal Entry reporting guidance uses Entry Date for the date of the change and recommends sorting it in descending order. It also distinguishes the affected field, the project, and the user who edited the record. Report on the Updates Area with a Journal Entry Report
If you mean project-owner changes specifically
If the requirement is to find the last time the Project Owner field itself was changed, add this filter:
fieldName=ownerID
In that case, do not filter editedByID to the current project owner unless you specifically want changes made by that person. The owner may have been changed by an administrator or another user.
The query becomes:
fields=ID,entryDate,editedByID,objObjCode,objID,fieldName,oldTextVal,newTextVal
&objObjCode=PROJ
&objID={{Project.ID}}
&fieldName=ownerID
&entryDate_Sort=desc
&$$LIMIT=1
If you want activity from tasks and issues inside the project
Remove:
objObjCode=PROJ
objID={{Project.ID}}
and use the project-context filter instead:
projectID={{Project.ID}}
This can include Journal Entries associated with child tasks or issues. Keep editedByID={{Project.ownerID}} if you still want only entries made by the project owner.
One important distinction
A Journal Entry represents tracked system or field changes. A user-written comment or status-update message is generally a Note, not a Journal Entry. If “update” means a free-form comment in the Updates area, query Notes or use the project’s native Status Update-related data instead. Searching through system logs - UPDATE vs. NOTE vs. JRNLE objects
Checklist
- Sort
entryDate newest first with entryDate_Sort=desc. - Limit the response to one record with
$$LIMIT=1. - Filter by the project owner using
editedByID={{Project.ownerID}}. - Restrict to direct project changes with
objObjCode=PROJ and objID={{Project.ID}}. - Clarify the difference between Journal Entries and user comments.