Enable assignement of taxonomy metadata fields using variables in Add Metadata Outcome
Currently, a taxonomy field in the metadata template used by a form can be completed (that is, the person completing the form can select a value from the taxonomy), but in an Automate workflow the value that is selected cannot be applied to a file using the Add Metadata outcome, because that field type does not allow value assignment via a variable.
The only way to make this work is to use a Dropdown field in the metadata template. Those do allow the use of variables to assign values in the Add Metadata step. BUT, that creates a maintenance nightmare for the following reasons:
1) If the same values are needed in multiple metadata templates, they have to be added to each one separately, as individual Drop Down fields. We have a taxonomy that has 40 items in it, and since we can't use that as a field in the template, it means that we have to hand-enter the same 40 items in a new Drop Down field every time we want to expose those values in a form, and
2) When the value(s) in that "taxonomy" change, each and every metadata template that has a field that exposes those values has to be edited. And there's no easy way to identify which metadata templates use the field, so the only way to make sure that you don't have a regression is to check every single one.
Obviously, both of those are huge issues at scale. How this wasn't implemented properly from the beginning is completely beyond me. It should be a high priority fix.
CAND Webmaster
shared this idea