Creating reports and dashboards | Stimulsoft community forum

When using the report editor, I'm having a problem when "displaying aliases" is enabled.

I should point out that I only use "Business Objects" as sources, derived from classes whose properties are decorated with the "DisplayName" attribute.

The objects are displayed correctly using aliases set with the DisplayName, but when used to build expressions or insert fields into the report, the system uses the alias instead of the field name, resulting in an error.

The version currently used for the report editor is the latest available: Stimulsoft.reports.Blazor 2026.1.1

Regards

Hello,

Please check the following link to our documentation:
https://www.stimulsoft.com/en/documenta ... ssions.htm

If this doesn't help, please send us a sample project that reproduces the issue.

Thank you.

Hello,

Manually editing expressions obviously works, but the problem is that when we drag and drop from the dictionary, the system inserts the expression with the incorrect syntax, making it necessary to manually edit it each time.

I've attached an example screenshot to highlight the problem.

Thank you.

Hello,

Please send the sample project that allows us to reproduce the issue for analysis at support@stimulsoft.com

Thank you.

Hi,

I've attached a simple VS project that reproduces the problem.

- Run the project and click "Designer."
- From the "Business Objects" section, open "Employees" and drag and drop the "First Name" field into the report.

You'll see that the field will be created with the syntax "{Employees.First Name}" and not "{Employees.[First Name]}."

regards

Hello,

We need some additional time to investigate the issue, we will let you know about the result as soon as possible.

Thank you.

hi, any news about this issue ?

Hello.​​

We are still working on the issue.
We will let you know when we get any result.

Thank you.

Hello.

We have identified the issue and need some time to improve it.
We will notify you as soon as we have the results.

Thank you.
#19372

Hello.

We have successfully implemented an improvement.
Please check our next build 2026.1.4, when it becomes available.

Thank you.