Hello, Could you please finally fix the localization in the excel methods of the AppService in a generate suite entity? I am tired of fixing myself everytime
for example, this is a generated excel method
public virtual async Task<IRemoteStreamContent> GetListAsExcelFileAsync(DemoEntityExcelDownloadDto input)
{
var downloadToken = await _downloadTokenCache.GetAsync(input.DownloadToken);
if (downloadToken == null || input.DownloadToken != downloadToken.Token)
{
throw new AbpAuthorizationException("Invalid download token: " + input.DownloadToken);
}
var clientes = await _clienteRepository.GetListWithNavigationPropertiesAsync(input.FilterText, input.Name1, input.Name2, input.Name3);
var items = clientes.Select(item => new
{
Name1 = item.DemoEntity.Name1,
Name2 = item.DemoEntity.Name2,
Name3 = item.DemoEntity.Name3
});
var memoryStream = new MemoryStream();
await memoryStream.SaveAsAsync(items);
memoryStream.Seek(0, SeekOrigin.Begin);
return new RemoteStreamContent(memoryStream, "DemoEntities.xlsx", "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet");
}
First, the file name is not localized, if I changed language, it will be downloaded always like "DemoEntities.xlsx". Also, if you are using an entity with navigationproperties or not, the columns are not localized either, you need to add a configuration for that.
For example
var config = new OpenXmlConfiguration
{
DynamicColumns = null
//[ new DynamicExcelColumn("XYZ") { Name = L["XYZ"]} ]
};
I have to recreate the column every time and it's kind of frustrating since ABP Suite template system doesn't provide a way to iterate or use the properties to do this kind of complex scenario, please fix it.
Hello
In ABP Suite 8.1.3, the "Menu Icon" field doesn't work, you can place any font-awesome icon (even the PRO one) and it get replaced with the default one "fa-file-alt", please move any validations from here, people can use it for PRO or FREE version of font-awesome
No answers here
any answers for this, please?
In the Index.Js template, for example, Frontend.Mvc.Page.index.js.txt
We can add this as navigation dropdowns, if anyone wants to use typeahead because they have high volume in their dropdowns, in the Index Page, we are forced to use traditional approach of getting the information in the Razor Pages and then bind the control, why can't we use typeahead in the Index.cshtml too?
To accomplish that, we might start by adding this to work in the index.js and change the HTML generated in the index.cshtml %%navigation-property-dropdown-methods%%