Forum Discussion

Anthony-123's avatar
Anthony-123
Iron Contributor
Feb 18, 2025

What is '_ip_UnifiedCompliancePolicyUIAct'

Our PowerAutomate workflow has broken due to an error that reads:

Column '_ip_UnifiedCompliancePolicyUIAct' does not exist. It may have been deleted by another user. 

This is not a column that has ever existed, to my knowledge. The action in this workflow is copying a folder from one site to another. 

I've created a new flow that just copies the folder and I'm getting the same error. When I try to manually copy the folder in SharePoint I get an error that "something went wrong". In both cases, the folder does copy to the destination. It's just that the flow is failing. 

I've created the column _ip_UnifiedCompliancePolicyUIAct in both the source and desitnation folder and this appears to resolve the issue. No data is found in the column. 

 

  • Kathy Murphy's avatar
    Kathy Murphy
    Copper Contributor

    Any updates from Microsoft on this as to the purpose of the field and why it started causing issues?

    • yoink's avatar
      yoink
      Copper Contributor

      I'm not aware of any updates.

      I was able to find a workaround for my specific use case, YMMV:
      - Unable to copy a folder from one site to another, found I could still copy folders between libraries in same site. Copied my folder templates to contain everything in one site and mapped flow to new source.

  • yoink's avatar
    yoink
    Copper Contributor

    I'm having the same issue. Tried the Copy folder action configured from scratch in its own flow and it's failing consistently. In my case, the source folder contains a few files. When the flow runs, an empty folder is created in the target destination, then the flow errors out.

    A colleague suggested it could be related to MO1009364 - Microsoft 365 suite

  • jreeseSoV's avatar
    jreeseSoV
    Copper Contributor

    This issue also broke a few of our PowerAutomate flows that move SharePoint folders. It first occurred for us at 8:50am EST on Feb 18. Nothing was changed in the flow or the SharePoint site to cause this error.

Resources