Hi Amy This is a real bugbear of mine! The unspoken assumption you are making is that there is a "field label" on forms and a separate field name in the backend database , or "API name" as you refer to it. That is a reasonable assumption to most people who have worked with databases previously and as David has said Workfront does provide that functionality in reports/views, so you can rename a column on a report with a name that is only relevant in the context of that report. However, in Workfront t here isn't that distinction/functionality at present between the "field label" on forms and the field name in the backend database , which is why the API name changes every time you change the "label" on a data field (even though I'm told that Workfront is actually an Oracle DB under the hood so the underlying functionality is already there) . I hadn't considered your integration use case before, and the impact of this issue on it . See also the recent discussion on this thread - "https://community.workfront.com/discussions/community-home/digestviewer/viewthread?MessageKey=4e0ddaf9-1d48-4d42-a53e-75b6b1951186&CommunityKey=aaafaff0-5e4e-4e38-8903-f1f990935567&tab=digestviewer#bm4e0ddaf9-1d48-4d42-a53e-75b6b1951186" Virtual Instance ID - VIID concept from LEAP 2019 - although the discussion of this issue is not the main topic of that thread. It's great in one way to see how ingenious and innovative this community is at finding ways to achieve a result by working around the limitations in the Workfront tool, but how much better it would be long term if the limitations were removed. We probably should put together an enhancement request so people can vote for it, but I've struggled to work out how to phrase it so it means something to others looking for solutions to the same underlying issue Hope this helps Regards Bob Sleigh BT Group