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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2024-09-25T11:42:45+00:00

    I have found three different fixes - it just depends on how extensive you want to get and the nature of your page and workflow.

    Fix 1 - Simply rip out the copy file action, and replace it with the exact same action

    Fix 2 - If your page is fairly simple (no custom components), then you can two a step copy - first copy the page to a different location, such as Style Library, and then copy the page from the Style Library to your Site Pages library

    Fix 3 - If your page has custom components, Fix 2 will not work for you - in this case, you will need to create a child flow that does the copy file action, and then call that child flow from your main flow.

    All three of these fixes have worked for different tenants, just depending on the nature of the workflow and page.

    Something about the action has changed, and MSFT did your provide an abstraction layer for old actions - they simply updated the action and all new instances of the action will work, but old actions have to be replaced (which introduces the new code and/or config behind the scenes)

    There's one other possible fix if nothing above works - I haven't tested this one. You could call an Azure Runbook that uses PowerShell to copy the page. Again, quite the workaround, but it should work.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-09-25T10:28:32+00:00

    Yes! It worked for me; tried two different source sites and two different destination sites.

    The copy folder also worked for the files in Site assets library.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-09-25T10:07:52+00:00

    Copying the file worked properly but then I get this error:

    Sorry, something went wrong

    NoComponentId

    Technical Details

    Go back to site

    Was this answer helpful?

    0 comments
  4. 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
  5. 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