Best Practice: Custom Applications (Custom Fields on OOB Tables)

[TFischer]

Hello,

As someone who works mostly within custom scopes, developing (hopefully) reusable apps for clients, I was wondering might be best practice, or best consensus, on adding custom fields to tables practices. 

Hypothetically let's say I was adding a single custom field to the Assessment Metric Definition[asmt_metric_definition] table, which I can't re-purpose from a field already on the table. Other than this one field, I can utilize the existing fields to satisfy my requirements.

I see myself as having two options...

1. Extend asmt_metric_definition and create the custom field

or

2. Create a custom field on the existing asmt_metric_definition table, but the table's Allow New Fields(alter_access) is set to false, so I would have to toggle that value, and capture that update globally before adding the field.

Option #1 may have licensing implications for potential implementations, but option #2 would involve customizing the table[sys_db_object] record.

Is there a specified best practice here? Or another option I'm not considering?

[Priyankagupta]

Hello @TFischer , I don't think you should be extending the asmt_metric_definition table for creation of just one custom field, creating a custom field on the asmt_metric_definition table would be a better option.

But before creating a custom field on the OOTB table do check if you really need a custom field created and also check if there's any other OOTB field which is fulfilling the purpose.

Thanks,

Priyanka