User Created date far into the future

[AshleyKerchhoff]

Hi All

I am currently doing the SN fundamentals course. In the lab instance, we created the two users Bob and Jane. I then went back to the list of users to find the users that were just created. While doing this I found some users with a Created date that is in the year 2031 (screenshot attached). I double checked the New User form and there is no way I can add a Created date which makes sense because as I understand that is added by a system process.

As such, I am assuming that the only way this could be done is by manually changing the date directly in the DB (if this is possible). But from a Production perspective, why would this be done? What use does this serve? Why would the system allow this?

Can anyone shed some light on this or should I not worry since it's just a lab instance?

Tx

[Mark Manders]

Probably a mistake while provisioning the lab instance. I wouldn't look into that, because you can't set any of this yourself, without going around the system. These users were probably created via script, imported on a wrong date setting and never updated.

[Sanjay191]

Hi  @AshleyKerchhoff 
The Created field (sys_created_on) is a system-maintained (you can say system default field https://www.servicenow.com/docs/r/platform-administration/table-administration-and-data-management/r... ) field in ServiceNow, so it normally cannot be entered manually from the standard New User form.

Seeing a future date such as 2031 in a lab instance does not necessarily mean that someone manually modified the database. There can be several reasons for this, such as:

• Data being loaded through an import/transform process.
• Data being inserted through scripts or integrations where system fields are explicitly handled.
• The lab/demo instance containing test or sample data with modified system dates.
• In some cases, the instance or data may have been manipulated specifically for training/lab purposes.
  
  In a Production instance, there generally isn't a business reason to manually change sys_created_on directly in the database. ServiceNow does not provide customers with direct database access, and modifying system fields directly would also be unsupported and could lead to data integrity or auditing issues and lab instance data its just for training demo data actually.
  
  

  If you found my response helpful and it answered your question, please consider marking it as the accepted solution and giving it a thumbs up. It helps others in the community find the solution more easily.

  Thank you!

[Ankur Bawiskar]

@AshleyKerchhoff 

I agree with what @Mark Manders mentioned.

I have seen something similar in past in lab instances.

So better to ignore that.

This is not going to happen in any customer instance i.e. created date on sys_user in Future.