https://community.appian.com/discussions/f/best-practices/19316/reminder-don-t-use-load-in-expression-rulesIn this post-19.2 world, I&#39;m hoping this will be less and less of an issue. But I continue seeing it, and even today I experienced a weird and unexpected issue that was traced down to some previous developer having used load() within an expression ruleen-USTelligent Community 12https://community.appian.com/thread/75719?ContentTypeID=1Fri, 31 Jul 2020 05:41:38 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:9dffc136-ede5-4d0f-b04e-0f42f2950998Stefan Helzle<p>Mike, thanks a lot. We made this part of our peer review checklist a while ago.&nbsp;While training and coaching all of our Appian Designers using load() and with() in a correct way always was difficult.</p><div style="clear:both;"></div>https://community.appian.com/thread/75716?ContentTypeID=1Thu, 30 Jul 2020 21:13:33 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:7efa51df-5542-4efc-9932-a99f304d7689martincamacho<p>I had the same issue a few weeks ago and spent around 2 hours to figure out what was happening, using a!localVaribales is a great solution because does not impact on the original expression rule behavior!</p> <p>Thanks for bring it up, I will add it to my topics of waring for my coworkers and students.</p><div style="clear:both;"></div>