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 No comments

48 answers

Sort by: Oldest
  1. 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 No 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 No comments
  3. 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 No comments
  4. Anonymous
    2024-09-25T12:51:40+00:00

    I was successfully able to copy pages by using Fix one that Chris Eaheart recommended (we have a fairly simple SharePoint template). I completely deleted the copy action and re-created it within the same flow rather than creating another flow. One thing I did notice was that when you enter a value into "If another file is already there*" It would change to an integer of 1 if you wanted it to replace a file with the same name. I manually entered 1 under (choose custom value) into my older flow with the same issue and that started working again as well. Could be they fixed things on their end, and this just happens to work now but figured I'd pass along what worked for me.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-09-25T13:26:41+00:00

    Hi Chris

    thanks

    Fix 1 works but that is (for me) as of today

    friday and monday I tested this already but got the exact same error
    Yesterday I used fix 2 that worked fine,

    regards,

    Bart.

    Was this answer helpful?

    0 comments No comments