# Seasonal Employees Start/End dates list

**URL:** <https://www.epiusers.help/t/seasonal-employees-start-end-dates-list/108951>\
**Category:** Kinetic ERP\
**Tags:** ud, employee, list, epicor\
**Created:** [November 8, 2023, 8:39pm UTC](https://www.epiusers.help/t/seasonal-employees-start-end-dates-list/108951 "2023-11-08T20:39:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![masuphiber](https://www.epiusers.help/letter_avatar_proxy/v4/letter/m/e0b2c6/32.png) [@masuphiber](https://www.epiusers.help/u/masuphiber)\
**Post date:** [November 8, 2023, 8:39pm UTC](https://www.epiusers.help/t/seasonal-employees-start-end-dates-list/108951/1 "2023-11-08T20:39:14Z")

</div>

Hello everyone,

We have a some seasonal employees who work winters and quit summers at our company.  
This means that they stop working here in spring time and start working here in the fall. They do this for several years.  
So far, we’ve been adding new UD fields to keep track of when an employee starts and when they stop working. Right now we have five EmpBasic\_UD\_Start\_Date#\_c and five EmpBasic\_UD\_End\_Date#\_c fields, but someone is about to start their 6th year.  
For example, this is how part of the Employee Maintenance screen looks right now:  
 ![image](https://www.epiusers.help/uploads/default/original/3X/b/5/b5f2ca73477f2a2d36d37bdcd8ba7a468526c2bc.png)

Adding N amount of UD fields is not ideal and we need a better solution.

I was thinking about the following options:

- We can use a UD table like UD03. I can add EmpID\_c, WorkStart\_c, and WorkEnd\_c UD columns and dedicate the entire table to these dates. It seems like a waste of a table to store a list however.
- I can create a really big nvarchar(10000) UD field for EmpBasic\_UD and comma-separate the date ranges.

Does anyone have any other easy suggestions to store UD lists for Employees?

We’d like to keep track of these things and store them inside Epicor because we use the total length of employment for anniversary gifts and stuff.

Thank you for your time.

---

<div class="post-metadata">

**Author:** ![jgiese.wci](https://www.epiusers.help/user_avatar/www.epiusers.help/jgiese.wci/32/51553_2.png) [@jgiese.wci](https://www.epiusers.help/u/jgiese.wci)\
**Post date:** [November 8, 2023, 8:41pm UTC](https://www.epiusers.help/t/seasonal-employees-start-end-dates-list/108951/2 "2023-11-08T20:41:50Z")

</div>

> [@masuphiber](#):
>
> We can use a UD table like UD03. I can add EmpID\_c, WorkStart\_c, and WorkEnd\_c UD columns and dedicate the entire table to these dates. It seems like a waste of a table to store a list however.

Unless you’re really close to running out of tables just use a UD table this is a perfect use for them. You could do the comma one but you might hate yourself later when they ask you for a report on these employees LOL.

---

<div class="post-metadata">

**Author:** ![masuphiber](https://www.epiusers.help/letter_avatar_proxy/v4/letter/m/e0b2c6/32.png) [@masuphiber](https://www.epiusers.help/u/masuphiber)\
**Post date:** [November 8, 2023, 8:45pm UTC](https://www.epiusers.help/t/seasonal-employees-start-end-dates-list/108951/3 "2023-11-08T20:45:23Z")

</div>

> Unless you’re really close to running out of tables just use a UD table this is a perfect use for them.

I feel like the UD table is the best solution so far. We are only using 1 or 2 of them as far as I know, so definitely not running out…  
Thanks for your feedback.

> You could do the comma one but you might hate yourself later when they ask you for a report on these employees LOL.

You’re right, that is the reason why I am hesitant to store them in a comma separated string 😆

---

<div class="post-metadata">

**Author:** ![jgiese.wci](https://www.epiusers.help/user_avatar/www.epiusers.help/jgiese.wci/32/51553_2.png) [@jgiese.wci](https://www.epiusers.help/u/jgiese.wci)\
**Post date:** [November 8, 2023, 8:49pm UTC](https://www.epiusers.help/t/seasonal-employees-start-end-dates-list/108951/4 "2023-11-08T20:49:05Z")

</div>

> [@masuphiber](#):
>
> I feel like the UD table is the best solution so far. We are only using 1 or 2 of them as far

As a kid (and an adult) I used to horde coloring markers this way too, especially my good ones. Have to let go and use those markers that’s what they are there for; to be used LOL
