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-24T05:54:36+00:00

    Hi Sophia!!!!

    Any news or solution to the problem?

    I need to try to solve it or look for an alternative to it, since I have it implemented in a client and this action is part of a core process for them.

    Thank you for your attention

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-09-24T07:01:34+00:00

    My Copy File flow has also worked fine for years, until suddenly last week it stopped with the same error as everyone else.

    Tried creating a new flow. Tried all different settings. No success.

    Then yesterday (Sept 23, 11.16 AM CET), I tried to copy a page I've previously copied (in May) - and it worked! New file name had an added '1' at the end.

    But then it broke again when I tried another previously copied page.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-09-24T07:08:02+00:00

    It seems that this is an old problem re-appearing:

    Power Automate SharePoint Copy File action started failing - Stack Overflow

    At that time, it took two days to solve.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2024-09-24T08:18:16+00:00

    We also have multiple flows that previously worked flawlessly and are now suddenly no longer functioning. A site cannot be found if it does not have a homepage. We would like a solution for this issue, which apparently also occurred over a year ago.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2024-09-24T09:02:05+00:00

    I'm still trying to debug this to establish exactly where the issues is. Here's my hunches:

    1. This does NOT appear to be related to any deprecated functionality. There are 2 actions - 'Copy file' and 'Copy file (deprecated)'. I'm using 'Copy file' and having the issue.
    2. The only number in the outputs appears to be in the 'If Another File is Already There' field. When setting the 'Copy file' parameters this is set to 'Replace', but in the Outputs it appears as '1'.
    3. Here's what Copilot makes of the error:
      "It seems that the error occurred due to an "Invalid number value" in the Copy_file operation. To fix this, check the parameter 'nameConflictBehavior' in the CopyFileAsync action. Ensure that the value provided for 'nameConflictBehavior' is a valid number according to the requirements of the destination library. Double-check the value being passed for 'nameConflictBehavior' to resolve this error."
      This appears to support the theory that the issue relates to the parameter of what to do if a file already exists in the destination.
    4. I've tried recreating the Flow and simplifying it as much as possible, using both Classic and New Designer, and still get the same error.
    5. Conclusion: Microsoft have broken / changed something and need to fix it ...

    If you've found anything further, please let us all know!

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments