<?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>DataSource Naming Best Practice Info</title><link>https://community.appian.com/discussions/f/best-practices/27867/datasource-naming-best-practice-info</link><description>What is the best practice for naming a datasource in Appian? 
 
 In DEV, UAT, PROD can what should be the name of datasource be provided?</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: DataSource Naming Best Practice Info</title><link>https://community.appian.com/thread/108498?ContentTypeID=1</link><pubDate>Fri, 24 Feb 2023 21:46:53 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:02c22920-722a-4bbf-8bd0-a22bc2ad93bc</guid><dc:creator>simranj0886</dc:creator><description>&lt;p&gt;&amp;nbsp;&lt;a href="/members/peter.lewis"&gt;Peter Lewis&lt;/a&gt;&amp;nbsp;I really appreciate your quick guidance on the same! Thank you!&amp;nbsp;&lt;span class="emoticon" data-url="https://community.appian.com/cfs-file/__key/system/emoji/1f603.svg" title="Smiley"&gt;&amp;#x1f603;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DataSource Naming Best Practice Info</title><link>https://community.appian.com/thread/108497?ContentTypeID=1</link><pubDate>Fri, 24 Feb 2023 21:43:58 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:16a28ec0-7a5e-4c05-a204-a796ab6bc756</guid><dc:creator>simranj0886</dc:creator><description>&lt;p&gt;I agree, however I see the administrators have set up the datasource name different in all the environments, hence looking out for the formal documentation available on the best practice/impact, if any.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DataSource Naming Best Practice Info</title><link>https://community.appian.com/thread/108496?ContentTypeID=1</link><pubDate>Fri, 24 Feb 2023 21:43:48 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:f73eb87a-4105-4d62-8238-889aaa6e1aa7</guid><dc:creator>Peter Lewis</dc:creator><description>&lt;p&gt;Sure, we document that right here:&amp;nbsp;&lt;a href="https://docs.appian.com/suite/help/latest/Appian_Administration_Console.html#data-sources"&gt;https://docs.appian.com/suite/help/latest/Appian_Administration_Console.html#data-sources&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The key phrase is: &amp;quot;If you are using multiple environments, a data source with the same name must be created in each environment.&amp;quot;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DataSource Naming Best Practice Info</title><link>https://community.appian.com/thread/108495?ContentTypeID=1</link><pubDate>Fri, 24 Feb 2023 21:42:20 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:12561dbe-9954-4902-b10e-aafe41ff6388</guid><dc:creator>Abhay Dalsaniya</dc:creator><description>&lt;p&gt;The object name should be same on different environments. Why you need different name based on the environment?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DataSource Naming Best Practice Info</title><link>https://community.appian.com/thread/108494?ContentTypeID=1</link><pubDate>Fri, 24 Feb 2023 21:42:13 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:3f1a431c-d717-44c5-aaca-1a78451d77bf</guid><dc:creator>simranj0886</dc:creator><description>&lt;p&gt;Dear &lt;a href="/members/peter.lewis"&gt;Peter Lewis&lt;/a&gt; Thank you for your input. I would really appreciate if you can help me in pointing out any documentation for the same?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DataSource Naming Best Practice Info</title><link>https://community.appian.com/thread/108492?ContentTypeID=1</link><pubDate>Fri, 24 Feb 2023 21:37:43 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:5b8a1321-a78c-42bf-9a8c-a695aa7f5c76</guid><dc:creator>Peter Lewis</dc:creator><description>&lt;p&gt;I&amp;#39;d recommend keeping the same name for the database in each of your environments. It&amp;#39;s already implied that it will go against the dev/uat/prod version of those, so naming it more about the business purpose (e.g. Case Management DB) will generally be easier to work with.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DataSource Naming Best Practice Info</title><link>https://community.appian.com/thread/108489?ContentTypeID=1</link><pubDate>Fri, 24 Feb 2023 20:41:22 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6d265304-fc8e-4e1c-aab2-851cddb295e9</guid><dc:creator>simranj0886</dc:creator><description>&lt;p&gt;Thank you&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;a href="/members/kaushikm0002"&gt;kaushikmg&lt;/a&gt;&amp;nbsp;my concern is related specific to the data source naming conventions.&lt;/p&gt;
&lt;p&gt;For e.g. Appian DEV has a datasource configured with name as &amp;quot;sample-dev-db01&amp;quot; where as the datasource name in Appian UAT is configured as &amp;quot;sample-uat-db01&amp;quot; due to which every time the deployment is happening the datastore entity need to be added manually and then all the&amp;nbsp;constants pointing to the datastoreEntity&amp;nbsp;need to updated manually!&lt;/p&gt;
&lt;p&gt;Hence I want a guideline on the datasource configuration in different environments and what&amp;nbsp;is the Appian Best Practice? I couldn&amp;#39;t find in any of the best practices/standards shared by Appian.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DataSource Naming Best Practice Info</title><link>https://community.appian.com/thread/108412?ContentTypeID=1</link><pubDate>Fri, 24 Feb 2023 02:21:52 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:820afd49-9c24-4ce0-9d1b-b0afa6288ae5</guid><dc:creator>kaushikmg</dc:creator><description>&lt;p&gt;Best practice for naming all the objects is defined here - &lt;a href="https://docs.appian.com/suite/help/22.4/Standard_Object_Names.html#overview"&gt;Standard Object Names - Appian 22.4&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DataSource Naming Best Practice Info</title><link>https://community.appian.com/thread/108409?ContentTypeID=1</link><pubDate>Fri, 24 Feb 2023 02:08:03 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:ec0a8c20-4307-42ed-ba85-f6078ee077d6</guid><dc:creator>Abhay Dalsaniya</dc:creator><description>&lt;p&gt;&lt;span&gt;This page provides standard&amp;nbsp;&lt;/span&gt;&lt;a href="https://docs.appian.com/suite/help/22.4/design-objects.html"&gt;Appian design objects&lt;/a&gt;&lt;span&gt;&amp;nbsp;and object property naming conventions that you can adapt to your environment and organizational guidelines as needed.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>