Andrew White

Hi, I think it should be as simple as setting `TenantNotSetMode` to overwrite on your db context.

Thanks for the update. I'm glad you got it working for you but I would like to understand what was going on so let me know if you see anything...

edit: No this will not be closed--sorry about that!

Edit: @robinabganpat beat me to the details above, thanks! Hi, I abstracted setting it behind `IMultiTenantContextSetter`. Take a look in the middle where to see how it can be used:...

I like this change and it fits in with a new strategy I am adding that ‘HttpContextStrategy` that just takes a delegate taking http context and wraps the cast from...

Makes sense. I will prioritize this change. On Jun 26, 2024, at 1:21 AM, robinabganpat ***@***.***> wrote: Although the current checks that return exceptions only make sense in http context...

@tsutomi yes it gets tricky. The `AsyncLocal` based implementation is modeled how `IHttpContextAccessor` works in ASP.NET Core... but obviously that is geared towards their async heavy web server design. There...

Hi, that particular entity is a little different from the others and I'm not sure why. First thing I recommend to try is to set the [TenantNotSetMode](https://www.finbuckle.com/MultiTenant/Docs/v9.0.0/EFCore#tenant-not-set-mode) for your context...

That would have been too easy huh? Hm, are you using the default Identity UI? Do you have the external login page scaffolded out by any chance and if so...

Ok I think I have a solution for you. Create a class: ``` public class TenantDefaultValueGenerator : ValueGenerator { public override string? Next(EntityEntry entry) { return "__tenant__"; } public override...