Hello Lech, sorry for the delay. We are building multiple features and our time is scarce.
So, first of all: we cannot update the API to 2024.x.x simply because our report doesn’t render after the update. As I said before, we cannot simulate the problem because we cannot debug the report, and as I said too, the data is being transported correctly, and proof of this is that after rollbacking the version to 2023.3.1 it works fine. No code was changed, only the API version and the .exe version. Everything suggests that there are some bugs in the 2024 version, as shown in the picture below:
Before update:

- Screenshot 2024-01-22 161549.png (72.09 KiB) Viewed 4641 times
After update:

- Screenshot 2024-01-22 161500.png (51.65 KiB) Viewed 4641 times
With further investigation, we noticed on our SQL profiler that the null values are being converted to empty strings, as shown below:

- Screenshot 2024-01-22 162450.png (45.34 KiB) Viewed 4641 times

- Screenshot 2024-01-22 162502.png (32.21 KiB) Viewed 4641 times
Thats our api parameters right before opening the report:

- Screenshot 2024-01-22 165609.png (39.81 KiB) Viewed 4641 times
That our source code:
protected async Task<StiReport> GetReportAsync(string reportFolder, Dictionary<string, object> parameters)
{
string reportFile = parameters["Report"] + ".mrt";
string path = Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "ReportTemplates", reportFolder, reportFile);
Stimulsoft.Drawing.Graphics.GraphicsEngine = Stimulsoft.Drawing.GraphicsEngine.ImageSharp;
var report = StiReport.CreateNewReport();
report.Load(path);
report.Culture = GetCulture(parameters);
if (parameters.ContainsKey("Lang"))
parameters["Lang"] = report.Culture;
var request = GetRequestData();
AddReportParameter(report, "CompanyId", request.CompanyId);
AddReportParameter(report, "UserId", request.UserId);
foreach (var (key, value) in parameters)
{
AddReportParameter(report, key, value);
report[key] = value;
}
AddCommentsToSqlCommands(report, reportFolder, request, parameters);
SetConnectionStrings(report);
await SetLogo(report, parameters);
report.Dictionary.Synchronize();
return report;
}
I tried to update to 2024.1.3 and still got the error.
So, we are stuck on this. We cannot even start to try to fix the chart colors because, now, the report doesn’t even render. Let's do one thing each. Let’s try to fix this data transport issue.
How can we move forward to find this bug? Is it a bug? Is it a new feature that converts strings to empty spaces? I really don’t know how to proceed.
I guess one of the possible solutions is to schedule a call so we can check this together.