We are trying to port a flow based on a SharePoint list to another site collection in another tenant with the same list. The list has a custom content type, and the flow consumes several of the content type's custom site columns throughout the flow. Here is an example of one step that consumes the custom site columns:
The problem is when I export the flow to a package, and import it to another tenant, it incorrectly maps a few of the fields (not all) in a few of the steps. e.g. if you open up the step above some of the mapped columns of the list are pointing to the wrong column.
We have double checked all the site columns in the list and the content type, and they seem to be correct. Does anyone know why this would happen?
Hi @Scot15 ,
Could you please share a screenshot of the column that are wrong mapped?
Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Do you mean a screenshot of the column from the flow, or from the SharePoint list?
An example from the flow is in my original post. The column referenced at the top "Naming_Prefix" should actually be "New_Team_Id", but it was changed to "Naming_Prefix" when the flow is imported to a new tenant.