cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Fish_mm
Regular Visitor

Get DayOfWeek from DateTimeReceived when new emails arrives

Hi All,

 

Anyone can help me on below?

 

I want to set a condition where 

if DateTimeReceived is equal to 6 (or Saturday)

Forward email to specified email address. 

 

How should i set the if DateTimeReceived is equal to 6 (or Saturday)?

 

i try with 

Compose

DayOfWeek(triggerbody()?['DateTimeReceived'])

but return this is not valid expression.

1 ACCEPTED SOLUTION

Accepted Solutions

Hi @Fish_mm construct your flow as in the image below.
Rob
Los Gallardos
If I've answered your question or solved your problem, please mark this question as answered. This helps others who have the same question find a solution quickly via the forum search. If you liked my response, please consider giving it a thumbs up. Thanks.

dayofWeek.png

View solution in original post

22 REPLIES 22
Pstork1
Most Valuable Professional
Most Valuable Professional

I suspect your problem is that the dayOfWeek function expects the date in the form of a Timespan string, not a dateTime value.  Try this formula instead:

dayOfWeek(formatDateTime(triggerBody()['DateTimeReceived'],'D'))



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



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

Hi @Fish_mm construct your flow as in the image below.
Rob
Los Gallardos
If I've answered your question or solved your problem, please mark this question as answered. This helps others who have the same question find a solution quickly via the forum search. If you liked my response, please consider giving it a thumbs up. Thanks.

dayofWeek.png

Capture.PNG

it returns with this error..

@Fish_mm your dayofWeek function doesn't use the same syntax that I put in my post. Try it with what I put, I didn't use formatdateTime but used a compose control with

dayOfWeek(triggerBody()?['DateTimeReceived'])

and it works fine for me. If you follow the steps in my image above you should be fine.

Rob
Los Gallardos
If I've answered your question or solved your problem, please mark this question as answered. This helps others who have the same question find a solution quickly via the forum search. If you liked my response, please consider giving it a thumbs up. Thanks.

@RobElliott 

i tried and it also returns error 

 

InvalidTemplate. Unable to process template language expressions in action 'Compose' inputs at line '1' and column '2683': 'The template language function 'dayOfWeek' expects its parameter to be a string that represents a timestamp. The provided value is of type 'Null'. Please see https://aka.ms/logicexpressions#dayofweek for usage details.'.

Could you post a screenshot of your flow as it currently is as that will make it easier for us to find out why it's not working for you.

Rob
Los Gallardos
If I've answered your question or solved your problem, please mark this question as answered. This helps others who have the same question find a solution quickly via the forum search. If you liked my response, please consider giving it a thumbs up. Thanks.

Pstork1
Most Valuable Professional
Most Valuable Professional

As I mentioned in my reply, DayOfWeek is expecting a TimeSpan string and you are giving it a DateTime value.  You need to enclose the DateTime value in a FormatDateTime() function to translate the dateTime value to a Timespan string.  Try this function.

dayOfWeek(formatDateTime(triggerBody()['DateTimeReceived'],'D'))


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

It looks from the error message that you also need to make sure that you are actually passing a DateTime value into the Flow.  The error says it is null.



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

@Pstork1the flow is as below.

Did i make some mistake somewhere?

 

a.png

@Pstork1 @RobElliott 

 

I think i know what is the mistake i made. If i applied in recurrence Flow, it will returns error. But if i use automated, it works fine. 

Pstork1
Most Valuable Professional
Most Valuable Professional

Is it still throwing the error?  If it is then you need to verify that DateTimeRecieved actually contains data and is not Null.  Otherwise the function now looks to be correct



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

Yes the trigger should be "When a new email arrives". The recurrence is unecessary and causing the problem. You're still not using the flow I posted but if it works that's great.

Rob
Los Gallardos
If I've answered your question or solved your problem, please mark this question as answered. This helps others who have the same question find a solution quickly via the forum search. If you liked my response, please consider giving it a thumbs up. Thanks.

@RobElliottinstead, I use your recommended query and use automated flow and it is working fine now. 

 

Thanks @RobElliott and @Pstork1 !

Anonymous
Not applicable

Hello

I know this an old post but the issue I have is relevant to this one at the moment, and I hoe you can help me with this. I have created the flow fine, the Day of Week function works and converts the date to a day of the week number (3), as it is a Wednesday the reference date relates to. However, the Condition action is to update the Case, from which the reference date was obtained. It is writing the result of the Compose function (3), to the target day of the week field. I need to be able to write it as "Wednesday". Can you show me how I can set the target field in the Update action to do this?

 

many thanks

 

Chris

Pstork1
Most Valuable Professional
Most Valuable Professional

If you use the same date that is used in the DayofWeek() function and instead put it in a format date time you can generate the day for that date.

formatDateTime('2021/04/14','dddd')

  The example uses a static date time string, but you can use the same datetime value used to get that it is day 3 of the week. 



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

Hello

Thank you for this response. Is the format function an extra action in the flow, or is it added to the target day of the week field in the record update action? This field has been created as a text field of maximum length 12 characters and the flow rejects a string greater than 12.

 

Chris

Anonymous
Not applicable

Just to clarify the flow logic:

Day of the Week 1.PNG

While the flow works fine when checking for the Compose value (in this case 3), as the reference date is always changing, the Compose output cannot be written as a constant value (ie 3). So there are 2 issues with my flow:

 

1. Having a variable reference to the Compose output

2. Formatting the Compose output to a text string (ie Wednesday), to insert into the day of the week target field

 

Sorry if I wasn't clear on this.

 

Chris

Pstork1
Most Valuable Professional
Most Valuable Professional

The formula is used in the target day of the week field in the record update action.  The output will be the day name so the 12 characters shouldn't be an issue.  Enter the formula using the Expressions Tab on the dynamic content dialog.



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

If you use the formula I provided in place of the day of the week formula you can change the condition to check for the name of the day instead of the number.  Then use the same compose output for your update.



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

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 | Results 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,899)