Hi,I just did and it worked perfectly well again. Did you compare your csv files concerning encoding, end of line sequence and delimiter as there can be multiple combinations? Perhaps there are differences between the tested files and the parse csv module does not allow all kinds...  RegardsLars

Ok, sounds promising. I think I need to go through it another time, as this approach was not working for me earlier. But perhaps I made a mistake... I will check and post an update.

@Madalyn_Destafney and @skyehansen Thanks a lot for your answers. I really hope this will be possible in the near future, as it would be an absolute benefit.

Can you also post a screenshot of the output of the parse csv module?   I just created a short similar test scenario and it is working fine. Perhaps you can try to remove the module Set variable and add it again...  RegardsLars

Hello, troubleshooting with this screenshot is not possible. More important would be to see how the parse CSV module is configured and what its output is. To understand the scenario: the downloaded document is always a csv-file, right?  RegardsLars

Hello,I know, that there are several threads and ideas concerning the ability to have filters, views, and groupings on a per-object basis, but I wanted to ask, if there are any workarounds.We absolutely need to be able to "customize" how a project and the tasks are shown groupwise. As it is possible...

Hi, I think you have a typo in your call. You need to pass the query string using a question mark instead of the slash before fields: https://<MyDomain>.my.workfront.com/attask/api/v15.0/user/5edb22c5022aac5751a37c4d0acfc53f?fields=parameterValues   RegardsLars

Ok, if it is working on another form I am quite sure, that this new form does not have access to the required "field path". Could you please double check, which object types are associated to the form? In this case I would suggest, that it needs the object type portfolio to get this field value.  Re...

I would cut and paste it into a text editor, copy from there and paste it back into the calculation expression to eliminate any hidden characters.

Hello RPGMF, this expression is correct, if you try it in a calculated field in a custom form.In textmode it also works asvalueexpression=IF({portfolio}.{name}="CNS CE - Customer Engagement", "CE") Where did you try to use it and do you get any error message / response? RegardsLars