web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Autonumber Date Time n...
Power Apps
Unanswered

Autonumber Date Time non-utc

(0) ShareShare
ReportReport
Posted on by 98

Hey there,

 

Is there any way to use the local time (or just adjust the utc time) in the autonumber formatting?  We have data that's being entered at 6pm local time and is showing up as the next day.  This is our unique identifier.  It'll cause issues if we have that same amount of data entered the next day.

 

JMerk_0-1691008474395.png

 

I have the same question (0)
  • Parvez Ghumra Profile Picture
    1,579 Moderator on at

    @JMerk According to the documentation, the date portion of the autonumber assigned is always in UTC: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/autonumber-fields#date-prefixed-number

     

    I think this kind of makes sense because that's how DateTime column values are stored at the database level, and applying localisation to the date portion of the autonumber when it is displayed would mean that a different value would be shown users depending on which timezone they're based in.

     

    Considering the autonumber is meant to be a table level unique identifier for each record, you should probably avoid customising this to apply localisation at display time.

  • JMerk Profile Picture
    98 on at

    @parvezghumra Is there any way to add an offset to the UTC time?  I'm in UTC-7.  The way I have my database set up, with power automate, it resets everyday at 00:00 UTC-7.  Or midnight MST. Whichever you prefer.  We have data being input anytime between 6AM MST and 7PM MST on the same day.  The autonumber would be unique, but due to the UTC giving me problems, I'm getting two columns labelled 230802-0041.  The way my identifier works is YYMMDD-#### autoinc number.  There's no way on the same day to get two 41's, it would reset.  But with this UTC thing, it's giving me a massive headache.

     

    I'm fine with keeping the date constant.  If someone else is in a different timezone and using this data (currently no one is), they can convert.  The vast majority of our operations occur locally so there's not a lot of reason to convert it.  For the sake of consistent data here, I need a way to add a UTC offset.

  • JMerk Profile Picture
    98 on at

    JMerk_0-1691074678579.png

    As you can see here, the data entered after 6 on 8/1, are showing up in the auto incrementing column as 8/2.  

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
Valantis Profile Picture

Valantis 414

#2
WarrenBelz Profile Picture

WarrenBelz 377 Most Valuable Professional

#3
Kalathiya Profile Picture

Kalathiya 315 Super User 2026 Season 1

Last 30 days Overall leaderboard