I'm noticing behavior in the Cost Object Permissions table related to Cost Objects that don't exist anymore. 

• When manually adding a row to the table it appears that anything that has ever been a Cost Object is available for selection
• When Importing Cost Object Permissions, you can also specify any of those values

Is there a specific reason that neither of these validates against the current Cost Object list ?   

I don't think this is new, I just think it's something I haven't noticed previously.  We recently revamped our Cost Object approach so there are a lot of superfluous values.

Seems like the drop down when manually adding permissions should only display the current list and it seems that the Import should also validate against the list of Current Cost Objects.

Hi George,

The "List" view of the Cost Object Permissions table shows all permissions used by all plans in the system. This is to ensure users can access historical Cost Objects used in prior plans. To remove the historical codes, you need to delete the plan that's referencing them. 

Thanks,

Ngoc Le

Makes perfect sense.  Thanks Ngoc !