Microsoft Dynamics 365 and Power Platform Library

“Expressions have the solution of every problem” Let’s say you have param1 which is data bound (drop down list from dataset1), and param2 which is data bound (drop down list from dataset2). Add dataset1 Add param1 and set its values to be “From dataset” with dataset set to dataset1 Add dataset2 with a parameter dataset2_param (it could be based on a data method with a parameter param, or a query with range param), dataset2_param is the parameter you want to use to filter the drop down list of the second parameter, report parameter param will be created automatically Set param default value to be expression “=Parameters!param1.Value” Add param2 and set its values to be “From dataset” with dataset set to dataset2 Add a data region Preview

Background With AX2009 you are now able to do SSRS reports in Visual Studio. The typical process for designing a report consist in creating a query and bind to it, code some business logic (BL) specific to the report and design the visual part. This post will focus on debugging the report business logic. For more information on designing reports in general, see the  msdn documentation You can have an idea on it from excellent post on Channel 9  here . Debugging Let say you've designed a fancy report in VS and in order to make it do cool stuff, you had to write some pretty complex business logic. Unfortunately, your business logic does not do what you think it should be doing. You know that you've been working too late on too much caffeine, so you suspect that there might be a bug there and you need to do some debugging. The 'attach-to-the-server-process' approach One approach to debug your business logic consist of the following steps · Re...