Custom Field ID to Name in Project Report

Stephen, I use the same calculated field on the issue and the project form, but slightly adjust the calculation. Here's how I handle it. Keep in mind, this will only update on the project during the convert activity.

Thank you Narayan, exactly what I was looking for. Appreciate the help! Stephen Schmidt The Home Depot Creative Services

Hey Stephen and Narayan, This is very helpful, as I have a similar issue I have not been able to find any help with. I would like to pass the name of a creative change/issue requestor through to the WF DAM, however there is not a system field that is mappable that contains the name, only the ID. I have tried to pass this information by mapping the Primary Contact and project Sponsor fields (both of which have the requestor's name), but there are only ID fields for each, no names. I am thinking I will have to create a calculated field on a custom form to capture that information, and it seems like your solution above would work. However, I am very inexperienced at text mode, so I was wondering if you would be able to share a couple more screengrabs of how exactly you have this setup (and what goes in each text mode for both the request/issue custom form and the project custom form). If I can get the name to appear as a custom form field on the project, I can then map it to a corresponding field within DAM. Thank you very much for any help you can offer! Jason Semall Sr Creative Ops Mgr Conversant

Hi Jason, I'm unfamiliar with the DAM and what you are trying to do there. What you've shown me there is new to me. Wish I could better help!

Okay, no problem. Thank you for taking the time to read it! Jason Semall Sr Creative Ops Mgr Conversant

@Jason Semall , I'm assuming that the reason you're pushing this info to the DAM is that there are documents/assets attached with the issue/request. So whoever attached the document to the issue is also the owner of the issue. Wouldn't owner:name be the map to a custom field on the DAM? Polly Co

Thanks Polly! The document(s) that I am passing to DAM from WF are posted to the project that the issue/request is converted to, by a designer. So, if they are the ones pushing their document from the Project to the DAM, I think they would pass through as the "owner" of the document, no? I am trying to find a way to capture and pass through the name of the person who created the issue/request that is then converted to the project that the final documents are then attached and passed to DAM from. That person is always the Primary Contact on the issue/request, but that system field doesn't seem to pass through when converted to a project, and only appears to be an ID when I try to map to DAM. It is also part of our process that when issues/requests are converted to projects, the person who requested it is always made the Project Sponsor. This also only returns an ID option rather than name when trying to map to DAM. I was hoping there was a way to create a calculated field that converts an ID to a name within a project, like Narayan and Stephen were describing for a project report, that I could use to pass to the DAM. Thank you again for your help! Jason Semall Sr Creative Ops Mgr Conversant

I'm confused on the workflow. Are the designers submitting the request? If so, their names are going to be attached to the document and so can be mapped to send to the DAM. But that's not what it seems to be on your last message. So whoever has attached the asset on the request, their names would still show up as the document owners. Converted to a project, the asset is still owned by the person who attached it to the request and that's something mappable to the DAM. Otherwise, and this might not be something that is available to you - we have multiple fields we want mapped from the issue itself that we want to get sent to the DAM. So we made a custom form that can be attached to the document. The custom form itself is automatically attached to the document/asset and copies over all issue data fields to the custom form (done thru coding). All document fields are mapped to the fields on the DAM. When we push the document to the DAM, it carries all the issue/document data. Polly Co

Hey Polly! Thanks again for your input! It is greatly appreciated! Let me step out our process so it is a bit clearer: Marketing Manager submits a request/issue via our queue Each request/issue has a custom form attached that contains the information captured Project Manager receives request and converts the request/issue to a project The request/issue custom form is then transferred to the project Designer is assigned tasks and completes the work. When complete, they post the final deliverables to the project under Documents tab. They then send the asset to the DAM When sending to the DAM, any of those fields from the custom form attached to the project can be passed to DAM attached to that asset I have been able to map all of the fields from the custom form that I need, except for the name of the Marketing Manager who made the initial request/issue - the system fields that would give me that information are both only ID's (Primary Contact ID and Project Sponsor ID), not names. I am trying to avoid having an open text custom field on my form where they have to enter their name, but that may be the only way. I am very interested to learn more about the solution you described. When you say "done thru coding," what exactly do you mean? What was your process for implementing? Jason Semall Sr Creative Ops Mgr Conversant