Hi,
I create an example for you https://github.com/realLiangshiwei/AbpQa274.
You can see that after create the user, change the user object again.
You have three options:
IdentityUserAppService
, update the user at the end of the method.DisplayName
parameter in the create user request. see https://github.com/abpframework/abp/issues/4467.OK, I will check it.
Have a ncie day.
Hi,
Example : https://github.com/realLiangshiwei/AbpQa263Demo
hostUser
will not be displayed in the user listhostPermission
will not be displayed in the permisson groupDemoAppService
, users of all tenants can be update.Note: This is not a best practice and not complete, it just provides an idea
I know you use the Migrator app, but this does not seem to be a problem with abp. The problem is with your database server.
I mean if you use other database server, will get this problem? .
Did you try use Microsft SqlServer Management Studio to connection database server?.
Can you provide steps to reproduce? I will try reproduce your problem locally , Thanks.
Hi:
host
user , but if you want hidden from the tenant in the user list, you need use object extend system add an identifier (like: IsHostUser
) to IdentityUser
entity and override IdentityUserAppService
to filter IsHostUser
.IsHostPermisson
) to the Properties
property of PermissionDefinition
.ICurrentTenant.Change(null)
to switch to the host , and then you can get all tenants.If I have an incorrect understanding, please let me know. I will try to create an simple example for 1,2,3.
Have a nice day : ).
Hi, ABP uses the unit of work system to save changes after the method returns, but you can save changes manually:
Try :
try
{
//......
await _myRepository.UpdateAsync(myEntity);
await CurrentUnitOfWork.SaveChangesAsync();
}
catch(DbUpdateConcurrencyException ex)
{
// handle exception
}
See Unit of Work Document learn more about unit of work system.
Hi,
I can't reproduce your problem, If you use other database server, will this problem occur?
Hi
Please See https://stackoverflow.com/questions/17650482/instance-failure-error-while-connection-string-is-correct Does the solution here work for you?