Thanks :)
An example maybe? Where does that show? Thanks
But I don't need that filter for the reference data stored on Host.
So if I am doing a query that combines both data from host and Tenant 1, then knowing how IMayHaveTenant is removed, there won't be any WHERE clause to filter on Tenant for entities that don't implement that interface, only WHERE clause filter applies for entities with IMustHaveTenant.
I tried it and it works.
Thanks
That is correct if I am using ng-options to bind elements, but in my case I am just looping over items.
Check App/common/views/languages/texts.cshtml
Thanks Ismail.
SettingsManger calls SettingsStore to persist data into DB.
Who calls SettingsManager to persist? Where in time does this happen?
Thanks
So basically the problem is having that IMayHaveTenant filter, correct? In my case, I want to bring them and do joins to those tables irrespective of the tenant.
So removing the IMustHaveTenant filter should solve the issue here?
Thanks
Here you go:
public virtual IQueryable<Shelter> Shelters { get { return _repository.GetAll(); } }
Sure, I will check it and get back to you. Many thanks
Ah, I thought all such exceptions are handled and sent back to client.
When an error happens at server, how is the client informed in this case? I thought it was handling that interface. Can you please guide me through the code to see where is the framework handling errors and sending them to client (Popup message).
Thanks