tag:blogger.com,1999:blog-6215355853745600041.post8896240230864357641..comments2023-06-29T06:30:57.142-07:00Comments on A Devotee of Dynamics CRM: Dynamics CRM 2011 – Be careful while setting up an owner of workflow in production environmentsAnkit Shahhttp://www.blogger.com/profile/02231940860065519189noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-6215355853745600041.post-44428243331120920832014-05-19T00:19:31.511-07:002014-05-19T00:19:31.511-07:00Hello Bujji Babu, Did you try to export the proces...Hello Bujji Babu, Did you try to export the process and check the customisation? If the exported customisation has the owner field then from there it can also be changed and re-imported. I did not do it before but just thought for such workaround.Ankit Shahhttps://www.blogger.com/profile/02231940860065519189noreply@blogger.comtag:blogger.com,1999:blog-6215355853745600041.post-5740084372692583582014-05-14T00:11:46.202-07:002014-05-14T00:11:46.202-07:00Hello Ankith,
I have the System Administrative pr...Hello Ankith,<br /><br />I have the System Administrative privilege in the CRM. I need to change the owner of the workflows that are belongs to other account (that owner no more but account is enabled still). When I am trying to change the owner of that workflows I am getting the error message ie "Processor Error" (This process cannot be activated or deactivated by someone who is not its owner). I don't have that account log in credentials log into CRM and change. Please tell me any other options to change the owner of those workflows.<br /><br /><br />Anonymoushttps://www.blogger.com/profile/00031274109968174642noreply@blogger.comtag:blogger.com,1999:blog-6215355853745600041.post-69192565907637713362013-04-30T06:21:35.894-07:002013-04-30T06:21:35.894-07:00I agree,we do the same thing. On top of it, if we ...I agree,we do the same thing. On top of it, if we are using queues in our workflow then we create the queues with same GUIDs in all environments.Anonymoushttps://www.blogger.com/profile/04193418105246403607noreply@blogger.comtag:blogger.com,1999:blog-6215355853745600041.post-68283086751174973062013-04-28T22:39:38.588-07:002013-04-28T22:39:38.588-07:00Hello Parvez,
Yes, the scope of workflow was orga...Hello Parvez,<br /><br />Yes, the scope of workflow was organization level(Global = 4).Ankit Shahhttps://www.blogger.com/profile/02231940860065519189noreply@blogger.comtag:blogger.com,1999:blog-6215355853745600041.post-24352614346014757712013-04-28T05:22:50.696-07:002013-04-28T05:22:50.696-07:00One thing that makes this more complicated is that...One thing that makes this more complicated is that not even a sysadmin can modify or update a workflow process that is owned by another user. Therefore if you need to import a new solution package to production that contains any existing workflows, you'll first need to re-assign the processes to yourself, import the solution and the re-assign them back to the business user. Due to these limitations, I usually keep all workflows in a separate solution, so that the need to change their ownership is minimized.Jukka Niiranenhttps://www.blogger.com/profile/01897989666680955589noreply@blogger.comtag:blogger.com,1999:blog-6215355853745600041.post-84949746395186717362013-04-27T08:46:14.624-07:002013-04-27T08:46:14.624-07:00Hi Ankit, just out of curiosity what was the scope...Hi Ankit, just out of curiosity what was the scope of the offending workflow? Just wondering if this would still be a problem with organization scope workflows?Parvez Ghumranoreply@blogger.comtag:blogger.com,1999:blog-6215355853745600041.post-55208223249612472882013-04-27T07:28:11.907-07:002013-04-27T07:28:11.907-07:00If I understood correctly then have you purchased ...If I understood correctly then have you purchased a separate license to run workflows?Ankit Shahhttps://www.blogger.com/profile/02231940860065519189noreply@blogger.comtag:blogger.com,1999:blog-6215355853745600041.post-9925964115465348062013-04-27T06:37:45.523-07:002013-04-27T06:37:45.523-07:00We use user id created specifically for running t...We use user id created specifically for running the workflows. Such user id is not owned by a person, rather the system owns it.Anonymousnoreply@blogger.com