New field created on HR case table caused a lot of time while committing the updateset in production

[si21]

Hi experts,

Previously we observed latency in committing update set for a new field on HR case form. What is the best practice when we need to create a new field on a table which has more than 70000 record data?

Currently we have requirement to create a field not a form UI (only for list view reporting purpose).

 We are planning to create a new field ( string or reference) but not adding on the form UI. This field would have auto populate parent case number for cloned cases.

Kindly suggest a better way in handling this requirement.

[Ankur Bawiskar · Accepted solution]

@si21 

Try creating field from Configure Form Layout.

I have seen improvement in performance when field is created using that approach although there is no documentation for this.
Also ensure you don't capture the form view in update set. Applying form view also might be taking some time.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar]

@si21 

Hope you are doing good.

Did my reply answer your question?

If my response helped please mark it correct and close the thread so that it benefits future readers.

[si21]

Hi @Ankur Bawiskar , I have created a field on table but not added to the form view. This did not cause any delay in comitting updateset.