Activities of "EngincanV"

[IgorG] said:

[EngincanV] said: Hi, when you need to add new columns or extend existing module entities, the recommended approach is to use Module Entity Extensions. This method automatically includes the new columns in the DataGrid, as well as in the create and update forms.

However, it doesn't support autocomplete functionality out of the box. From your scenario, it looks like you need an autocomplete component that can filter or search for an entity record as the user types. In this case, you'll need to implement the required changes manually.

To do this:

• Override the UserManagement.razor page in the identity-pro module.
• Add your custom autocomplete component to both the edit and create models.
• On the backend side, extend the IdentityUser entity in your application by creating a new user entity and add your custom logic accordingly.

Regards.

Override the UserManagement.razor page in the identity-pro module. - in this case i need the layout of the UserManagement.razor page. Where can i get it ?

Hi, you can get the source code of the identity-pro module with the following command:

abp get-source Volo.Abp.Identity.Pro

This command will install the source code of the Identity Pro module (I guess you have access?), and then you can find the UserManagement.razor in the Blazor project.

Regards.

[htalavera] said: Just to clarify, if we extend the PermissionAppService to include inherited permissions and return them to the UI correctly, will any changes made to the enabled permissions at the user level be saved?

Hi, simply extending the PermissionAppService.GetAsync method to display inherited permissions in the UI won't automatically enable saving changes to those permissions at the user level.

This is because when permissions are granted via the user or role permission models, they apply only to that specific user or role. In your case, since the permissions are globally granted to tenant users, overriding them at the user level won’t have any real effect (except for adding a few redundant records to the database). So, while newly granted permissions may work as expected, attempting to un-grant inherited ones likely won't take effect.

To handle this properly, you may need to override the UpdateAsync method in the PermissionAppService to apply your custom logic and review GlobalPermissionValueProvider again.

Regards.

Hi, when you need to add new columns or extend existing module entities, the recommended approach is to use Module Entity Extensions. This method automatically includes the new columns in the DataGrid, as well as in the create and update forms.

However, it doesn't support autocomplete functionality out of the box. From your scenario, it looks like you need an autocomplete component that can filter or search for an entity record as the user types. In this case, you'll need to implement the required changes manually.

To do this:

• Override the UserManagement.razor page in the identity-pro module.
• Add your custom autocomplete component to both the edit and create models.
• On the backend side, extend the IdentityUser entity in your application by creating a new user entity and add your custom logic accordingly.

Regards.

[rogercprops] said: The above steps didn't resolve the problem

Hi, could you please open a new terminal and run the abp suite command, then share the output with us?

If you've recently upgraded ABP Studio, created a new solution, and then attempted to open ABP Suite, ABP Studio first checks the project's compatibility with your installed ABP Suite version. If there's a version mismatch, it prompts you to update ABP Suite before launching it.

In some cases, if the suite is launched before the update completes, it can result in errors like the one you're experiencing. By running the abp suite command manually, we can confirm whether this is the issue.

Regards

[nguyenngoc.son] said: If we have multi templates and each template have different model, how we can do it dynamic instead of hardcode the model for each template

Hi, the model does not have to be a named class, it can be an anonymous class with the related properties. So, maybe you can have a key-value pairs (or dictionary to be more specific), convert it to an ExpandoObject and pass it as a model like below:

// Get these values from an input as key-value
var dictionary = new Dictionary<string, string>
{
    { "Name", "John" },
    { "Age", "30" },
    { "City", "New York" }
};

// Convert to ExpandoObject (which behaves like an anonymous type)
dynamic expando = new ExpandoObject(); 
var expandoDict = (IDictionary<string, object>)expando;

foreach (var kvp in dictionary)
{
    expandoDict[kvp.Key] = kvp.Value;
}

// Use TemplateRenderer
var rendered = await _templateRenderer.RenderAsync(
    templateContent,
    expando,
    "Razor"
);

Hi, you can use the script that was shared at https://abp.io/qa/questions/8627/3a17775e-701a-1b24-6604-8bc0622ac518 and pass the version as 0.9.8.

Regards.

I'm running ABP Suite on a sub module that has been upgraded to 9.1.3 from 6 or 7 originally

Adding typeof(VoloAbpCommercialSuiteTemplatesModule) to C:\Users\brauerj\Source\repos\MyProject\modules\MyProject.SubMod\src\MyProject.SubMod.Domain\SubModDomainModule.cs Seemed to solve the problem. But I shouldn't have to do that for each sub module should I?

Hi, by default, in our domain module, we have the related reference, but since you upgraded from a much earlier version, it might not have been added at the time. For now, you can continue by adding the VoloAbpCommercialSuiteTemplatesModule, and if you create a new solution, you will see the module dependency in your domain layer.

Thanks for understanding. Regards.

[jmvvliet] said: Thanks! Would add a lot of value and is complementary to the BookStore example (BookTypes) provided by ABP :)

I agree, it's a great feature that fits well with the BookStore example and how BookTypes are used. It will definitely add value. Thanks again for the suggestion!

Hi, thanks for the feature request! We've created an internal issue to track it and will include it in our planning.

Best regards.

Hi, ABP does not check if the URL is empty or not, it's a nullable field, because in your code you may want to write audit logs for any internal process call. For example, you may want to audit log your event handlers and for these cases, the URL should be emptyl and you can also think similar scenerios where HttpContext is not in the place.

If you don't want to log if the URL is empty, then you can create audit log contributor or configure AbpAuditingOptions and add a selector to its AlwaysLogSelectors property. (See https://abp.io/docs/latest/framework/infrastructure/audit-logging#abpauditingoptions)