+4For one user, SQLExecutor is correctly changing to connect to DEVSQL\\High at run-time. For another user, the default parameters specified in the SQLExecutor (QASQL\\High as shown above) are being used. What user configuration setting needs to change in order to correctly grab the same database as user #1 is getting?
+2Hi @ravibansal,
One thing I would confirm, is whether the user is running from the latest feature cache or if they are re-running the entire workspace. It sounds like they might have feature caching enabled and they are viewing the data from the previous connection because it has been cached.
+4Hi @ravibansal,
One thing I would confirm, is whether the user is running from the latest feature cache or if they are re-running the entire workspace. It sounds like they might have feature caching enabled and they are viewing the data from the previous connection because it has been cached.
Hi @chrisatsafe, Both users, (logging into the server from their respective accounts) are running the Entire Workspace (feature caching is disabled).
+2Hi @chrisatsafe, Both users, (logging into the server from their respective accounts) are running the Entire Workspace (feature caching is disabled).
Hi @ravibansal,
Ok you should just need to create a user parameter for the connection then: https://www.screencast.com/t/aJQRXWhtuO
Since you are going between users, it's likely best to use a shared database connection otherwise they both need to have the 2 connection names exactly the same.
Hope that helps
