<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>dynamic object manipulation</title><link>https://community.appian.com/discussions/f/plug-ins/39735/dynamic-object-manipulation</link><description>I need to check if a function exists and then call it, using its name as a reference for both operations. I know that the functions doesruleexist and rulereferencebyname exist, but I don&amp;#39;t know which plugin they belong to or if there is an alternative</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: dynamic object manipulation</title><link>https://community.appian.com/thread/151602?ContentTypeID=1</link><pubDate>Wed, 17 Sep 2025 16:41:46 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:8a29b502-20e4-484a-80a4-f3c8d6a36086</guid><dc:creator>Jesse Knight</dc:creator><description>&lt;p&gt;From a governance perspective, it isn&amp;#39;t a good idea to use an unsupported plugin (or undocumented function, like &lt;code&gt;eval&lt;/code&gt;) in production. Any Appian upgrade or plugin change could break your code without warning and without a way to revert. So be very careful with this plugin in production.&lt;/p&gt;
&lt;p&gt;From the plugin&amp;#39;s description:&lt;br /&gt;&lt;em&gt;None of the functions or smart services in this plugin should be used for any other purpose, nor are they verified to work outside of their usage in Appian-built solutions and the Solutions Customization Suite.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;With that said, there are some excellent test-related use cases for it in lower environments.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: dynamic object manipulation</title><link>https://community.appian.com/thread/151593?ContentTypeID=1</link><pubDate>Wed, 17 Sep 2025 13:11:18 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:ba2d9871-ebb1-4f9f-8d90-4cdd238beb9b</guid><dc:creator>Mike Schmitt</dc:creator><description>[quote userid="299046" url="~/discussions/f/plug-ins/39735/dynamic-object-manipulation/151584"]Stick with choose()[/quote]
&lt;p&gt;FWIW,&amp;nbsp;&lt;em&gt;choose()&lt;/em&gt; has been completely and utterly replaced by &lt;strong&gt;&lt;em&gt;a!match()&lt;/em&gt;&lt;/strong&gt;.&amp;nbsp; I know of zero use cases where it&amp;#39;s still necessary to use &lt;em&gt;choose()&lt;/em&gt; instead of the newer, more flexible, and safer, &lt;em&gt;a!match()&lt;/em&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: dynamic object manipulation</title><link>https://community.appian.com/thread/151584?ContentTypeID=1</link><pubDate>Wed, 17 Sep 2025 08:59:00 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c29b09f7-3659-4b8a-b12d-87bbe9ac9b4a</guid><dc:creator>Shubham Aware</dc:creator><description>&lt;p&gt;Recommendation -&amp;gt; Use the plugin approach for 15+ validation rules with frequent additions and standard input/output contracts. Stick with choose() for fewer than 10-15 validation types where you need explicit visibility of all options, easier debugging, and strict governance compliance.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: dynamic object manipulation</title><link>https://community.appian.com/thread/151583?ContentTypeID=1</link><pubDate>Wed, 17 Sep 2025 08:54:43 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:77659b56-5613-4302-a0b0-450c1dac391e</guid><dc:creator>iluvatar</dc:creator><description>&lt;p&gt;Yesss,&amp;nbsp;This is it, thank you very much.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: dynamic object manipulation</title><link>https://community.appian.com/thread/151582?ContentTypeID=1</link><pubDate>Wed, 17 Sep 2025 08:52:15 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:09003fa5-2278-4ab5-b28e-e34f57260fcb</guid><dc:creator>Shubham Aware</dc:creator><description>&lt;p&gt;Got you!&lt;br /&gt;&lt;span&gt;doesruleexist and rulereferencebyname this functions are part of&amp;nbsp;&lt;a href="/b/appmarket/posts/appian-solutions-plug-in"&gt;Appian Solutions Plug-in&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: dynamic object manipulation</title><link>https://community.appian.com/thread/151580?ContentTypeID=1</link><pubDate>Wed, 17 Sep 2025 08:38:00 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:2300cdf3-abae-4264-9420-460f4e488242</guid><dc:creator>iluvatar</dc:creator><description>&lt;p&gt;I have a long list of rules that have the same functionality: validating certain data as appropriate. Instead of using a huge choose(), I want to rely on this plugin that I know exists and ask if the name of the rule exists to execute the rule, since they all return the same structure and receive the same parameters. The issue is in the intermediate rule, where the choose is located.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: dynamic object manipulation</title><link>https://community.appian.com/thread/151579?ContentTypeID=1</link><pubDate>Wed, 17 Sep 2025 08:34:29 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:e42d009f-5c29-4265-949a-f745aa63f7ae</guid><dc:creator>Shubham Aware</dc:creator><description>&lt;p&gt;May i know your use case to understand better?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>