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?
Discussion posts and replies are publicly visible
Thank you kaushikmg my concern is related specific to the data source naming conventions.
For e.g. Appian DEV has a datasource configured with name as "sample-dev-db01" where as the datasource name in Appian UAT is configured as "sample-uat-db01" due to which every time the deployment is happening the datastore entity need to be added manually and then all the constants pointing to the datastoreEntity need to updated manually!
Hence I want a guideline on the datasource configuration in different environments and what is the Appian Best Practice? I couldn't find in any of the best practices/standards shared by Appian.
I'd recommend keeping the same name for the database in each of your environments. It'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.
Dear Peter Lewis Thank you for your input. I would really appreciate if you can help me in pointing out any documentation for the same?
The object name should be same on different environments. Why you need different name based on the environment?
Sure, we document that right here: https://docs.appian.com/suite/help/latest/Appian_Administration_Console.html#data-sources
The key phrase is: "If you are using multiple environments, a data source with the same name must be created in each environment."
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.
Peter Lewis I really appreciate your quick guidance on the same! Thank you!