Others

How to Fix Power Apps and Power Automate ISO 8601 Date Errors

WPS Content Manager Sep 30, 2026 868 views

Question details

Users encounter formatting errors when passing date values from Power Apps or Power Automate to a SharePoint list.

How to Fix Power Apps and Power Automate ISO 8601 Date Errors

Product: Power Apps and Power Automate
Device & OS: not provided
Scenario: Submitting or patching date values to a SharePoint list via a form submission, flow trigger, or Save button.
Observed behavior: The system returns an error because the date value is passed as an object or an improperly formatted string instead of the expected ISO 8601 or RFC 3339 date-time format.

Before you start

Ensure you have edit permissions for both the Power App canvas and the target SharePoint list to modify column settings and formulas.

Solution 1Recommended

Format the Date Value in Your Patch Formula

Ensure the date value sent to SharePoint is formatted as a correct ISO 8601 string rather than a complex object.

Power Apps often stores dates as objects internally, but SharePoint expects a specific text-based date format (ISO 8601/RFC 3339) to process it correctly.

Select the Save button

In your Power Apps canvas, select the 'Save' or 'Submit' button that triggers the data submission to SharePoint.

Open the OnSelect property

Navigate to the top formula bar and select the 'OnSelect' property from the dropdown menu.

Wrap the DatePicker value

Locate the date column in your Patch formula and wrap the DatePicker value using the Text function. For example, modify it to read: Text(DatePicker1.SelectedDate, DateTimeFormat.UTC).

Test the submission

Save and publish your app, then try adding a new item to verify if the ISO 8601 error is resolved.

Format the Date Value in Your Patch Formula

Formatting Success: Converting the date object to UTC text ensures universal compatibility with SharePoint's backend database.

Solution 2

Configure the DatePicker Control Properly

Review the DefaultDate and StartYear/EndYear properties of your DatePicker control to ensure it provides valid inputs.

Solution 3

Troubleshoot Power Automate Flow Triggers

If a flow is triggered from Power Apps, ensure the date variable is explicitly converted before updating SharePoint.

Free Microsoft Office alternative

Manage Your SharePoint Data Exports Easily with WPS Office

While troubleshooting Microsoft Power Apps errors, you may need to export SharePoint lists to Excel for data verification and formula checking. WPS Office provides a lightweight, highly compatible, and free alternative to Microsoft Office for seamless data analysis.

1. Download WPS Office: Download and install the free WPS Office suite from the official website.
2. Open exported SharePoint lists: Export your problematic SharePoint list to Excel and open the .xlsx file directly in WPS Spreadsheet.
3. Analyze date formatting: Use familiar formula tools to format cells, check date values, and troubleshoot inconsistencies before importing data back into Power Apps.

Fully compatible with Microsoft Excel (.xlsx) formats exported directly from SharePoint.Lightweight design ensures faster loading and processing of large list datasets.Familiar user interface with advanced pivot tables and formula support, requiring no learning curve.All-in-one free suite containing Word, Excel, PowerPoint, and PDF alternatives.

microsoft office alternative - wps office

Frequently Asked Questions

Why does SharePoint require an ISO 8601 date format from Power Apps?

SharePoint securely stores date and time values in UTC using the ISO 8601 standard (e.g., YYYY-MM-DDTHH:mm:ssZ). This strict standardization ensures time consistency across different global time zones, user profiles, and regional settings.

How can I fix a date error when importing data from Excel to Power Apps?

Ensure the date column in your Excel table is formatted strictly as a 'Date' or 'Text' string. When patching this imported data, use the 'Text()' function in your Power Apps formula to enforce the ISO 8601 format during the SharePoint submission.

What is the difference between passing a date object and a date string to SharePoint?

A date object contains complex metadata representing a specific time construct in the application's memory. A date string (like RFC 3339) is a standardized plain-text representation that external databases like SharePoint can parse without translation errors.

Can I use the DateValue function to fix SharePoint date errors?

Yes. If your date is received as a standard text string, wrapping it in the DateValue() function can correctly convert it to a standard date type inside Power Apps. You can then format it into an ISO string to successfully patch to SharePoint.

Office Quick Solutions