Process Builder Record Update action can produce unexpected results when filtered on certain ID fields
Trailblazer Community

Known Issues · Fixed

Process Builder Record Update action can produce unexpected results when filtered on certain ID fields

Process Builder

Last updated 2017-04-14 ·Reference W-3241359 ·Reported By 2 users

Fixed - Winter '17

Summary
In Process Builder User Interface, we add an implicit filter to the underlying Flow Record Update action to fetch the relevant record to update.

eg. If the Record Update action updates the triggering Account record ( [Account] ), we add an implicit filter: [Account].Id Equals myCurrentVariable.Id

The Flow filter engine converts 2 or more filters with the same left hand side and the equals operator to an OR comparison

Thus if another filter is added to the action based on the same Id field (like [Account].Id Equals <somehardcodedId>) the result would be an update to both records based on the OR logic.



NOTE: This behavior has been partially addressed by hiding Id as an available field for filtering record updates. However, it has been discovered that this prevents selection of Id in some scenarios where that selection would be valid, and that the fix does not address certain scenarios (specifically when a Process Record Update is updating child records). This is under review.

Repro
** NOTE: This repro scenario is no longer possible as of Summer '16 **

1. Create a Process on Account (for example).

- Can run on Create or Create and edit; Doesn't matter
- Criteria can be anything (or nothing); Doesn't matter

2. Add an "Update Records" action.

a) Select "Select the Account record that started your process"
b) Select "Updated records meet all conditions"
c) Add a condition based on "Id", like "Account Id equals <some 18 character Account Record Id>"
d) Set the action to update some Account field.

3. Trigger the Process. Note that this causes an update to both the Account where the Process was triggered AND the account given in the filter added in 2c above.

Workaround
a) avoid adding filter conditions to a Process Builder Record Update based on the same Id field which the update itself is based on.

b) If trying to update child records and filter that record update by Id (currently not an option due to the partial fix already implemented for this issue), use a Flow to perform the desired record update action.

Reported By (2)

George Weilenmann Bill Florio

Is it Fixed?

AP0 AP3 AP4 AP5 AP6 AP7 AP8 AP9 AP10 AP11 AP12 AP13 AP14 AP15 AP16 AP17 AP18 AP19 AP20 AP21 AP22 AP24 AP25 AP26 AP27 AP28 AUS14S AUS18S AUS16S AUS13 AUS11 AUS1 AUS28S AUS20S AUS27 AUS26S AUS25 AUS24S AUS23 AUS22S AUS2S AUS36S AUS38S AUS3 AUS4S AUS47 AUS43 AUS5 AUS58 AUS6S AUS64 AUS62 AUS60 AUS7 AUS77 AUS75 AUS9 BRA1 BRA2S BRA3 BRA4S BRA5 BRA6S BRA8S CAN1 CAN17 CAN11 CAN25 CAN2S CAN20S CAN29 CAN28 CAN27 CAN26 CAN34 CAN4S CAN6S CAN8S CS1 CS2 CS4 CS5 CS6 CS100 CS109 CS108 CS107 CS106 CS105 CS102 CS101 CS115 CS119 CS110 CS117 CS114 CS113 CS112 CS111 CS116 CS123 CS122 CS121 CS126 CS127 CS129 CS128 CS125 CS124 CS137 CS138 CS133 CS132 CS14 CS148 CS142 CS159 CS152 CS151 CS15 CS162 CS167 CS166 CS169 CS165 CS160 CS173 CS17 CS172 CS170 CS171 CS174 CS189 CS194 CS192 CS193 CS190 CS191 CS199 CS197 CS198 CS196 CS195 CS203 CS209 CS200 CS202 CS201 CS210 CS219 CS218 CS217 CS216 CS215 CS214 CS213 CS212 CS211 CS22 CS220 CS226 CS224 CS222 CS225 CS223 CS221 CS237 CS234 CS238 CS239 CS236 CS24 CS242 CS248 CS247 CS241 CS245 CS244 CS243 CS249 CS246 CS240 CS252 CS259 CS257 CS256 CS255 CS254 CS250 CS258 CS253 CS251 CS263 CS265 CS268 CS267 CS266 CS269 CS262 CS261 CS260 CS264 CS27 CS271 CS270 CS28 CS29 CS308 CS31 CS32 CS33 CS34 CS35 CS364 CS36 CS365 CS37 CS40 CS41 CS42 CS43 CS44 CS45 CS57 CS58 CS59 CS60 CS61 CS62 CS63 CS67 CS72 CS73 CS74 CS75 CS76 CS77 CS80 CS81 CS84 CS86 CS87 CS88 CS89 CS98 CS99 DEU10S DEU13 DEU11 DEU1 DEU16S DEU14S DEU12S DEU2S DEU20S DEU25 DEU36 DEU3 DEU38 DEU46 DEU4S DEU48S DEU5 DEU52 DEU50S DEU6S DEU8S EU16 EU17 EU18 EU19 EU25 EU26 EU27 EU28 EU29 EU30 EU31 EU32 EU33 EU34 EU35 EU36 EU37 EU38 EU39 EU40 EU41 EU42 EU43 EU44 EU45 EU46 EU47 EU48 FRA12S FRA19 FRA1 FRA11 FRA24S FRA2S FRA32 FRA36 FRA34 FRA4S FRA5 FRA6S FRA7 FRA8S FRA9 GBR1 GBR2S GBR4S IND14S IND17 IND19 IND18S IND16S IND15 IND13 IND11 IND1 IND12S IND10S IND20S IND27 IND25 IND21 IND23 IND2S IND28S IND26S IND24S IND22S IND37 IND3S IND39 IND41 IND47 IND4S IND43 IND54S IND5 IND6S IND7 IND8S IND9 JPN18S JPN12S JPN10S JPN1 JPN19 JPN17 JPN20S JPN2S JPN21 JPN28S JPN24S JPN22S JPN3 JPN4S JPN5 JPN6S JPN7 JPN8S KOR1 KOR2S KOR4S NA104 NA107 NA109 NA100 NA101 NA103 NA102 NA105 NA119 NA116 NA110 NA118 NA112 NA111 NA115 NA114 NA113 NA117 NA125 NA124 NA122 NA120 NA126 NA127 NA123 NA129 NA121 NA128 NA138 NA134 NA133 NA136 NA135 NA132 NA131 NA130 NA137 NA139 NA140 NA142 NA141 NA149 NA146 NA147 NA148 NA154 NA158 NA159 NA153 NA151 NA155 NA152 NA150 NA156 NA161 NA163 NA167 NA160 NA166 NA165 NA169 NA164 NA168 NA162 NA172 NA170 NA174 NA171 NA173 NA196 NA207 NA204 NA206 NA208 NA209 NA21 NA218 NA214 NA217 NA215 NA211 NA212 NA213 NA210 NA223 NA226 NA224 NA225 NA70 NA71 NA75 NA80 NA81 NA82 NA83 NA84 NA85 NA89 NA90 NA91 NA92 NA93 NA94 NA95 NA96 NA97 NA98 NA99 SGP10 SGP1 SGP2S SGP3 SGP4S SGP6S SGP8S SWE1 SWE2S SWE4S UM1 UM2 UM3 UM4 UM5 UM6 UM7 UM8 UM9 USA194S USA13 USA198S USA196S USA1 USA19 USA17 USA15 USA20S USA26 USA28S USA2S USA222S USA220 USA22S USA3S USA32S USA30S USA36 USA34 USA59 USA60S USA61 USA62S USA7 USA8S

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.