# Best Practices 1: Standard Object Fields

**URL:** <https://forums.knack.com/t/best-practices-1-standard-object-fields/7725>\
**Category:** No-Code Solutions\
**Created:** [February 11, 2016, 9:59pm UTC](https://forums.knack.com/t/best-practices-1-standard-object-fields/7725 "2016-02-11T21:59:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![OmarTing72560](https://avatars.discourse-cdn.com/v4/letter/o/f07891/32.png) [@OmarTing72560](https://forums.knack.com/u/OmarTing72560)\
**Post date:** [February 11, 2016, 9:59pm UTC](https://forums.knack.com/t/best-practices-1-standard-object-fields/7725/1 "2016-02-11T21:59:57Z")

</div>

Thought to give back to some Knack/database newbies, share some of the things I've learned.

I see myself having a need for the following fields for most objects:

1) Date Created

2) Date Updated

3) Created by (user)

4) Updated by (user)

5) ID # (auto increment field)

^I find it is always better to include these fields when you first create an object, and delete them at a later date if there is no need for them, rather then to build it in after the fact.

I also think that building those core fields into each object will make your life easier going forward.

Maybe these things are covered in "Database 101" ... ???

**_\*It is also a good idea to foresee all the possible User Types and create them at the very beginning also..._**

---

<div class="post-metadata">

**Author:** ![MichaelMcC83608](https://avatars.discourse-cdn.com/v4/letter/m/db5fbb/32.png) [@MichaelMcC83608](https://forums.knack.com/u/MichaelMcC83608)\
**Post date:** [December 3, 2016, 5:18am UTC](https://forums.knack.com/t/best-practices-1-standard-object-fields/7725/2 "2016-12-03T05:18:14Z")

</div>

To add to this, you need to setup each form so that it records and updates the above fields.