Automated issue import displaying true requester

[FrankatMSC]

I wrote a nifty scenario, sorry I'm fairly new to Fusion and this one I'm very proud of lol, that monitors a OneDrive folder for new files and then imports the issues listed in the CSV file.   The problem is I can't make the issue show the actual requested by as any one but Fusion.  The only field I seem to be able to change is the submitted by.  Even though I update the Entered By date with a column from the CSV displaying who I want to be the requester, it changes it to Fusion every time.  Has anyone found a way around this?  We need the requester to show as the actual person in the overview section.  Thanks in advance for any ideas.

[IvanBebek-iX]

Hi @FrankatMSC,

Some of the fields are system fields and will be updated by the system for example in your case you are probably getting user (that you use as a connection defined in Workfront Fusion) as the user who did the action was this user this will savelastUpdatedByID field as this user and it will also affect the modification date, as thats automatically added once the request finishes.

As I do not know the specifics to your use case I would advice that you use a custom form and add a custom form field on the issue where you will store the user which you can later on use in the scenario.

Hopefully this helps.

Best regards,
Ivan

[FrankatMSC]

Hi Ivan,  Thanks for you reply.  I had thought of using a custom field but then all the built in reporting, Home page widget, Request submitted page etc, won't report as designed.  This what all the users have come to use.  I'd have to write all new custom reporting.  Not that that is a problem.  Adobe need to update coding so that we can submit request and other objects through Fusion and have them show as who we chose.

[kautuk_sahni]

@FrankatMSC Just checking in. Were you able to resolve your issue? We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could benefit the community. Thanks again for being part of the conversation!