1. Make it non-changeable in the UI, requiring changes be made directly in the database. This is a trivial IDL change.
2. Add an API or stored procedure to support changing the value, which would also update any rows linked to the pkey from other tables (e.g. acq.invoice_item).
3. As suggested, add an ID surrogate key to the invoice_item_type table. This would resolve the update-ability but adds other complications at the SQL level. (We've been talking about dropping the ID from permission.perm_list table for a long time, because it complicates SQL upgrades).
Thanks for confirming, Tiffany.
Options that come to mind:
1. Make it non-changeable in the UI, requiring changes be made directly in the database. This is a trivial IDL change.
2. Add an API or stored procedure to support changing the value, which would also update any rows linked to the pkey from other tables (e.g. acq.invoice_item).
3. As suggested, add an ID surrogate key to the invoice_item_type table. This would resolve the update-ability but adds other complications at the SQL level. (We've been talking about dropping the ID from permission. perm_list table for a long time, because it complicates SQL upgrades).