https://community.appian.com/discussions/f/general/20989/interface-should-be-a-ruleI just ran accross an interface that throws errors when I try to test it. I noticed that it is running a!queryEntity so it should be an expression rule. Is there an easy way to change it from an interface to an expression rule?en-USTelligent Community 12https://community.appian.com/thread/81747?ContentTypeID=1Mon, 17 May 2021 21:13:17 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b69c9eb3-4ddd-4f90-8da5-86d4b5a02322helmuta0001<p>I was afraid of that.&nbsp; Thank you!</p><div style="clear:both;"></div>https://community.appian.com/thread/81740?ContentTypeID=1Mon, 17 May 2021 19:40:39 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:1cbece49-a732-41ce-9fa2-d7f0cfcc7b45Mike Schmitt<p>We could use a bit more info here.&nbsp; What are the errors?&nbsp; What makes you think it should be an expression rule just because it&#39;s running an <em>a!queryEntity()</em>?&nbsp; The real determination for this would be whether the main result of the evaluated expression is a visual element such as a component or form element (form layout, section, box, etc, or any single input component or array thereof).</p> <p>If it really does need to be an expression rule, the simplest (and probably only) solution is to copy the code into a new expression rule editor and save it there instead.&nbsp; There&#39;s no direct or supported way to change interfaces to expression rules or vice versa.</p><div style="clear:both;"></div>