cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
pmontalbano
Frequent Visitor

Trying to pass Date from powerapps to Flow to Sharepoint

I have what I thought would be a simple PowerApps App that collects a few pieces of information and uploads this to SharePoint. I found that since I am including a picture from the camera control I needed to do this with a Flow. The date fields were being passed to the run command from a DatePicker using DatePicker.SelectedDate. For the Flow, I tried to use:

formatDateTime(triggerBody()['Updatefileproperties_ReportDate'],'MM-dd-yyyy')

in the expression field but I ended up with the following error in PowerApps:

pmontalbano_1-1672348909555.png

Then I decided to hard code the date as string and use variables in the flow to take a string date and convert to Date. then add the Date to the File Properties Update. The flow now contains:

pmontalbano_2-1672349532224.png

pmontalbano_3-1672349558424.png

This produces the exact same error from PowerApps. To make matters worse, when I look at the 28 day run history, none of my attempts show up. There are only two entries and both are from tests I performed, not from the manual action from PowerApps. So I have 2 questions:

1. how can I pass the DatePicker.SelectedDate to the Flow to end up in a Date column in SharePoint?

2. Why am I not seeing the Flows fail? In fact, no matter what change I make in PowerApps or in Flow, the error message I get is exactly the same. This seems very strange to me.

 

Bonus points for anyone that can tell me how to update only a subset of fields when creating this record as some fields in SharePoint are not required and will be modified later by users directly in SharePoint.

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
pmontalbano
Frequent Visitor

Solved it. Instead of passing 

DatePicker1.SelectedDate

 I am now passing

Text(DatePicker1.SelectedDate, "yyyy-mm-dd")

This sends the correct format to flow and the flow now works.

View solution in original post

9 REPLIES 9
Pstork1
Most Valuable Professional
Most Valuable Professional

You can pass the date directly to the Flow without changing the format if you use the Power Apps V2 trigger and add a data parameter.  Then in the flow use one of the standard ISO 8601 formats when formatting the date to supply it to SharePoint.  That is what SharePoint expects.  Here's the format command I used in my test. 'u' is one of the standard ISO 8601 formats.

 

formatDateTime(triggerBody()['date'],'u')

 



-------------------------------------------------------------------------
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 for your help. I am still having an issue however. I did change the trigger in my flow to be a PowerApps V2 trigger and added several Data Parameters including 2 Date fields.

pmontalbano_0-1672532484352.png

 

Just to test, I did not add the variable to the update file properties for the corresponding columns in SharePoint. So essentially, I am just collecting the parameter from the DatePicker control using SelectedDate.

pmontalbano_2-1672532741578.png

 

This failed with error:

pmontalbano_3-1672532772718.png

 

This shows that PowerApps is passing a String, not a date to the flow. Just to be thorough, I added the formula as you suggested to the update file properties for the fields I need to update, but this still failed with the same error. I must be missing something here. Why is the DatePicker.SelectedDate passing a String instead of a Date?

 

 

 

One more thing to note. The Trigger in Flow shows "Please enter or select a date (YYYY-MM-DD)" suggesting that the date needs to be passed from PowerApps in YYYY-MM-DD format but is being passed as MM-DD-YYYY in string format.

pmontalbano
Frequent Visitor

Solved it. Instead of passing 

DatePicker1.SelectedDate

 I am now passing

Text(DatePicker1.SelectedDate, "yyyy-mm-dd")

This sends the correct format to flow and the flow now works.

I've been searching for ages on how to solve this.

I've been updating SharePoint via PowerApps and PowerAutomate, using Shane Youngs video,  which was great. It all worked fine until I tried to pass a date through.

Can I just check what your fix was...

In PowerApps, you passed through "Text(DatePicker1.SelectedDate, "yyyy-mm-dd")

Really appreciate any help

Thanks for any help

Hello, Yes passing the date from PowerApps to the flow uses the Text() function as you mentioned. The flow takes this input into a Date parameter in the PowerAppsV2 trigger. Note that I did need to use the PowerAppsV2 trigger and not the PowerApps trigger. Then the format needs to be changed. In the field you are trying to use this date, you will need to format it properly. Instead of just picking your date parameter, you need to enter the following expression:

 

formatDateTime(triggerBody()['Date'],'u') Where ['Date'] is the name of your parameter. Hope it helps.
CLISS
Frequent Visitor

Hi Bethany

Im using the Power V2 trigger to send documents to a SharePoint library via a Gallery but am having trouble with passing Dates as metadata due to this formatting issue. I'm using the instructions below and the files are successfully created in SP with the text field metadata but I can't get the dates to pass. I get the error that 'Documents' can't use the 'Text' function. Can you see a solution to this?

Thanks

Craig

ForAll(galAttachments.AllItems As Document,
MultiUploadofFilesToSPLibrary.Run({
contentBytes: Document.Value,
name: Document.Name}
,Document.mSalesComment.Text
,Document.Text(mEffectiveFrom.SelectedDate,"[$-en-US]yyyy-mm-dd")
,Document.Text(mEffectiveTo.SelectedDate,"[$-en-US]yyyy-mm-dd")
));

The date needs to be passed as an ISO 8601 formatted date, which is a string.  In ISO 8601 the year always comes first. You need to enclose the date in a Text format like this

Text(DatePicker1.SelectedDate,DateTimeFormat.UTC)

when you pass it to the flow.  That will put it in ISO 8601 format.



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

I found the answer to my question if anyone was interested:

I moved the "Document." inside the Text function so that it reads:

,Text(Document.mEffectiveFrom.SelectedDate,"[$-en-US]yyyy-mm-dd") ,Text(Document.mEffectiveTo.SelectedDate,"[$-en-US]yyyy-mm-dd")

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 in the Forums 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 of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (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. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     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 Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27  

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

Top Solution Authors
Top Kudoed Authors
Users online (3,892)