Can mapped custom fields still be used in the task title?

We want to be able to sort/filter/report on certain tasks based on responses gathered in the request form (such as building/office location and type-of-request).  When I "map" the request form question to those custom fields, the option to use the response in the title of the created task disappears.  Is there any way around this?  Any creative solutions/suggestions welcome!

2 commentaires
Spot On Innovative Approach Stellar Advice

Hi Erika, I'm wondering if redirecting certain answers (like building office and request type) to an additional, existing, parent Folder might help?

This way when the office/building is selected on the form it will generate an additional item in another Parent Folder in your Folder tree (say you call this Folder Requests for Building A). Now it's easy for you to find all requests that are for that building, while still retaining the original Request in the initial location you selected.

Then when you want to build a Report about one specific building etc., you'll be able to base the Report on this the Requests for Building A folder. 

Take a look at Conditional Parent Folder and let me know if you think this might help 👍

Spot On Innovative Approach Stellar Advice

Hi Stephen, thanks for the follow up.  We are playing around with a sub-folder structure to accommodate some of the groupings but it would be nice to have a little more flexibility with the custom fields!  Looking forward to further updates.


Folllowing List for Post: Can mapped custom fields still be used in the task title?
[this list is visible for admins and agents only]

Haut de la page
Didn’t find what you were looking for? Write new post