<?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>What Happens When Deploying a Constant That Already Exists in Test?</title><link>https://community.appian.com/discussions/f/general/40016/what-happens-when-deploying-a-constant-that-already-exists-in-test</link><description>In the Test environment, suppose a constant named PV_TXT_TEST already exists. Now, if I create a new constant in the development environment with the same name (PV_TXT_TEST) and deploy it to the Test environment, what will actually happen during deployment</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: What Happens When Deploying a Constant That Already Exists in Test?</title><link>https://community.appian.com/thread/152772?ContentTypeID=1</link><pubDate>Fri, 12 Dec 2025 02:13:30 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:177f5fe6-3083-4f7e-9b4e-96c250832bd6</guid><dc:creator>Basheer Ahmed</dc:creator><description>&lt;p&gt;Hi Pooja,&amp;nbsp;&lt;br /&gt;From my understanding, we can deploy the constant, but during deployment, the status of that constant object will be displayed as &lt;em&gt;&amp;quot;Conflict Detected&amp;quot;.&lt;/em&gt; But, &lt;strong&gt;yes, we can deploy the constant without any errors.&lt;/strong&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What Happens When Deploying a Constant That Already Exists in Test?</title><link>https://community.appian.com/thread/152759?ContentTypeID=1</link><pubDate>Thu, 11 Dec 2025 14:00:50 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:7b7694a5-bdd2-432c-96f1-e4bf903aa447</guid><dc:creator>Mike Schmitt</dc:creator><description>&lt;p&gt;The deployment will throw an error similar to &amp;quot;name insufficiently unique&amp;quot;.&amp;nbsp; 7 or 8 years ago we had no ability to rename constants using any supported functionality, so overcoming this when it happened by accident was a giant pain.&amp;nbsp; These days it&amp;#39;s a 2-second fix, thankfully.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>