@ninomartini , thanks for your feedback. it'll be fixed in the next release.
closing the issue, you can always reopen if you need help on the same issue.
closing the issue, you can reopen if you need help again.
for the shared entities like Vehicles; don't add IMultiTenant interface. if you are joining a MultiTenant entity with Non-MultiTenant entity you can disable MultiTenancy for that particular query.
public async Task<long> GetOnSaleVehiclesCountAsync()
{
using (_dataFilter.Disable<IMultiTenant>())
{
// some query with multitenant entities included.
}
}
https://docs.abp.io/en/abp/latest/Multi-Tenancy#data-filtering-disable-the-multi-tenancy-filter
1- see this document https://docs.abp.io/en/abp/latest/Entity-Framework-Core-Other-DBMS 2- also I advice you to update your project to v3.2.1
actually there's no practical way of this :(
the only way is removing the [Authorize]
attribute from Application Services.
If you want to guard some specific Web API actions, you can also put the [Authorize]
attribute to your service methods .
@talha in the new version (v3.2.X) there shouldn't be files under %UserProfile%\.abp\suite\solutions\{solution-id}\entities\
.
So the new location for entity files are in your solution folder. This is done because we wanted to include entity json files to the source-code system.
Find your entities in your-solution-root-direcroty\.suite\entities