@Jason Semall , the single quotes should keep the input together so spaces between quotes should be fine. I think the special characters should be fine unless it's a quote character. IF(CONTAINS('dam1',test3),'dam1','') should be IF(CONTAINS('word space & word',your checkbox field),'word space & wor...

@Jason Semall , the pattern would be IF(CONTAINS('damx',test3),'damx','') So CONCAT(Pattern1,Pattern2,Pattern3,Pattern4,Pattern5) where pattern is IF(CONTAINS('checkbox option',checkboxfield),'checkbox option','') CONCAT( IF(CONTAINS('dam1',test3),'dam1','') , IF(CONTAINS('dam2',test3),'dam2','') , ...

@Yannick Seifert , I haven't seen it done and I took a look at my calculated fields, I don't think it's possible but maybe somebody else in the forum can answer. Logically, the reason why I think it's not possible in the custom form is that usually the project custom form is set up upon project crea...

@Jason Semall , I haven't used checkboxes to map to the DAM but I've tested and saw what you meant by just one checkbox item is being sent forward. So... the best option I could think of is adding another calculated field for each checkbox field. For example, you have test3 as a checkbox field with ...

https://support.workfront.com/hc/en-us/articles/115000165713-API-Version-Release-and-Deprecation-Schedule According to the page above: NOTE All Workfront URI calls must specify a version of the API. Integrations that do not specify a version in the URI are automatically routed to the Default Version...

@Jason Semall , I see what you mean now. I think the best solution I can suggest is to put a calculated field on your issue/request and project form. On the issue form, put in the calculated field Label: Original Requester Calculation: Entered By.Name On the project form, put in the calculated field...

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 st...

@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

It would be great if WFDAM can let us have clickable links within the metadata fields so that users can just click a link to go to the url. Use case would be that the specific image can be linked back to the WF project it's associated with.

I guess the API explorer would be the best source of objects in WF - but it does not include definitions - maybe this is something WF can just tack on to the API explorer. If you know the basics of API, you'll be able to generally get the fields available and when I see what's the data in the fields...