From 56dda15518490cea126c62ede625fb9eb1d6479b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Halil=20=C4=B0brahim=20Kalkan?= Date: Sun, 27 Jul 2025 21:04:01 +0300 Subject: [PATCH] Fix image path --- .../2025-07-26-Separate-Tenant-Schema/POST.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/POST.md b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/POST.md index 0f473e9999..5567b42aad 100644 --- a/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/POST.md +++ b/docs/en/Community-Articles/2025-07-26-Separate-Tenant-Schema/POST.md @@ -428,7 +428,7 @@ Finally, we came to the point that we will create a new tenant with a separate, Just fill these information as you wish, then open the *Database connection strings* tab: -![new-tenant-dialog-conn-string-2](D:\Github\abp\docs\en\Community-Articles\2025-07-26-Separate-Tenant-Schema\new-tenant-dialog-conn-string-2.png) +![new-tenant-dialog-conn-string-2](new-tenant-dialog-conn-string-2.png) Uncheck the *Use the shared database* option and set a connection string to the *Default connection string* for this tenant. I used `Server=(LocalDb)\MSSQLLocalDB;Database=MtDemoApp_Volosoft;Trusted_Connection=True;TrustServerCertificate=true` as the connection string value. The database name is `MtDemoApp_Volosoft`. You can Test the connection string to be sure that it is a valid connection string.