Activities of "sean.alford"

@Chrille yes I reported that bug in 2.8.0 and @Alper has added it to their backlog.

@Alper,

I manually copied Volo.Abp.Commercial.SuiteTemplates.dll into the .Web project; however ABP Suite is still unable to locate it.

@Alper

I verified Volo.Abp.Commercial.SuiteTemplates.dll is where it's suppose to be. However, Suite is still displaying the same error.

Non-Teir Project (.Web.Unified)

@ididsbury,

You said you upgraded from 2.8 to 2.9. Did you creat your project in 2.8? If so, have you tried creating a new project with 2.9? I think OU were just added in 2.9. If your proejxt was created with 2.8 you'll probably need to add the OU in manually.

@ididsbury does the user you're logging in with have access to the Org Units? You may need to grant the admin user access to it also.

ABP Suite CRUD Generator (Module)

Description: Cannot find Volo.Abp.Commercial.SuiteTemplates.dll

Configuration

• ABP Framework version: v2.9.0
• ABP CLI version: v2.9.0
• ABP Template: module-pro-2.9.0
• ABP Suite version: v2.9.0
• UI type: MVC (Module)
• Tiered (MVC) or Identity Server Seperated (Angular): no

Steps to reproduce the issue:

1. Create new module: abp new Company.ProjectName -t module-pro
2. ABP Suite: Add an existing solution
3. ABP Suite: Add an Entity info with Properties
4. ABP Suite: Click Save and generate

ABP Suite Error

I followed @Alper's instructions here ([Cannot find Volo.Abp.Commercial.SuiteTemplates.dll #48](https://support.abp.io/QA/Questions/48#answer-ea26e90e-4e76-ccdf-44a4-39f3ea298e33)); however, this did not correct the problem.

Domain Project

ABP Suite 2.8.0

I created a new role for our support technicians and gave them access to View, Create and Edit Identity Management User. (See below)

Next, I create a new user and assigned them to the Support Technican role. They can see the Users list, but when they click New, Edit, or Claims nothing happens. The Set Parrword dialog opens as expected.

NOTE: I also tried granting the user access within the User Permissions. However, this produced the same results.

ABP Suite 2.8.0 - Low Priority Cosmetic Issue

Here's another low priority cosmetic issue that really doen't cause any problems.

I've noticed that if you click anywhere outside the MessageBox's bounded rectange that it will close as if you clicked OK. However, withing the MessageBox's bounded rectange you must click OK before it will close. I have not tried this on other MessageBox's that have multiple buttons. (i.e. OK, Cancel)

@hikalkan thanks!

I have watched your presentation a few time before. (You do a great job of explaining things in that presentation!) To be honest I didn't relazie the navigation properties in ABP Suite were actaully creating an EF naviagation property. I thought it was only creating and storing the Id. I used the Naviation Properties in ABP Suite simply for the modal picker. :)

So we really shouldn't ever use the ABP Suite Navigation Properties if we what to follow the DDD best practice. Right?

All we really wanted from the begining was to stort Guid Ids.

Is this approch OK? Use ABP Suite to create the properties for the Id's, and then manaully add HasIndex(), and then the FK into the generated migration?

Manually Added Indexs

Manually Added FK

Where can I find an example of adding a modal Picker for an Id field similar to the one that ABP Suite creates when you choose Modal in the NP UI? I've looked in the EasyCRM project but I don't see an example of a Modal picker.

Thanks guys!

@hikalkan, I am fairly new to DDD so please forgive me for my lack of knowledge. If a navigation properties to the AppUser is not good practice, then what is a best practice for this use case in DDD? Is there a better way to utilize the existing system user? I don't think creating and maintaining multiple user entities is very practical.

1. When we create a support ticket we need to assign it to one of our Support Technicians.