Add effective date capabilities to custom fields in User Profiles

  • 4
  • Idea
  • Updated 2 years ago
  • Not Planned
I would like to see effective date functionality in custom fields for user profiles, much like Supervisor, Billing, and Cost fields.  We record information in some custom fields that change as user's salary structure changes, which would be much more effective if we could determine change dates.
Photo of Rachel Slaughter

Rachel Slaughter

  • 21 Posts
  • 3 Reply Likes

Posted 3 years ago

  • 4
Photo of Lingaraj Dharwad

Lingaraj Dharwad, Product Champion

  • 1100 Posts
  • 46 Reply Likes
Hi Rachel,

Thank you for using Replicon community,

We are reviewing your idea.

Thanks,
Lingaraj
Photo of Karen Chao

Karen Chao, Product Manager

  • 117 Posts
  • 16 Reply Likes
Hi Rachel, Would you please elaborate with a few examples of information you are storing in the custom fields that you would like to assign effective dates to? I want to make sure I understand the business need fully. Thanks, Karen
Photo of Rachel Slaughter

Rachel Slaughter

  • 21 Posts
  • 3 Reply Likes
Hi Karen, a few examples are as follows:
- Some employees receive an hourly bonus based on the type of work they're doing.  This number changes following raises and promotions.  Without the effective date functionality, reports aren't very accurate when calculating total hourly bonus for a given time period.
- We have three offices worldwide and sometimes we "rent out" employees to another office.  This incurs an internal cost that changes based on the employee's tenure and expertise.  Without the effective date functionality, it's hard to tell when I've last updated this cost amount.
Photo of Karen Chao

Karen Chao, Product Manager

  • 117 Posts
  • 16 Reply Likes
Hi Rachel, I want to get input from other members of the Product team for this. Thanks, Karen
(Edited)
Photo of Jo Hart

Jo Hart

  • 1 Post
  • 0 Reply Likes
I too have a request for an "effective date" field to be available in customised fields.  We are using scheduled rates, and these are likely to change annually within the project.  This would be a really useful addition for our project. I logged a call, and referenced this comment, and was requested to add a post. Thanks
Photo of Sangeet Saurabh

Sangeet Saurabh

  • 53 Posts
  • 10 Reply Likes
Hi Joe,

Billing rates on Project do have effective date. Does that not work for you?

Thanks,
Sangeet
Photo of Olaf

Olaf

  • 4 Posts
  • 1 Reply Like
Hi All,
I would like to see this feature as well.

Our example:
We are using a field for the Department Code of an employee. Once the department is changed, all hours retroactively are counted for the new department.
With an effective date capability such as for the cost rate, this problem could be solved.
If there is any other solution for this already in place, please let me know.

Best regards

Olaf
Photo of Tsakis, Deon

Tsakis, Deon

  • 21 Posts
  • 0 Reply Likes
This is an old post, however i agree with everyone above.

Date Ranges on custom fields would allow long-term reporting to be more accurate.
We use Cost Centers, Roles and Location fields all of which are liable to change over time.
Without date ranges, we end up losing historic data when attempting to run reports over a number of months
Photo of Leeks, Jon

Leeks, Jon

  • 3 Posts
  • 0 Reply Likes
I agree with Deon,

We would like to track simple attributes about the clients in our system that change over time (e.g. a prospect becoming a client)

There are other items in the user table that change over time that we would like to track as well (e.g. provisions of hours for a specific employee type over time)

The location and division fields in the payroll package solve some but not all of these issues.
Photo of Tsakis, Deon

Tsakis, Deon

  • 21 Posts
  • 0 Reply Likes
Hi All,

Thought id post here again, as it seems like a critical feature for quite a few customers.

As i have stated above, from a reporting/tracking/planning perspective it is strange that historic information is lost over time. 

If at all possible, it would be helpful to know if additional date functionality is being planned for implementation at all in the future