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

Sending Date and Time to SharePoint Column Type Date and Time

New to PowerApps. I'm a high school teacher not a developer. This is my first question to this community. Thanks in advance.

I have a DateAndTime Input in a form. I have a button to insert Now() into the DateAndTime Input. However, we also want to capture entries that were collected hours earlier, even days earlier. I have validation to prevent invalid entries. I've been unsuccessful to find a way to send the data to SharePoint as Type Date and Time. I've been sending it as Single line of text,  but that is not sufficient. We cannot sort properly if it's in Type Single line of text. I've figured out how to send the Now() data using Patch() but that also isn't sufficient.

1 ACCEPTED SOLUTION

Accepted Solutions
Anonymous
Not applicable

@paguirre 

Thanks for this, this is very helpful.

 

If you have validation in-place to ensure users enter data in the correct format then you can simply us the DateTimeValue() function to achieve what you want, eg

// On your Save Button
Patch(Attendance, Defaults(Attendance), {DateAndTime: DateTimeValue(DateandTime_TextInput.Text)})

// where DateandTime_TextInput is the name of your TextInput control

It maybe helpful to read the documentation related to the Date/Time functions here

 

Here is the above in action, Note: the label below the textinput is to demo what's happening in the background

DateandTime_toSP.gif

You mention 'Single line of text' is that the column you are Patching to in SP? This needs to be a Date and Time column with Date and Time selected if you wish to store actual Dates with Times. Otherwise you are just storing Text. You may need to setup a new column rather than changing the one you have already.

 

I'd also recommend setting up another column called DateTimeNumber as a Number/Numeric column. Then adjust your Patch to this:

// adjusted Patch
Patch(Attendance, Defaults(Attendance), 
        {DateAndTime: DateTimeValue(DateandTime_TextInput.Text),
         DateTimeNumber: Value(Text(DateTimeValue(DateandTime_TextInput.Text),"yyyymmdd"))
        }
)

What this will do is add a number to SP that represents your Date. You will then be able to Filter your SP List (in PowerApps) based on this number. There is currently no way to Filter dates in SP by using > or < but this is a workaround. You can then filter by 'Date' by filtering the Number column, eg

 

To filter greater than or equal to 4/1/2020 you can use something like:

Filter(mySPList, DateTimeNumber >= 20200401)

You cannot do the above with a DateTime column. This filtering technique will help you with a large dataset >2000 records.

 

Let me know how you get on.

View solution in original post

7 REPLIES 7
Anonymous
Not applicable

@paguirre 

If you setup your SharePoint column as Date & Time then created the Form in PowerApps the functionality should all be there for you. Is the Now() just to make things easier for users?

 

Can you share some code and screenshots of what you are trying to achieve?

 

Also, depending on how large your SP list will get (>2000 records) you may be better storing the date and time as a number? I can elaborate further if needed.

Text Input: Default: If(IsBlank(DateNow1), ThisItem.DateAndTime, DateNow1)

 

Date and Time Button: OnSelect: UpdateContext({DateNow1: Now()})

 

Save Button: OnSelect: Patch(Attendance, Defaults(Attendance), {DateAndTime: Now())

 

All that gives me is the Date and Time at the moment I press the Save Button. It was pointless to put have the Date and Time Button. I want the Text Input field to be the Date and Time that the user wants it to be either Now() or an earlier Date and Time. We will probably have > 2000 records. We collected records in Attendance that nearly reached 8000 before we used a new SharePoint List.

 

There are only eight columns in the SharePoint List and two of them are generated by SharePoint. For a school getting the Date and Time as Type Date and Time is a big deal. Thanks for replying so quickly.

 

 

 

 

Text Input: Default: If(IsBlank(DateNow1), ThisItem.DateAndTime, DateNow1)

 

Date and Time Button: OnSelect: UpdateContext({DateNow1: Now()}) & UpdateContext({varClock:false})

 

Save Button: OnSelect: Patch(Attendance, Defaults(Attendance), {DateAndTime: Now())

 

All that gives me is the Date and Time at the moment I press the Save Button. It was pointless to have the Date and Time Button. I want the Text Input field to be the Date and Time that the user wants it to be either Now() or an earlier Date and Time. We will probably have > 2000 records. We collected records in Attendance that nearly reached 8000 before we used a new SharePoint List. There are only eight columns in the SharePoint List and two of them are generated by SharePoint. For a school getting the Date and Time as Type Date and Time is a big deal.

The HintText: "M/D/YYYY H:MM ?M" is for validation. The code is correct that's just for the users to realize there's validation. It doesn't match PowerApps guidelines.

TextInput-DateAndTime and Button.png

Anonymous
Not applicable

@paguirre 

Thanks for this, this is very helpful.

 

If you have validation in-place to ensure users enter data in the correct format then you can simply us the DateTimeValue() function to achieve what you want, eg

// On your Save Button
Patch(Attendance, Defaults(Attendance), {DateAndTime: DateTimeValue(DateandTime_TextInput.Text)})

// where DateandTime_TextInput is the name of your TextInput control

It maybe helpful to read the documentation related to the Date/Time functions here

 

Here is the above in action, Note: the label below the textinput is to demo what's happening in the background

DateandTime_toSP.gif

You mention 'Single line of text' is that the column you are Patching to in SP? This needs to be a Date and Time column with Date and Time selected if you wish to store actual Dates with Times. Otherwise you are just storing Text. You may need to setup a new column rather than changing the one you have already.

 

I'd also recommend setting up another column called DateTimeNumber as a Number/Numeric column. Then adjust your Patch to this:

// adjusted Patch
Patch(Attendance, Defaults(Attendance), 
        {DateAndTime: DateTimeValue(DateandTime_TextInput.Text),
         DateTimeNumber: Value(Text(DateTimeValue(DateandTime_TextInput.Text),"yyyymmdd"))
        }
)

What this will do is add a number to SP that represents your Date. You will then be able to Filter your SP List (in PowerApps) based on this number. There is currently no way to Filter dates in SP by using > or < but this is a workaround. You can then filter by 'Date' by filtering the Number column, eg

 

To filter greater than or equal to 4/1/2020 you can use something like:

Filter(mySPList, DateTimeNumber >= 20200401)

You cannot do the above with a DateTime column. This filtering technique will help you with a large dataset >2000 records.

 

Let me know how you get on.

Thank you so much. After reading your reply and going to the site you provided a link to, I came to the conclusion that in the Patch of the Save Button all I needed to change was the following.

 

Save Button: OnSelect: Patch(Attendance, Defaults(Attendance), {DateAndTime: DateTimeValue(Inp_DateAndTime.Text))

 

Now in SharePoint the DateAndTime column that is Type: Date and Time, not Text or Single line of text, records the Date and Time that was set by the Date and Time Button, or by what the user entered under the requirements of the validation. 

 

Yay!

 

Thank you very much. Stay safe and stay healthy.

 

Something to keep in mind with the solution I ended up using. Once the user presses the Date and Time Button the variable that sets Date and Time is set to Now(). As I stated earlier the users were using the Date and Time placed by Now() as a template to satisfy the validation requirements. However, when the Save Button is pressed and the Patch runs the DateTimeValue(Inp_DateAndTime.Text) will be set to Now() not to what the user keyed in. That was frustrating. I developed a solution I do not believe is very elegant but does the job. I made it a two step process that informs the user they need to enter the earlier Date and Time without pressing the Date and Time Button. Those that want to use Now() will press the the Date and Time Button  basically twice. I used twice as a way to train them not to immediately press the Date and Time Button. As I said, it is not an elegant solution. I'm am hopeful that kind Eelman or some other worthy might share some insights. I'm at a lost how to do this efficiently and user friendly.

Thanks,

Anonymous
Not applicable

@paguirre 

I didn't comment on your flow of controls but I figured you may run into some issues. My suggestion would be to add a DatePicker and Dropdowns for Hrs & Mins like in this post https://powerusers.microsoft.com/t5/Building-Power-Apps/Is-there-a-TIME-PICKER/td-p/65252.

 

You would remove the TextInput field and add the DatePicker to that part of you app and put the Hrs & Min Dropdowns beside it.

 

This will take up a little more real estate in your app but will be well worth it. This setup will make validation of the data going to SP so much easier - or you can try to write some regular expression to validate your TextInput?

 

I would then remove the 'Set Date Time to Now()' button and just do a check inside your Patch, ie

Patch(..., {DateandTime: If( IsBlank(DatePickerDate1.SelectedDate), Now(),
            // this part is from the post link
            DatePickerDate1.SelectedDate + Time( Value(DropdownHour.Selected.Value),
            Value(DropdownMinute.Selected.Value), 0)
           }

What this is doing is checking if the DatePicker is Blank(), if it is then use Now() as the DateTime if not then use the selected DateTimes. 

 

I would also add Reset() functions to the OnVisible property of your screen and possibly give the users options to Reset when they want with a 'X' icon. Code for both of these would be:

Reset(DatePickerDate1); Reset(DropdownHour); Reset(DropdownMinute)

For the DatePicker, and the 2 Dropdowns also do the following:

- Set the 'AllowEmptySelection' Property = true, and

- Clear the 'DefaultDate' and 'Default' Properties, ie leave them blank

 

That should do it, I think.

 

Let me know if you get stuck on any of the above and I'll help out.

 

 

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 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     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 Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

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

Top Solution Authors
Top Kudoed Authors
Users online (2,154)