cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Formatting Date List Items from SharePoint when sending an E-mail notification

As part of an otherwise working and pretty straightforward FLOW, I'm sending an e-mail message that pulls in a date field from SharePoint into the body of the e-mail, but the format is pretty ugly...and I can't figure an obvious way to change the formatting. 

 

Assuming 12/31/1999 is the value I have for an item, it looks like the following in the e-mail: 1999-12-31T21:00:00Z 

 

Even restricting the SharePoint list item to be a short date does nothing to influence the formatting of the e-mails getting sent by FLOW. Is there a simple way to change this that I'm missing? In Workflow Designer 20XX this could be adjusted in seconds.

 

(Edit for clarity)

1 ACCEPTED SOLUTION

Accepted Solutions

Not sure if you got this to work yet, but I found a solution here:  here  - recreated below.

 

1. Add a Compose Action after the trigger/Action, then specify the Compose input with the following format:

"@formatdatetime( ,'yyyy-MM-ddThh:mm:ss')"

2. Click at the first parameter part of the formatdatetime, then choose the corresponding dynamic content, save it,

3. Microsoft Flow won't save successfully, and would notify the error message of validation failed,which then we may find the corresponding part for the input,

4. Copy and paste the corresponding data within the braces @{ } into the function first parameter, then save the flow

Adding screenshots as reference:

68.PNG

69.PNG

70.PNG

 

 

 

View solution in original post

19 REPLIES 19
v-micsh-msft
Community Support
Community Support

Hi @Anonymous,

 

Yes, that could be done.

We could take use of Compose Action, together with the formatdatetime function to format the date format.

Assume the date field from SharePoint is Named with Date, then we could follow the flow below to format the date:

The formula used under Compose Action input is the following:

"@formatdatetime(triggerBody()?['Date'],'MM/dd/yyyy')"

Then use the output of the compose to replace the Date part in the Send Email Body or Subject.

 

15.PNG

See the results:

16.PNG

 

The lanugage used here is Workflow Definition Language.

If you have any further questions, please post back.

Regards,

Michael

Community Support Team _ Michael Shao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Anonymous
Not applicable

Hi @v-micsh-msft - Thanks for the reponse! Your solution makes perfect sense...and it seems like it should work easily for my situation, but my FLOW fails at the Compose input stage with: 

 

" InvalidTemplate. Unable to process template language expressions in action 'Compose' inputs at line '1' and column '2031': 'The template language function 'formatdatetime' expects its first parameter to be of type string. The provided value is of type 'Null'. Please see https://aka.ms/logicexpressions#formatdatetime for usage details.' "

 

In my case I'm trying to do:

 

"@formatdatetime(triggerBody()?['Report Sent to Installer'],'MM/dd/yyyy')"

 

Seems pretty straightforward? I've tried inserting dynamic content for the Report Sent to Installer date field and even

"@formatdatetime(triggerBody()?['Report%20Sent%20to%20Installer'],'MM/dd/yyyy')" but still with the same failure message...

 

 

Hi @Anonymous,

 

The error message indicates that the field value you have specified under the formatdatetime function is "Null".

 

If Report Sent to Installer is a field defined under your sharePoint list, and the value comes from the SharePoint -> When a new item is created trigger, then the formula should be:

"@formatdatetime(triggerBody()?['Report_x0020_Sent_x0020_to_x0020_Installer'],'MM/dd/yyyy')"

Flow uses _x0020_ to replace the space.

Besides, would it be convenient for you to share the flow configuration details?I will then perform some tests from my side and update you the proper formula.

Regards,

Michael

Community Support Team _ Michael Shao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Anonymous
Not applicable

Hi @v-micsh-msft, thanks again for the insight. However for some reason I'm still hitting the same error even when I format the Compose as suggested:

 

"@formatdatetime(triggerBody()?['Report_x0020_Sent_x0020_to_x0020_Installer'],'MM/dd/yyyy')"

 

What's the easiest way to share config details? Screenshots?

 

Many thanks,

Dan

I receive the same error message on formatting date times from SP. Have you figured out how to do this yet?

@WiggityZwiggity - no success yet. I'd be curious to hear from anyone who has successfully implemented a FLOW where a SP Date/Time field was formatted with something other than the default way it shows up in FLOW.

Hi @Anonymous,

 

Yes, the screenshots please.

For the flow configuration, including the Trigger, and the Action you used in your flow.

Also the Field from the SharePoint list.

 

In addition, please add a condition, then put the corresponding field content into the first Input box, click Advanced Mode, you should be able to find the corresponding field name, for example:

74.PNG

Use the item()?['haiz'] as the field parameter.

 

 

 

 

Regards,

Michael

Community Support Team _ Michael Shao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Thanks, unfortuantely I am trying to convert multiple date values within a get items action which would cause a nested for each.  I assume there is no way to do this globally? 

SLarson
New Member

So, I figured out the error in the example of this.

 

you shouldn't be using triggerBody() when you're getting the value from a sharepoint list

 

It should be body('Get Item')

 

e.g.  

  • @formatdatetime(body('Get_item')?['Impact_x0020_Start'], 'g')

Perform a compose for each date value before you call it later in the flow, then just select the correct Output (i.e. Output 1, Output 2)

Anonymous
Not applicable

Thanks for the suggestion @SLarson. It makes sense, but incredibly I *still* can't get this to work.

 

If I use this for my Compose Input:

 

@formatdatetime(body('Get_item')?['Report_x0020_Sent_x0020_to_x0020_Installer'],'MM/dd/yyyy')

I just get that entire string of text verbatim spit back in the e-mail where I specify Output.

 

If I try to use the same line from above but instead of using text to specifythe actual field I'm trying to reference (e.g. "Report_x0020_Sent_x0020_to_x0020_Installer") I insert it using parameter, then I get the same results except it doesn't even show the full field name in the e-mail, instead it shows this:

 

@formatdatetime(body('Get_item')?['@{triggerBody()?['Report_x0020_Sent_x0020_to_x00200']}'],'MM/dd/yyyy')  

 

Bold is added for emphasis. The implication being that the field name is actually too long to work with??? But that's a wild guess. I'd have expected the first approach here to work.

Not sure if you got this to work yet, but I found a solution here:  here  - recreated below.

 

1. Add a Compose Action after the trigger/Action, then specify the Compose input with the following format:

"@formatdatetime( ,'yyyy-MM-ddThh:mm:ss')"

2. Click at the first parameter part of the formatdatetime, then choose the corresponding dynamic content, save it,

3. Microsoft Flow won't save successfully, and would notify the error message of validation failed,which then we may find the corresponding part for the input,

4. Copy and paste the corresponding data within the braces @{ } into the function first parameter, then save the flow

Adding screenshots as reference:

68.PNG

69.PNG

70.PNG

 

 

 

Anonymous
Not applicable

Bravo @mmikkelson - brilliant! These steps allowed me to finally get this working! Thank you so much for posting this!

 

Putting aside my hours of troubleshooting and imagine someone else starting from these steps...this is still a ludicrous amount of effort IMHO to achieve something so simple (that again had a straightforward built-in feature in SharePoint Designer 2013) but it is what it is. This works!

 

Thanks to everyone who replied along the way!

 

 

Thanks so much! 

 

I've gotten some part of this working but not all of it!  When I look at the "compose"' outputs, it shows me a date of 08-16-2018 which is what I want.  However, when I run my flow, it still shows 2018-08-16.  Here is my input

 

"@formatdatetime(triggerBody()?['In_x002d_Hands_x0020_Date'],'MM-dd-yyyy')"

 

I deleted and then replaced my dynamic content field hoping that was the issue, but I'm still getting the date format I don't want.  

 

 

Thanks @mmikkelson this is exactly what I was looking for and it worked perfectly for me.

Why it has to be so difficult to change the date format I will never know.

Gary

Anonymous
Not applicable

Hoping you can help with mine. My compose input is: 

 

@formatDateTime(triggerBody()?['General_x0020_On_x002d_Sale'],'dd/MM/yyyy')

 

Yet it is still not working, what am I doing wrong? 😞

Anonymous
Not applicable

I don't know how I have managed to do this, but been playing around with it and it now works!

 

I entered this in "Expression" rather than into the "Input" text field.

 

formatdatetime(triggerBody()?['General_x0020_On_x002d_Sale'],'dd/MM/yyyy')

After all the research and troubleshooting, it was your solution that worked. Thanks @Anonymous!

Instead of showing the date format as 'yyyy/mm/dd.
Is there a way to show a long date? Like F riday March 1st, 2019

 

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

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.    

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 (2,631)