Progress® Telerik® Reporting Feedback Portal
Back to Feed
Request a Feature Report a Bug
Unplanned
Last Updated: 14 Feb 2024 13:14 by Steve
Jonathan
Created on: 26 Jun 2018 13:45
Type: Feature Request
20
add new function: LOOKUP() (similar to SSRS)
This function would allow you to lookup a value from another data source with a value that is in your current data source.  It would return the first matching value for the specified name from a data source that contains name/value pairs.

This would allow the porting of many SSRS reports over to Telerik Reporting.

Example: 

I have a report which lists all sales staff in our firm, with other personal information. We have a multi-dimensional data source (Cube) where we have all the financial data stored and calculated. 

If I wanted to retrieve the total sales and total revenue that each member of the sales staff had, it would require me to use a sub-report to load the data (using a parameter to pass the staff member's unique ID).  

This causes the loading/generating of the report to take longer, as the query against the Cube has to happen for each member of the sales staff, because of the use of a sub-report. With this new LOOKUP() function, it would allow the data source to be loaded and the report would be able to lookup the sales and revenue values for each staff member ID.
5 comments
Steve
Posted on: 14 Feb 2024 13:14

Hi,

This will be a very useful feature. In data that I work with, there are numerous entities referenced by ID/key that have a detail record - and in some cases these exist in another database. We have mostly solved these by implementing database views. I have in the past sourced detail records in separate datasources and embedded List report items, filtered to the ID of the current parent  data item. This isnt very efficient.

A "lookup" feature only requires the datasource query/retrieval to run once (unless theres some need/feature to evaluate differently dependant on scope?). Potentially, something like a dictionary object could be defined at the report/global level, having datasource and key/value definition properties.

An object/function-like entry can be shown in the expression editor for a defined lookup dictionary. While a statement format like "LookUp("myDictionary", "myKey")" could be supported, something like "myDictionary["myKey"]" could work (though maybe "Dictionaries.myDictionary["myKey"]"). The statement then just returns the corresponding value when there is a match or null otherwise.

ADMIN
Silviya
Posted on: 10 Jan 2019 09:49
Hello Mykhaylo and Jonathan,

Mykhaylo, thank you for your input, we will consider this scenario during the implementation.

Jonathan: Unfortunately, I cannot name the exact date when the task will be in development. All tasks are sorted based on multiple criteria such as demand, severity, available and required resources etc.
Alternatively, you can follow the feature request to check if the status is changed to 'In Development' and also our release history page for release notes.
 
Regards,
Silviya
Progress Telerik
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Mykhaylo
Posted on: 09 Jan 2019 15:58
Another possible usage of Lookup: translation of report resources. All translations as text resources are stored in a database and returned in a corresponding dataset for current user Locale. I need a formula to be inserted in each Label Value in a report to get translated value from translations dataset. Lookup("CurrentResourceAlias",Fields.Alias.Value,Fields.Text.Value,"ReportResourcesDataset").
Jonathan
Posted on: 28 Sep 2018 12:39 
Milen,

Do you know when this functionality might be added?
ADMIN
Milen | Product Manager @DX
Posted on: 12 Sep 2018 16:56 
Thank you for your request.
Create an account Log In
View
Type
Status