Custom Form Fields

[markTwo]

Hi, I have a tickbox field which has over 50 options, this field is used to create the job name by Fusion. Is it possible to use this field on several custom forms but alter the answers available to choose from dependant on the form it's used. E.G. Form one has all choices, Form two only has choices for print because it''s a print job form. 

TIA

[MorganHatcher]

Hi @markTwo - unfortunately, it is not possible to update the field from form to form - any changes you make will reflect everywhere the field is used. If you wanted to only have two choices visible on Form two, you would need to create a new field. 

[skyehansen]

I'm currently working on something similar at work -- one field that would indicate a changing list of choices based on whatever the primary custom form is (the custom form at the top of the list if you have more than one custom form).

The way it would work for me, would be to make it an external lookup field. So you would have to create another new field, and retire your tickbox field. Kat has some examples of external lookup fields here:

https://experienceleaguecommunities.adobe.com/t5/workfront-discussions/how-to-replace-typeahead-with...

There are many ways to set this up and I am sure someone else will come up with something more cunning than this. However, what I would suggest as a beginner, would be a workfront project with parent tasks that are named after your custom form IDs, and child tasks named for the selections you would like for each. So Form 2, the print form -- the parent task would be named 63782432fk3489 and the children under this would be your 2 options. Form 1, the parent task would be named 908234678sjkdhs873, and the children under this would be 50 options (ouch). And so on.

If you haven't been scared off yet, you would then set up a calculated field. Again, someone might suggest something different here! Your calculated field would just be {categoryID} -- so I need a calculated field to indicate to my external lookup field what the category ID is, because I didn't have time to figure out how else to do this, for my demo.

Now, your external lookup field. Bare minimum, the API call would be something along the lines of:

$$HOST/attask/api/v17.0/task/search?projectID=ABC123&parent:name={DE:DEF456}

where ABC123 is the guid of your project, and DEF456 is the name of your calculated field. You can add other options! I normally put something in for task status = new, because then I can retire the old options (keep them off the list) but keep them around (not delete) for historical. 

I know this is a lot to build out! And possibly someone can skinny this down for you. But this at least works in the meantime as a proof of concept, so you can build out a couple of the parent tasks and then see if you like it enough to keep going.

[kautuk_sahni]

@markTwo just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!