The connection override works as expected ,I noticed one problematic behavior :
After i override for example BD to BP in production ,BD is also visible in the list of connections
I dont want users to see or use BD in BP,but when trying to change the rights to BD (nobody can view it ) when the reports are opened in Webi there is an error massage : you dont have right for BD connection ,seems like even after the override was done it uses the BD connection and searches for security rights; .
If you’ve set up the override correctly, then your “BD” connection in production will have the production credentials. That is, you should only have one connection in production, named “BD”, which will be pointed at your production database.
i basically only did connection override,I didn’t define BD connection in Prod but i the override settings ,this is why i wonder from start why users can see it from first place
All an override does is change the credentials of a connection when it’s moved from one environment to another. So, when your “BD” connection is migrated from development to production (using Promotion Manager), it will be modified to use the credentials specified in the override. The connection will still have the same name as in the source.
that’s the stage i am trying to understand why is going that why,I only did the override settings but eventually I do see the BD connection new object in Prod system,I guess i’ll have to check the settings again