Audit of Field Name References

[CalvinFold]

Assume I have a field named Brand - Brushed . Because of a change in market tactics, the name of the brand changed and now the field needs to be named Brand - Shiny . We don't want to leave the old field name displayed. So if I change the name like this, will it update that name in Text Mode references and calculated fields? Such as {Brand - Brushed} or {DE:Brand - Brushed} references: will those change automatically? I suspect not, in which case: is there a way to generate a report that will unearth every Text Mode or calculated field reference to the old field name so I can fix it to the new field name? Kevin Quosig

[Doug_Den_Hoed__AtAppStore]

Hi Kevin, Actually, although I don't such parameter name changes used to propagate this way, Workfront's made some big improvements in this area: I just did a test and confirmed that when I changed a parameter name, upon saving, Workfront did indeed "do the right thing" as far as the formulas were concerned. I'd suggest you test in your preview environment first, to be safe; and you might also consider: Our "https://store.atappstore.com/product/report-categories-and-parameters/" Report Categories and Parameters solution, which automatically enumerates your Workfront categories and parameters into an Excel spreadsheet that you can use for clean up, maintenance planning, and backup documentation, and/or Our "https://store.atappstore.com/product/populate-category-generator/" Update Category Generator solution, which gives you the current definition of an existing custom form as an Excel file in the proper format (including the formulas) so you can then easily manipulate and upload using our "https://store.atappstore.com/product/populate-category/" Update Category solution. Regards, Doug Den Hoed - AtAppStore Got Skills? Lend a hand! https://community.workfront.com/participate/unanswered-threads

[CalvinFold]

Just responding a bit after-the-fact for anyone else who runs into this: I can't recall the specifics, but Doug was 99% correct that in most cases, the swap of names of fields seems to also swap the names out in the calculations and other back-end stuff. Even the field display logic worked. I want to say the only exception was some issues with drop-down values, but in my case it was minor. Kevin Quosig