Adding a new choice in Hardware asset function field

[janindiadoc_1]

Two new choices need to be added in the asset function field in alm_hardware table. This field (asset function) is from the Asset table (alm_asset) . Please advise the better option to add the choices

1. Add the new choices to the asset function field in the hardware table. By doing this, the OOB choices will not be visible. Is there any impact to this field during the upgrades if we recreate the OOB options for the child table? Will the future changes in the base table get inherited to the child table?

2. Add the new choices to the asset function field in the asset (alm_asset) table, but the options will be visible to all the child tables.

[Peter Bodelier]

Hi @janindiadoc_1,

When creating new fields in child tables, always ask yourself, if the field might ever be used on its parent. If so, create it on the parent to make sure you don't need to create them again on the parent in the future, and up with duplicate fields on the child.

Since these fields will have a u_ prefix, they will never impact upgrades.

[janindiadoc_1]

Hi Peter,

Thank you for the reply. Sorry if I have not phrased it correctly.

I want to add new two choice values to an existing choice field, not a custom field.

[Peter Bodelier · Accepted solution]

Ah, I misunderstood.

Same goes for this actually. Create them in parent, if they are needed in all childs. 
Create them in child if they are only needed there.
Only impact during upgrades could be that you won't see new OOTB choices on parent table within the child.

[janindiadoc_1]

Thank you for the reply. 

Is it okay to move the already available OOB choices from the parent in to the child table as well using "configure form choices". I tried that and its creating new entries for the options in the child table ? Will there be any impact in doing that so?