On a custom table extending the task table, should new State choice added on custom or global scope?

[Smith Johnson]

Hello,

I am new on the custom app development, and I would like your opinion on the following 🙂

I am working on a custom app created with App Engine Studio. 
I have a table extending the task table, and I would like to modify the choices of the State field.

Does it make sense to add new choices for the State field on my custom app scope or on global scope?
What's the best practice on fields that are inherited from a parent table? 
Could you please provide your reasoning on this?

Thank you in advance,
Smith.

[Dr Atul G- LNG · Accepted solution]

Hi @Smith Johnson 

If the state is not used in any other table and since it’s a custom app, it's better to create the new value only in a new table (meaning a custom table only). If you create it in the parent table, it will be visible everywhere, and every child table will need to make changes. So, it's better to create it within the scope of the custom table.

[Jaspal Singh]

Hi Smith,

Well, if it custom table that you need state choices for then better to add it to custom table's state field instead of task.

It will make sense to add it to task table in case, you want it to be available for other tables as well extending task table.