Hi there,

I was wondering if you had in the Pipeline/road map a Report Designer integrated into Visual Studio for .NET Core?

And also if there is an ETA?

If I can add my +1 to this would be appreciated.

Regards,

Mark

Data Explorer of the Report Designer does not refresh the schema on the Refresh button click when the Stored Procedure used in a SqlDataSource component is modified.

You need to reconfigure the data source component, for example, just open the Data Source Wizard and click Finish, or close and re-open the report for the actual refresh.

My report consists of a Report Header and a Detail section. Their design-time height is totally less than 20mm. There are no PageBreaks or GroupPageBreaks and all KeepTogether properties are False. In Print Preview, the Detail section starts from the second page when the PaperSize Height is 88mm or less. This is not expected as there is sufficient space left after the Report Header. The Detail section starts rendering from the first page only when the paper height is more than 88mm, which is the expected behavior.

See the forum post Report Header and Detail Section does not print together for the report definition that allows reproducing the issue.

When exporting to Excel Worksheet, the CheckBox item is rendered as Excel Picture. If the machine settings are higher than the default 96 DPI (100%), the checkbox image is generated with incorrect size and the produced Excel file is corrupted.

Steps to reproduce:

1. Create a Blazor application;

2. Add Teleri.Reporting NuGet package;

3. Add Telerik.WebReportDesigner.Services Nuget package -> some of the app dependencies are broken.

Solution:

Refer the .NET Standard DLLs from C:\Program Files (x86)\Progress\Telerik Reporting <Version>\Bin\netstandard2.0.

Current Behavior

1. Open the Standalone Report Designer.

2. Navigate to the Open Menu.

3. Select the Computer Tab.

4. Observe the available list of folders under the Computer Menu.

5. Navigate to the Options Menu.

6. Change the Default Working Directory.

7. Navigate to the Open Menu.

8. Observe the Available Folder and the directory will not be listed.

9. Select the Browse Button.

10. Observe the open folder is not the expected Default Working Directory from Step 6.

Expected Behavior

It would be nice to remove the previous folder from the Standalone Report Designer Open Menu.

Please add support for Data Matrix barcodes.  As of Q3 2014 this is the only format we will still need to rely on another library to create an image that is placed in a picture box.  We would much rather be able to use the Barcode control for all our barcode requirements.

It would be very handy, if the value property of the PictureBox would resolve images from base64 strings besides the Image, Image byte[], relative or absolute URI.
It should be fairly simple to implement. I wrote my own user function for this. It would be beneficial to have this out of the box.

[Function(Category = "Image", Namespace = "ImageFunctions", Description = "Converts a base64 string to an image byte array")]
public static byte[] ConvertFromBase64(string imageString)
{
    if (imageString != null)
    {
        // Convert base 64 string to byte[]
        byte[] imageBytes = Convert.FromBase64String(imageString);
        return imageBytes;
    }
    else
    {
        return null;
    }
}

When the SqlDataSource wizard uses a connection to a non-MSSQL database, which is registered in a Report Server instance, previewing the results on the "Preview data source results" page will throw an exception.

I am suggesting a global 'this.value' option for conditional formatting. This approach would allow quick use of the fields value to be the basis of the condition. In reports that use complex and sometimes lengthy calculations, this is would be a huge timesaver.  This feature would also have to work with your current 'cut and paste' rule feature.

If I had to create individual rules for each box on a page, or a series of rules for each box to do multiple colors it would be a very unproductive use of time for me.

Putting my one project in perspective, if I had to do it with rules.

Right now, I have over 300 fields with 2 rules each, which is 600 rules to write and that is only about 75% of what I need on a single page of the report. This is a serious time burn activity just to get something like a conditional formatting to work on the value of the field. The rule approach might be good if the solution has less than 10 fields, but to have the shear numbers I do, I do not think it rule creation for each field is a viable solution.  Another solution proposed was to create additional calculated columns. The problem with this is that the data source already has 100+ columns and I would hate to add any more fields (at least 100+ more), due to performance considerations.

I love the Telerik reporting solution do to the instant flexibility in my apps, but the conditional formatting is lacking especially if you use it for large analysis reports with comparisons that the client (and myself) would like coloring of the text to 'see' things easier.

Telerik: See ticket 1462207 as reference