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

As a full time developer I'm constantly switching between open documents.

It would be very nice if the Report Designer would support the standard Ctrl+Tab keyboard shortcut for switching between open tabs.

able to modify the line spacing in paragraph

When using specific tables the query builder of the Standalone designer may fail with the message:

System.NullReferenceException: Object reference not set to an instance of an object.
   at Telerik.Reporting.Design.QueryDesigner.Form.DataModelManager.CreateEntity(String path)
   at Telerik.Reporting.Design.QueryDesigner.Form.DataModelManager.FindOrCreateEntity(String path, Boolean refreshRelations)
   at Telerik.Reporting.Design.QueryDesigner.Form.DataModelManager.AddProperty(Property sourceProperty)
   at Telerik.Reporting.Design.QueryDesigner.Form.DataModelTreeViewController.TreeViewAfterCheck(Object sender, TreeViewEventArgs e)
   at System.Windows.Forms.TreeView.OnAfterCheck(TreeViewEventArgs e)
   at System.Windows.Forms.TreeView.WndProc(Message& m)
   at Telerik.Reporting.Design.Common.Controls.TreeViewEx.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

The SQL script for creating the table to reproduce the issue is given in the Object Reference error on using Query Designer forum post.

Hi there,

I would like to make a feature request for your Reporting Tool that would greatly improve the way we are able to create Custom Report Parameters Front-End for our application.
Currently we have access to a number of properties against each Report Parameter such as whether it is Visible or whether or not it is a MultiValue control as well as some other options you are well aware of. I would like to request that you allow the ability to create custom properties against a Report Parameter.

Currently when we build up our custom parameter interface we use the Visible field whether or not to Show the parameter and we use the MultiValue parameter to switch between multi select and single select inputs and we determine the type of control we use based on the Type property. Up to now we have managed ok with the built in properties but we are starting to find some limitations that would easily be resolved if we could add whatever properties we want to a Report Parameter.

An obvious example is if we had more complex control options for the various Report Parameters we might like to add a property that has the name of the control to use rather than having to guess which control to display based on the Type of the Parameter. Or if we have multiple parameters that depend on each other we can add a property that tells us what the hierarchy for the parameters is. That would allow us to know on the front end that one Parameter depends on another parameter.

The reason I believe adding custom properties is the best approach is because then the sky is the limit with how I can customise those options and my own customer parameter interface.

Is there any chance this request could make it into your product roadmap? I believe it is a feature that could be very beneficial not just for us but to all your customer.

Thanks,

Aaron

In the ReportProcessor, it would be interesting to be able to capture the log.
Since it is shown on the Console. And if possible to have other statuses such as generated the query, loading resources etc ...

Processing report
Rendering report

You can also calculate an estimated time to process / render.

Tranks.