cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Date time format issue when downloading sharepoint list to csv with power automate

I have a SharePoint list where HR inputs information concerning new hires.  One of the fields is the username and then the other is the hiredate.  HR enters the name and date, but when I use power automate to extract the data to a CSV,  the format of the date changes to something like 2022-07-31T00:33:00Z  (this was 8:33pm ET in the SharePoint list).

 

I thought maybe I could convert the time, but that didn't work.  How can I retain the original format for the date and time?

 

LOWED3498_0-1658796432196.png

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Ok. This is the answer to your issue. You need to initialize an array variable to store each list item. Then we will use the "convert time zone" action. The issue is, the date value in the SharePoint list is in UTC. So you need to convert it from UTC to whatever time zone you want. My is in EST.  The CSV at the end is outside of the For Each. 

PoohBear_4-1659402720405.png

PoohBear_5-1659402739899.png

PoohBear_6-1659402804898.png

 

 

 

View solution in original post

15 REPLIES 15

You can try using formatDateTime(<DateTimeFieldInSharepoint>,'dd/MM/yyyy'). 

Pstork1
Most Valuable Professional
Most Valuable Professional

That formatting is ISO 8601 for the UTC timezone.  The date is actually stored as UTC in the SharePoint list.  SharePoint converts it to the local timezone when you access the list, but Power Automate doesn't do the conversion.  So to get it to look exactly the same you need to subtract the number of hours that you are off from UTC and then wrap that in a formatdatetime() to generate the format you want in the CSV

formatdatetime(addHours(<<SharePointDateTime>>),-4),'MM/dd/yy hh:mm:ss')


-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Thank you @Pstork1   So I would scrape the "convert time zone" and do an "apply to each" action with the expression you provided?

 

 

Pstork1
Most Valuable Professional
Most Valuable Professional

Not necessarily.  The convert time action you are using would be fine.  But you are doing it on the created time, not the hire date.  My code does essentially the same thing as a formula.  You can do it using the convert time action too.  But you need to supply the right field as the base date.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Create a new Calculated field in the SP List and convert the date to text.. 

Pstork1
Most Valuable Professional
Most Valuable Professional

That will probably work, but its not needed.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

I decided to focus on this same process but for tracking when to "disable" a user account that HR submits via SharePoint.    I have been trying to get this to work, and I am missing something.    After "Get Items", I did an "Apply to Each" to convert the time from UTC to Eastern and the output looked good, except I needed to convert the time to Eastern.   So  I  add another operation "Subtract from time" to subtract 4 hours.  That worked but the output reverts back to UTC.  So I pulled that operation out, just to see if the "Convert to time" output, which was ET, would show up correct in the CSV file.  And it didn't.    I am new to power automate so I am trying to figure this out and read a bunch of threads and watch videos.   I think this is tricky because I am using a future time (the future date HR wants the account disabled) and then subtracting from that to get the Eastern time conversion.   I suspect I am also missing something to pass the converted date to the CSV as well?

 

LOWED3498_0-1658944653920.png

 

LOWED3498_1-1658944870902.png

 

I have a very similar process for contracts so I am going to describe how I tackle the issue. In my opinion, SharePoint calculated columns can solve your issue and make your flow much easier. In my process, someone uploads a pdf file and enters a Start Date and End Date which are date fields. I create 3 calculated columns for email notification dates (90,60,30 days) from the end date. The formula in the 90DayDate column is in the screenshot below. I also have a column "Processed" and set the default value to "Pending". My flow has a recurring trigger to run daily at a specified time. The next action is to get the Current Time. The "Today" compose action converts that to a string so I can use that in a condition. The "GetPOs" is a Get Items action and I am filtering to find only the "Pending" items. You could filter by a date as well. Next, I have a condition where I want to find the contracts that are expiring in 90 days. The first condition is a "length" condition to make sure the "Get Items" has a value. The second condition is compares the "90DayDate" in the SharePoint list to the "Today" compose action. My SharePoint list settings are set to Eastern Standard Time. Since the "90,60,30" columns are text, it will extract into the CSV as is and will not convert back to UTC. The next action in the condition would be to update the "Processed" field in SharePoint of any item that matches the condition to "Processed". After that you can send an email or whatever else you want to do. Dates can be tricky, but I found using this method works great in a lot of scenarios. 

 

PoohBear_0-1659017259192.png

PoohBear_1-1659017357859.png

PoohBear_2-1659018082030.png

 

PoohBear_3-1659018082036.png

 

 

 

 

 

Thank you @PoohBear   What you posted is actually another item I have on my list of things to automate.  Too many contracts, different dates, renewals....keeping track of all of those.  Perfect!

I am still struggling with getting the time to change to ET.  The issue (maybe?) is that this is not the create or modify date for the record in the SharePoint list.  It's a field that the HR person is entering to schedule disabling an AD account.  I've tried converting, adding hours, subtracting hours....it always ends up UTC  08/09/2022 10:28  (the time should have been 6:28PM ET

 

 

LOWED3498_0-1659395613581.png

 

Ok. This is the answer to your issue. You need to initialize an array variable to store each list item. Then we will use the "convert time zone" action. The issue is, the date value in the SharePoint list is in UTC. So you need to convert it from UTC to whatever time zone you want. My is in EST.  The CSV at the end is outside of the For Each. 

PoohBear_4-1659402720405.png

PoohBear_5-1659402739899.png

PoohBear_6-1659402804898.png

 

 

 

PoohBear_7-1659403009047.png

 

Here is an alternative method using a SP Calculated Field with the same result and less steps in Power Automate. 

PoohBear_8-1659403950683.png

This is a calculated field set as text. 

PoohBear_9-1659404021409.png

PoohBear_10-1659404057329.png

PoohBear_11-1659404115114.png

 

 

 

Thank you for this information.  I am going work on this today and get one of these to work!

@PoohBear  Thank you.  It works perfectly now.

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22  

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (4,811)