
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2015 06:57 AM
When I create a new table my gut feeling is to always extend it to the task table.
I never know when users will come back and ask for more functionality that requires the extension.
My question is what is the down fall to extend custom tables to the task table? Is this a bad practice to always extend?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2015 07:05 AM
My rule of thumb is this: If I need SLAs, I extend task. Else, I just have it standalone.
I think if you always extend, there will be tables with unnecessary fields and data in it. Your reporting may get confusing, especially when choosing which fields to report on.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2015 07:05 AM
My rule of thumb is this: If I need SLAs, I extend task. Else, I just have it standalone.
I think if you always extend, there will be tables with unnecessary fields and data in it. Your reporting may get confusing, especially when choosing which fields to report on.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2015 07:10 AM
Thank you for the input.
I am leaving it open a bit to see if there is more input.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2015 07:15 AM
Mark,
I base my decision if someone needs to be assigned work to be accomplished. If this is so then it's going to extend off the task table.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2015 07:19 AM
So your saying if you are going to create task from the new table?