Workflow Issues. This process cannot be created, updated, or activated because....

(0) Share

Report

Posted on by Community Member

I am trying to build a workflow that fires off using a customized field "Billable" that when equal to yes sends an email. When trying to save the condiftion I get the Error, This process cannot be created, updated, or activated because it was created outside Microsoft Dynamics CRM web application. My organization does not allow this type of process. How do I correct so I can have my customized fields in the forms as part of my conditions in workflows?

*This post is locked for comments

I have the same question (0)

All responses (12)

Answers (1)

Sort by

Verified answer

JBirnbau Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi Garabed,

Are you currently using CRM Online or do you have Update Rollup 12 installed in CRM On-Premise? If so, we have identified an issue with specific types of lookup conditions in workflows that will trigger this error on UR12. A fix is currently being developed, but I would recommend opening a support case if the above criteria matches your environment in order to increase visibility on the issue.

Was this reply helpful? Yes No
Brittany Tripp 5 on at

Like (0)

Report
Copy link

Link copied!

Does this same issue still exist in Roll Up 13?

Do you have an estimate for when it will be fixed?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Brittany,

I will let you know once I install it in a few days.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Good News

I installed Roll UP 13 and am now able to trigger workflows off of customized fields.

Was this reply helpful? Yes No
Suggested answer

Farhan Syed 1,156 on at

Like (0)

Report
Copy link

Link copied!

Hi BRITTANY TRIPP,

If you are facing this case in RU 13 then you are not alone.

I faced this while editing an existing workflow ( changing the condition block and then trying to save which the system didnt allow) developed on the same on premise environment on RU13.

The solution was not to create a new workflow with the same conditions but to delete the condition block (irrespective of the custom or system fields) and recreate it with the same conditions and save it (which the system will allow)

Was this reply helpful? Yes No
ErinNickelsburg 5 on at

Like (0)

Report
Copy link

Link copied!

This was an issue with RU12 that was not fixed in RU13. Do we know if it was addressed in RU14?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Does anyone know if this is resolved in Rollup 14 or 15??? We have a client experiencing the same issue.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi Kristen,

It was resolved for me in RU13.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

We are on rollup 13 and have a client with this issue so obviously it is not resolved for us. Thanks.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi,

I have just struck this issue with Microsoft CRM2013 Online product. If you delete the conditional check block and re-create it with your new check condition the WF will save. It seems to be editing that is the issue.

This is frustrating if the condition is the start of your WF!

Thanks

Was this reply helpful? Yes No