Power Automate Copy file no longer works - Copy SharePoint Home.aspx to New SharePoint site

Anonymous
2024-09-19T10:30:35+00:00

Need help:

Power Automate Copy file not working since 18.9.2024 - copy SharePoint Home.aspx to New SharePoint site, error: Invalid number value. A number field contains invalid data. Please check the value and try again. CallStack -- at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx) at Microsoft.SharePoint.Library.SPRequest.SetGhostedFile(String setupPath, Byte setupPathVersion, Int32 iVersion, Guid& pguidListId, Guid& pguidDocId, Int32 lDoclibRowId, Int32 iAuthorId, String authorLogin, String serverRelativeUrl, String targetUrlWebRelative, Boolean isInDocLib, Boolean isMigration, Boolean isPublishing Object varProperties, Int64 PutFileOpt) at Microsoft.SharePoint.Deployment.FileSerializer.SetGhostedFile(Object fileOrListItem, SPLoggerObject loggerObject, SPWeb web, Guid existId, SPResourcePath fileUrl, SerializationInfoHelper infoHelper, SerializationInfoHelper infoHelperListitem, Boolean fileExistsInDb, Nullable`1 isLastVersion, StreamingContext context) clientRequestId: 1f3421bf-23fb-48aa-887a-e*** serviceRequestId: 77bf51a1-d04f-9****

Microsoft 365 and Office | SharePoint | For business | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

48 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-09-24T13:35:16+00:00

    For me, I get this error message when copying to a site URL that does not have numbers in the URL (i.e., https://tenant.sharepoint.com/sites/ABCD but it succeeds when I run the action to a URL that has numbers (i.e., https://tenant.sharepoint.com/sites/122345). What does this mean??

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-09-24T22:44:06+00:00

    I have the same issue with copying some of our site pages, I get this error even using the native copy to function in site pages library. However, it only affects some old site pages.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-09-25T06:19:06+00:00

    Hi Victoria,

    that is odd in my tenant the destination site alias is a 6 digit number

    Can you try the workaround?

    1. Copy from source to a document library in the destination site
    2. Copy from this document library to the sitepages (within te destination site)

    it works for me!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-09-25T06:29:29+00:00

    Hi everyone, I do not see my post from yesterday, so I post it again:

    => I've found a workaround (below) on Reddit and tried this myself and it works!!!!

    Workaround

    1. Copy the source page/file from the source site collection to a document library in the destination site collection (using the same Copy File action)
    2. Copy the page from the (destination) document library to the SitePages list in the destination site (again using the same Copy File action)

    So until fixed or better solution, I think we can use this instead.

    ps: The SharePoint engineer handling my ticket suggested contacting Power Automate support, but I opened the ticket using Power Automate Admin Center

    And as you can see in the flow history input and output it has nothing to do with flow,

    it is from the SharePoint REST calls used, you will have this result from any other client application.

    Can anybody try this as well?

    (simple workaround as it is just one extra copy action)

    regards,

    Bart

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2024-09-25T07:54:52+00:00

    Something's going on .... I was just trying out the workaround kindly provided by Bart Korn1 by trying it with one element of a Flow that had 18 that had been failing. When I tested the Flow, a lot of the elements that had previously been failing with the 'Invalid number' issue suddenly worked (along with Bart's workaround). There's still a few that a failing, but I'm wondering if Microsoft have put in a partial fix ...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments