Activities of "alper"

I see that the dropdown code is generated but there's problem with the loading. You can check your backend logs to understand the issue.

Maybe database migrations didn't apply well. Can you check if EthinicityId exists on your entity. Also run DbMigrator to ensure all migrations are applied.

if these won't work, send me your both entity.json files (ethinicity and main entity)

@unlonlyness did you add the source-code of Volo.Account.Pro module to your module?

it should roll back.

while we check it, here's a workaround to make it transactional in your custom UOW scope.

private readonly IUnitOfWorkManager _unitOfWorkManager;
   
public virtual async Task FooAsync()
{
            using (var uow = _unitOfWorkManager.Begin(requiresNew: true, isTransactional: true))
            {
                //...do your work here...
                
                await uow.CompleteAsync();
            }
 }

hi,

First of all there's strict rule. Suite version and ABP version must be same. Because Suite is the generator which generates code from the templates that are in your ABP project.

dotnet tool uninstall --global Volo.Abp.Cli 
dotnet tool uninstall --global Volo.Abp.Suite 
dotnet tool install --global Volo.Abp.Cli 
abp suite install

@unlonlyness

run the following commands :

dotnet tool uninstall --global Volo.Abp.Cli 
dotnet tool uninstall --global Volo.Abp.Suite
dotnet tool install --global Volo.Abp.Cli
abp suite install

@murat.yuceer

This is fixed. First login to abp.io and then download sample https://abp.io/api/download/samples/easy-crm

see https://support.abp.io/QA/Questions/791

This is because your CLI token has been expired. Relogin with the following command:

abp login <username> -p <password>

@dmeagor

Updating nuget packages - Suite

1-Created a new project with version 4.0.2

2-Clicked "Update all ABP packages"

3-I see the versions are updated to 4.1.0

check that you have both CLI and Suite updated to 4.1.0. otherwise I don't see a reason not updating to 4.1.0 :/

New module creation - Suite I reproduced this issue. created an issue. will be fixed in 4.1.1. for a workaround use the CLI. it'll create the host folder. then you can add this module to your solution (or just move the host folder)

abp new Acme.MyProModule -t module-pro

angular proxy multiple issues reported by my developers. can you provide a concrete issue so that I can report to the team?

Please, slow down! thanks for your suggestion ;)