It solved the issue.
Thanks
This code is there, but still i am getting error when Actions->Edit
blazor.web.js:1 [2025-12-20T05:02:32.742Z] Error: Volo.Abp.AbpException: No object mapping was found for the specified source and destination types.
Mapping attempted:
TaskGroupDto -> TaskGroupUpdateDto
Payhas.TaskManagement.TaskGroups.TaskGroupDto -> Payhas.TaskManagement.TaskGroups.TaskGroupUpdateDto
How to fix:
Define a mapping class for these types:
- Use MapperBase<TSource, TDestination> for one-way mapping.
- Use TwoWayMapperBase<TDestination, TSource> for two-way mapping.
For details, see the Mapperly integration document https://abp.io/docs/latest/framework/infrastructure/object-to-object-mapping#mapperly-integration
at Volo.Abp.Mapperly.MapperlyAutoObjectMappingProvider.Map[TSource,TDestination](Object source)
at Volo.Abp.ObjectMapping.DefaultObjectMapper.AutoMap[TSource,TDestination](Object source)
at Volo.Abp.ObjectMapping.DefaultObjectMapper.Map[TSource,TDestination](TSource source)
at Payhas.TaskManagement.Blazor.Pages.TaskManagement.TaskGroups.OpenEditTaskGroupModalAsync(TaskGroupDto input) in D:\Billing_Platform\modules\payhas.taskmanagement\src\Payhas.TaskManagement.Blazor\Pages\TaskManagement\TaskGroups.razor.cs:line 218
at Payhas.TaskManagement.Blazor.Pages.TaskManagement.TaskGroups.<>c__DisplayClass107_0.<<BuildRenderTree>b__41>d.MoveNext() in D:\Billing_Platform\modules\payhas.taskmanagement\src\Payhas.TaskManagement.Blazor\Pages\TaskManagement\TaskGroups.razor:line 151
--- End of stack trace from previous location ---
at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)
at Volo.Abp.BlazoriseUI.Components.EntityAction`1.ActionClickedAsync()
at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)
at Blazorise.DropdownItem.ClickHandler()
at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)
this is the code :
public class TaskManagementBlazorModule : AbpModule
{
public override void ConfigureServices(ServiceConfigurationContext context)
{
context.Services.AddAutoMapperObjectMapper<TaskManagementBlazorModule>();
Configure<AbpAutoMapperOptions>(options =>
{
options.AddProfile<TaskManagementBlazorAutoMapperProfile>(validate: true);
});
Configure<AbpNavigationOptions>(options =>
{
options.MenuContributors.Add(new TaskManagementMenuContributor());
});
Configure<AbpRouterOptions>(options =>
{
options.AdditionalAssemblies.Add(typeof(TaskManagementBlazorModule).Assembly);
});
}
public class TaskManagementBlazorAutoMapperProfile : Profile
{
public TaskManagementBlazorAutoMapperProfile()
{
/* You can configure your AutoMapper mapping configuration here.
* Alternatively, you can split your mapping configurations
* into multiple profile classes for a better organization. */
CreateMap<TaskGroupDto, TaskGroupUpdateDto>();
CreateMap<TaskTypeDto, TaskTypeUpdateDto>();
CreateMap<TaskItemDto, TaskItemUpdateDto>();
}
}
and here is application configuration :
public class TaskManagementApplicationModule : AbpModule
{
public override void ConfigureServices(ServiceConfigurationContext context)
{
context.Services.AddAutoMapperObjectMapper<TaskManagementApplicationModule>();
Configure<AbpAutoMapperOptions>(options =>
{
options.AddMaps<TaskManagementApplicationModule>(validate: true);
});
}
}
Hi I figured it out. the problem was not in the features. We using RenderdMode so BlazorClient configured to RemoteServer which is the BlazorServer not HttpApiHost.
Thanks.
Any suggestions on this issue, cause dependency is there. Signa R getting the features but by http api it does not?
I could not find solution for the issue that I have
Main project is WASM but modules are Blazor server (they do not have blazorClient). Main project and modules are tiered. Does this endpoint's website depend on your feature definition package? Answers : yes, FeatureManagement modules installed.
Nuget package was made from moduled Blazor WASM project from one of the modules for example Module#2 . MainProject (tiered) Module#1 => (feature groups were added DefinitionProvider) (tiered) Module#2 => (DependsOn Module#1 using adding features to the featureGroup) (tiered) Module#3 => (DependsOn Module#1 using adding features to the featureGroup) (tiered) Module#4 => (DependsOn Module#1 using adding features to the featureGroup) (tiered)
Created New Blazor Wasm moduled tiered project where modules are Blazor server , cause there no BlazorClient. In Domain added FeatureDefenitionProvider with GetGroupOrNull and added feature with default true. In DomainShared added constant for features name to use in BlazorClient MenuContributor class for menu item that RequersFeature().
In database AbpFeatureGroups table the custom added groups are there, also in Administration-Settings-FeatureManagment: FeatureGroups are visible and they functionaly working but in menu they are disappeared
Thanks for responding. )))
But with change of configuration, does the localhost also should change in browse as entry point. You still using localhost:44336, instead of test.company:44336? Or am I misunderstanding?
No, I ment url not port
{
"App": {
"SelfUrl": "http://test.company:44336"
},
"AuthServer": {
"Authority": "https://localhost:44376",
"ClientId": "Billing_Blazor",
"ResponseType": "code"
},
"RemoteServices": {
"Default": {
"BaseUrl": "https://localhost:44317"
},
"AbpAccountPublic": {
"BaseUrl": "https://localhost:44376"
}
}
}
Hi, yes it is working. It overriding it. Try to change localhost to random url. In api it works, but in blazor it does not work. Thanks.