So I searched for a workaround… and I found one! Here’s how you do it: It was pretty obvious neither of the solutions above were viable in my situation. I needed to update the currency field of the campaign entity, which is read-only in the workflow designer. We didn’t have alternative forms and because it was a user owned workflow to be created in a production environment, I couldn’t change the behavior of the field and perform a publish. Go to your Form customizations, uncheck Field is read-only, publish, go back to your workflow, update your workflow, go back to your form and set the field read-only again… ouch!!.Since the workflow designer uses your ‘Sticky’ Form, you will then be able to update the field. Switch between forms and choose a form that does not have the field, or has the field as editable. ![]() ![]() To work around this issue you’re left with a few options: Have you ever encountered having to update a field in a workflow only to realize that the field is read-only on the form and therefore also read-only in your workflow designer?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |