'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Power Automate Copy File Errors for SharePoint Home.aspx
Question details
The user needs to resolve an error in Power Automate where copying a SharePoint Home.aspx page between sites fails due to invalid data in a number field.
- Product
- Power Automate and SharePoint
- Device & OS
- not provided
- Scenario
- Automating the transfer of a SharePoint Home.aspx page to another site using a Power Automate flow.
- Observed behavior
- The flow fails with an error indicating a number field contains invalid data, preventing the Home.aspx page from being copied. This often happens due to Microsoft API changes or the nameConflictBehavior parameter.
Verify your SharePoint site permissions and confirm whether the Power Automate flow previously worked, as sudden widespread failures usually indicate a backend Microsoft API or schema update.
Route the Page Copy Through the Style Library or a Child Flow
Bypassing direct site-to-site copies by using an intermediate library or a child flow can help avoid the schema validation error.
If the error is caused by a recent change in how SharePoint handles site-to-site page copies via the Power Automate API, routing the file through a different library structure can successfully complete the transfer.
Navigate to Power Automate, locate your failing flow, and click 'Edit'.
Replace the existing 'Copy file' action with a new one that copies the Home.aspx page to an intermediate location on the destination site, such as the 'Style Library'.
Add a subsequent 'Copy file' or 'Move file' action to transfer the page from the intermediate 'Style Library' to the final 'Site Pages' destination.
If the intermediate library doesn't work, create a separate Child Flow containing just the 'Copy file' action and trigger it from your main flow.
Recreate the Copy File Action
Replacing the current action with a fresh instance can resolve temporary glitches or corrupted flow configurations.
Use an Azure Runbook with PowerShell
If Power Automate's native actions continue to fail due to schema changes, using a PowerShell script provides more robust control over SharePoint operations.
Discover WPS Office for Your Document Needs
While WPS Office does not directly manage SharePoint Power Automate flows, it offers a powerful, free, and lightweight alternative to Microsoft Office for creating, editing, and managing your daily documents. Enjoy high compatibility with Microsoft formats and a familiar interface.
- 1. Download WPS Office: Visit the official WPS website and download the free installer for your operating system.
- 2. Install the Software: Run the downloaded installer and follow the on-screen instructions to complete the lightweight setup.
- 3. Open and Edit Office Files: Launch WPS Office to easily open, edit, and save your Microsoft Office documents without format issues.
Frequently Asked Questions
Why does the Power Automate copy file action report invalid data in a number field?
This error often occurs due to Microsoft backend changes related to the nameConflictBehavior parameter, where 'Replace' is passed as the number 1 instead of a recognized string, causing SharePoint's schema validation to fail.
Can I move a SharePoint Home.aspx page directly without Power Automate?
Yes, you can manually copy or move the Home.aspx page using the 'Copy to' or 'Move to' feature directly within the SharePoint Site Pages library UI if automation is currently failing.
Will reverting to a deprecated Copy file action fix the SharePoint page issue?
No, testing indicates that the issue does not involve the deprecated action. The error persists across different versions of the standard Copy file action due to underlying SharePoint API updates.
What is the Style Library workaround for copying SharePoint pages?
The workaround involves configuring your flow to first copy the page into the Style Library (an intermediate location) and then moving it to the final Site Pages destination to bypass the direct site-to-site schema conflict.
