16

I wanted to add an "Update Records" action in a process and set a new checkbox field to true which I created just before. However, even after reloading process builder the field is not available in the list of fields to update... is the list cached somewhere or am I missing something obvious?

2
  • 1
    Per success.salesforce.com/answers?id=90630000000CtdgAAC, check that the Field Security is set. Commented Nov 25, 2019 at 17:29
  • 1
    @JohnnyStenson I won't remove that commet as it could be of use to someone, but the actual answer was Shannon's which I accepted nearly 5 years ago! I just got confused by the UI at the time.
    – Matt Lacey
    Commented Nov 26, 2019 at 1:19

2 Answers 2

20

I tried this and saw my checkbox field no problem, so I'm going to hazard a guess that you have fallen into the "Select a Field" overlay trap. Which is this:

When you click on the "Object" field and it gives you the "Select a Field" overlay, it's REALLY asking you to select an object, not a field. So it gives you a list of lookup fields to navigate to a related object.

If you click on the object name, and click save, it will then give you a list of fields on that object that you can update.

enter image description here

enter image description here

enter image description here

4
  • 2
    Wow, that is exactly what I did. Time to go pester the UI team methinks ;)
    – Matt Lacey
    Commented Mar 17, 2015 at 1:41
  • 2
    They are already aware of it. I did exactly the same thing a couple weeks ago, and I only have to walk 3 aisles over ;-) Commented Mar 17, 2015 at 1:42
  • Could you go pester them again please - I just wasted 5 minutes of my life on the same issue :-)
    – MikeA
    Commented Jan 28, 2016 at 12:16
  • This helped me when I got stuck in Lightning super badge. It was actually confusing in Process builder. Thanks. Commented Nov 2, 2017 at 1:00
1

I have had a problem with editing a process where the field was not showing in the process builder.

The problem was because the process was created whilst the field was 'not required', then the field was made 'required'. The process needed updating to set the value which then wasn't available.

The solution was to make the field 'not required', update the process, then set the field back to required.

btw: if the field is required and a new process created to create/update an object then the field is pre-loaded into the form and a value must be given.

1
  • This worked for me :-D Commented Aug 20, 2020 at 8:48

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .