What version of PowerServer?

Hi Luis;

  FWIW: That is one of the uses of the CacheName parameter in the SQLCA DBParm field is for.

  FYI: https://docs.appeon.com/pb2022r3/connection_reference/CacheName.html

HTH

Regards ..> Chris

2022 R2

I know that Chris, that's how I was able to make the new site and make it point to a different DB. But what now I have two sites

 https://Server address/ic_i26/

https://Server address/ic_i20/

But both generated the shortcut ic_m20 in the client side. even that they are pointing to a different DB, and is because the app name is the same.

"unacceptable under our standard to create a new power server project for each DB and redeploy"

If you are testing the PB part of the code, then you should setup a new project so you can test the new code.  But i think you are wanting to just test out different databases?

if you are just testing some database changes, then why not just setup your login to 'repoint' to the database you want it to use.  You use different db caches for this (the cache names can be created/setup at runtime via the webapis).  Same exact concept as a SAAS deployment where each customer has their own database.  

the big difference is that instead of deciding which icon to click, the user clicks which "database profile" to use after clicking the single icon.  We name our testing databases "TEST" so that users know they are connecting to a test database, and then put up a messagebox that says 'you logged into test'.

We have 14 environments for testing, this is to test different project (changes to the same application pointing to different release) at different time. Not all the project go to prod at the same time and they start at different period of time. So, currently in Appeon 2020 we created a package and we deploy that package to what ever environment we need. We don't recompile the application to deploy the package to a different environment unless is a code change or a rebase from PROD when a release is move to that environment. So, now in 2022 I'm trying to setup the same thing, but my problem is that after I created the package to install the API, WEB and runner in the server, I can install that package in different sites to point to different DB as need, but when the user click in the link the app name is the same even when is pointing to a different environment. So I need my app name to contain the environment name. Your solution does not work to me, because it would be the same code always pointing to different DB. But when I new project is compile and is part of a complete different release I will be stuck with the same issue.

I just found out that if I replace the appconfig.json.zip from another Power Server project with a different appname it will rename the app. So, just to simplified, is there any way to made changes to this file after is deployed? I see that the file is encrypt and I see that we can edit this file using CustomizeDeploy.dll. But I haven't found any doc saying it is possible to change the name of the app.  

If I understand correctly what you want to do, all you need to do is rename the folder on the Web server rather than the app itself or any of the contents of the folders.  For example...

I deploy the demo app to folder called "salesdemo_local" on the Web server.  Then I simply did copy n' paste of the folder and renamed it "salesdemo_test". 

Here you can see under the second folder renamed to "salesdemo_test" the application .EXE is still the same salesdemo_local.exe as the other folder on the Web server. 

Then I launch each of the subfolders with corresponding URL.  For example, http://localhost/salesdemo_local and http://localhsot_salesdemo_test. It creates two shortcuts automatically, and each shortcut points to the right subfolder. 

You could do exact same thing even on different servers, but I just illustrate this example on same server.