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: Most helpful
Most helpful Newest Oldest
  1. 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
  2. Anonymous
    2024-09-23T18:38:04+00:00

    This Article might help for clarification:

    Important changes (deprecations) coming in Power Platform - Power Platform | Microsoft Learn

    What's the link with the issue raised in this thread?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2024-09-23T10:42:10+00:00

    Hi Bittor,

    mine is also in production (in customers tenant)

    As I said to Tadej I think it is better that they receive multiple tickets/calls about it

    so it will be escaleted quicker,

    thanks,

    Bart

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2024-09-23T10:38:38+00:00

    Thanks,

    maybe it is better to open a ticket yourself anyways

    so they'll see the problem is in multiple tenants

    regards,

    Bart

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2024-09-23T10:01:57+00:00

    Hi,

    I see two Copy File actions (in the SharePoint group)

    One Copy File (deprecated) but this is within the same site collection

    the other (Copy File) gives the error we are discussing here.

    I only noticed the depricated one as of today....

    Bart

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments