I have a workflow step that's locking Field1 before record load. Field2 is a drop-down list. I have an After Field Edit step triggering on selection of a value in Field2 that's supposed to either unlock Field1 or do nothing to Field1 (ie leave it locked) based on the selection of Field2. It doesn't work and I suspect it's because the After Field Edit step can't "override" the step that's locking it on Before Record Load. I did figure out a work-around, but it's clunky and inefficient so I was hoping there was a more efficient way.
RJMNS
06/09/2023, 6:23 PM
The work-around was basically to not lock the field on Record Load, but to lock it on setting of Field2 unless the one value is chosen that leaves it open.
Because Field1 should be blank unless the certain value is chosen in Field2, I also had to add a step to wipe out the value in Field1 unless the "unlocking" value is chosen in Field2.
m
MGBC
06/09/2023, 6:28 PM
Try locking the field on Before User Edit instead of Before record load
MGBC
06/09/2023, 6:30 PM
also if it's a custom field and you've set the display type to Disabled on the field settings when making it, I've seen that cause trouble with using the field display type actions in workflows
MGBC
06/09/2023, 6:30 PM
make sure that is set to normal on the feild settings AND on the custom form
r
RJMNS
06/09/2023, 8:10 PM
Thanks @MGBC I'll give that a shot
k
KevinJ of Kansas
06/09/2023, 8:44 PM
In the past, I've done this by having triggering fields include other mandatory fields and not necessarily the one that I want to have drive it just because I can ensure that it does in fact get triggered
KevinJ of Kansas
06/09/2023, 8:44 PM
Doesn't hurt to have it triggered more than once as long as your criteria is good on the action