process-migrator icon indicating copy to clipboard operation
process-migrator copied to clipboard

Published 20 hours ago • verified publisher icon microsoft

Process import validation failed. Field in target Collection conflicts with 'Accepted By' field with a diffrent refrence name or type

Open shiva-gattu opened this issue 2 years ago • 2 comments

Process import validation failed. Field in target Collection conflicts with 'Accepted By' field with a diffrent refrence name or type. i am trying migrate process template from org to org and i get error.

shiva-gattu avatar Oct 14 '21 07:10 shiva-gattu

@shiva-gattu I am also facing the same error while using the Process-Migrator on different custom field. Any luck or resolution did you find with this?

sonamgit15 avatar Jun 22 '23 14:06 sonamgit15

Just pumped to similar issue when trying to import Process into existing ADO organization.

For me the the problem was with Custom.Owner field that was already defined for other process that already was defined in target ADO organization. As the type definition was similar my work-around was to manually rewrite that part of process definition .json to match the existing type in target ADO organization. After that the import was successful.

Suggested fix:

  • add a process-migrator option that can be used so that process-migration re-uses the existing Custom field definitions in Target ADO organisation if the type definition matches.

  • alternatively have an option to rewrite process definition fields so that overlapping Custom.<Field> fields can be renamed on-the-fly according to some rule set during process import.

eg. field Custom.Owner would be re-written to Custom.MyLovemostOwner for process to be imported ?

juha-ranta avatar Feb 15 '24 11:02 juha-ranta