POSTED BY AHMED MUHAMMAD ALAM  ON 17 FEB 2013 3:11 AM

Hello Experts,

It's a default report.

I have one report "Detailed Trail Balance" for the first time when I click select for the General Journal Account Entry [and select Financial Dimension Branch = 01] and click ok than again click select for another time. The dialog box shows me two lines of Range although I have define only one range and the second line is duplicated. If I click ok and again click Select it shows me duplicate of last two line of range.

I am using MS Dynamics AX 2012 R2. 

Any help in this situation.

Regards,

Ahmed

Reply

• POSTED BY FABIO  ON 8 MAY 2013 8:08 PM  VERIFIED ANSWER VERIFIED BY AHMED MUHAMMAD ALAM

  Class_DimensionProvider.rar

  Hi Ahmed,

  About the duplicated ranges bug, the problem is in\Classes\DimensionProvider\addAttributeRangeToQuery method. I'm attaching a XPO with the code fixed.

  Cheers

  DYNAMICS AX 2012 TRIAL BALANCE REPORT BUG RANGE

  Reply
• POSTED BY BSUGITAYASA  ON 13 MAY 2013 9:47 PM  VERIFIED ANSWER VERIFIED BY AHMED MUHAMMAD ALAM

  Dear Fabio,

  Thanks for the advice. I have tried and have been successful.

  About duplicate existing range problem on\Classes\DimensionProvider\addAttributeRangeToQuery also been successful in fix

  
  

  Cheers

  Reply

• POSTED BY AHMED MUHAMMAD ALAM  ON 26 FEB 2013 5:03 AM

  Any suggestion

  Reply
• POSTED BY AHMED MUHAMMAD ALAM  ON 26 MAR 2013 3:34 AM

  Dear Experts,

  Is there any patch or hot fix from the Microsoft to resolve this issue.

  Regards,

  Ahmed

  Reply
• POSTED BY AHMED MUHAMMAD ALAM  ON 8 APR 2013 4:21 AM

  Dear Experts,

  another problem which I forget to share with you, i.e. when I run the report it shows me the following error.

  Error executing code: The field with ID '0' does not exist in table 'LedgerTrialBalanceStagingTmp'.

  Stack trace

  (S)\Classes\RecordInsertList\add

  (S)\Classes\LedgerTrialBalanceDP\populateTmpTransDetail - line 100

  (S)\Classes\LedgerTrialBalanceDP\processReportDetail - line 28

  (S)\Classes\LedgerTrialBalanceDP\processReport - line 32

  (S)\Classes\SrsReportRunRdpPreProcessService\executeWithContract - line 102

  (S)\Classes\SrsReportRunRdpPreProcessService\executeRDLClasses - line 38

  (C)\Classes\SrsReportRunService\preRunReport - line 26

  (C)\Classes\SrsReportRunImpl\preRunReport - line 12

  (C)\Classes\SrsReportRunController\runReport - line 42

  (C)\Classes\SrsReportRunController\run - line 6

  (C)\Classes\SysOperationController\startOperation - line 10

  (C)\Classes\SrsReportRunController\startOperation - line 12

  (C)\Classes\LedgerTrialBalanceController\main - line 9

  Reply
• POSTED BY BSUGITAYASA  ON 7 MAY 2013 3:48 AM

  Hi All,

  I also found a similar error.

  I've been trying to open a report in the General Ledger > Reports > Detailed trial balance. In the form, I input a parameter for Ledger account.MainAccount. When I click OK, I got an error

  Can anybody help me, how to open the report without getting this error?

  Thank you in advance,

  bsugitayasa

  DYNAMICS AX 2012 TRIAL BALANCE REPORT DETAIL BUG

  Reply
• POSTED BY FABIO  ON 8 MAY 2013 4:01 AM SUGGESTED ANSWER

  Hi Ahmed.

  For the error "The field with ID '0' does not exist in table 'LedgerTrialBalanceStagingTmp'" you just need to change the RecordInsertList initialization:

  \Classes\LedgerTrialBalanceDP\populateTmpTransDetail, Line 64:

  Original line:

  recordInsertList = new RecordInsertList(tableNum(LedgerTrialBalanceTmp), true, true, true, true, true, _ledgerTrialBalanceStagingTmp);

  Change to:

  recordInsertList = new RecordInsertList(tableNum(LedgerTrialBalanceStagingTmp), true, true, true, true, true, _ledgerTrialBalanceStagingTmp);

  Compile forward, generate incremental CIL, and it's done.

  Cheers

  DYNAMICS AX 2012 TRIAL BALANCE REPORT DETAIL BUG

  Reply
• POSTED BY FABIO  ON 8 MAY 2013 8:08 PM  VERIFIED ANSWER VERIFIED BY AHMED MUHAMMAD ALAM

  Class_DimensionProvider.rar

  Hi Ahmed,

  About the duplicated ranges bug, the problem is in\Classes\DimensionProvider\addAttributeRangeToQuery method. I'm attaching a XPO with the code fixed.

  Cheers

  DYNAMICS AX 2012 TRIAL BALANCE REPORT BUG RANGE

  Reply
• POSTED BY BSUGITAYASA  ON 13 MAY 2013 9:47 PM  VERIFIED ANSWER VERIFIED BY AHMED MUHAMMAD ALAM

  Dear Fabio,

  Thanks for the advice. I have tried and have been successful.

  About duplicate existing range problem on\Classes\DimensionProvider\addAttributeRangeToQuery also been successful in fix

  
  

  Cheers

INTRODUCTION

This article provides links to documentation about how to install hotfixes for Microsoft Dynamics AX 2012. It also describes how to install hotfixes for Microsoft Dynamics AX 2009 and Microsoft Dynamics AX 4.0.

Note Make sure that you thoroughly review the Microsoft Knowledge Base article that documents a specific hotfix to determine the objects, the database tables, or the files that will be affected.

Back to the top | Give Feedback

More information

Hotfixes that are released for Microsoft Dynamics AX 2012

The detailed process for installing updates and hotfixes to Microsoft Dynamics AX 2012 is documented on TechNet, in the following section: Apply updates and hotfixes.

Hotfixes that are released for Microsoft Dynamics AX 2009 and for Microsoft Dynamics AX 4.0

Note The general process for installing updates and hotfixes to Microsoft Dynamics AX 2009 is documented in the following white paper: Servicing Microsoft Dynamics AX 2009.

Microsoft releases hotfixes for Microsoft Dynamics AX in the following formats:

• Hotfixes are released as a compressed (.zip) file. The files that the .zip file contains replace existing files on the computer.
• Hotfixes are released as a Microsoft Windows Installer update. These hotfixes contain a Setup.exe file.

Microsoft releases hotfixes for Microsoft Dynamics AX 4.0 in the following formats:

• Hotfixes are released as Microsoft Windows Installer updates. These hotfixes contain a Setup.exe file. 
• Hotfixes are released as DIS-layer files (AxDIS.aod) or as DIP-layer files (AxDIP.aod). DIS-layer changes address issues in SYS-layer code. DIP-layer changes address issues in GLS-layer code. 
• Very rarely, hotfixes are released as .xpo files that contain code. The code is applied to existing objects, to database tables, or to both. 

General guidelines for hotfixes that replace files

Some Microsoft Dynamics AX hotfixes replace files on the computer. For instructions about how to install a hotfix that replaces files, carefully read the documentation that accompanies the hotfix download. The following are general recommendations for installing hotfixes that replace files:

• Before you copy the files that are included in the hotfix to your computer, use your usual backup processes to back up the server files that are affected by the hotfix.
• Test all hotfixes in a test environment to verify that your customizations are not adversely affected.
• Have all users log off the Microsoft Dynamics AX client application. Stop the Application Object Server (AOS) instance before you rename and copy the hotfix files.
• When label files are included in the hotfix, copy all the included label files to the Microsoft Dynamics AX application folder. The label files will have the following file name extensions:
  • .ali
  • .acd
  • .alc
  By default, the application folder has the following path:
  root directory\Axapta Application\appl\Standard
  Note In this path, root directory represents the hard disk drive and the main directory in which Microsoft Dynamics AX is installed.

Customized environments

If you customized your environment before you installed a hotfix, thoroughly review the Microsoft Knowledge Base article that documents the hotfix that you want to install. Any objects that are affected by the hotfix will be overwritten. This may cause customizations in those objects to be lost.

Database backups

If database tables are affected, create a full database backup before you apply the hotfix. For instructions about how to back up a database, see the Microsoft SQL Server documentation. Or, see the Oracle Database Server documentation.

Installation information

Hotfixes that are released for Microsoft Dynamics AX 2009

To install hotfixes that are released as an application update for Microsoft Dynamics AX 2009, follow these steps:

1. Extract the files from the package.
2. Open the kbxxxxxx.txt file in the hotfix package to identify which objects will be patched when the hotfix is installed.
3. Exit all Microsoft Dynamics AX 2009 clients, and then stop the AOS instance.
4. Back up the database.
5. Back up the application folder.
6. Restart the AOS instance, and then review the Application log on the server that is running the AOS service to make sure that the AOS instance starts correctly. The AOS instance rebuilds the application object index. The Axapd.aoi file contains the application object index.
   
   Note Depending on the server hardware that you are using, the startup of the AOS instance may time out before the process is completed. This issue occurs because the process has insufficient time to rebuild the Axapd.aoi file before the AOS tries to use the file.
   
   The AOS instance remains in a starting status until the *.aoi file rebuild is completed. At that point, the AOS instance has a "started" status. No additional steps are required. Wait for the rebuild to finish, and then review the Application log for an indication that the AOS instance starts. 
7. Run the Axpatch.exe file for the application hotfix installation.
   1. Select the language in which to run the installation, and then click OK.
   2. When the installer wizard starts, click Next.
   3. Review the Microsoft Software License Terms, click to select the check box to accept the license terms if you agree, and then click Next.
   4. On the Select components page, the Application files option should be selected by default. Click Next.
   5. On the Select configuration page, indicate the correct configuration, and then click Next.
   6. On the Ready to apply hotfix page, click Install.
   7. When setup is complete, click Finish to exit the wizard.
8. From a client, verify that you can connect to the AOS instance as the Microsoft Dynamics AX administrator.
9. Validate the installation of the hotfix by doing the following:
   • Open the SysHotfixManifest class in the AOT.
   • Verify that the class contains a method that has a name that is the same as the article number of the installed hotfix.
10. Use the code upgrade tool (“Code comparison”) to compare the SYP or GLP change with any VAR or CUS layers. If customizations exist, the partner's or customer's IT staff may be required to merge the hotfix into the customized system.

Hotfixes that are released as a Windows Installer update

Important The following actions must be performed:

• The ObjectServer kernel file must be installed on each AOS server.
• The Client kernel file must be installed on each client computer.
• The NetBusinessConnector kernel file and the ComBusinessConnector kernel file must be installed on every computer that is running the Microsoft Dynamics AX .NET Business Connector and the Microsoft Dynamics AX Com Business Connector.
• The ApplicationIntegrationServer kernel file is the BizTalk Adapter. Make sure that you install the ApplicationIntegrationServer kernel file together with the NetBusinessConnector kernel file when you update the BizTalk Adapter.

A Windows Installer update updates the following Microsoft Dynamics AX 4.0 client binary files:

• The .exe file
• The .dll files

These files are also known as the kernel files. To apply the Windows Installer update, follow these steps:

1. Extract the files from the hotfix. The extracted files may contain the following folders:
   • ApplicationIntegrationServer
   • Client
   • ComBusinessConnector
   • NETBusinessConnector
   • ObjectServer
2. Test the hotfix in a test environment. Then, schedule downtime.
3. Exit all the Microsoft Dynamics AX software clients. Then, shut down the AOS instances that are connected to the production program file share.
4. Back up the database, and then back up the application folder.
5. Run the Setup.exe file that is included in each folder in the hotfix.
6. Restart the AOS instance. Review the application event log on the server that is running the AOS service to make sure that the AOS instance starts correctly. The AOS instance rebuilds the application object index. The Axapd.aoi file contains the application object index.
   
   Note Depending on the server hardware that you are using, the startup of the AOS instance may time out before the process is complete. This issue occurs because the process has insufficient time to rebuild the Axapd.aoi file.
7. Use the AOS instance to log on to a client by using the Microsoft Dynamics AX 4.0 Administrator account. Verify that you can successfully connect.

Hotfixes that are released as an .xpo file that contains code

Hotfixes that are released as an .xpo file contain code-level fixes that directly affect objects or database tables in Microsoft Dynamics AX.

Important Before you continue, examine each .xpo file for the objects or tables that will be changed. Note any customizations to your current environment that may be affected. We highly recommend that you apply all hotfixes in a test environment before you apply the hotfixes to your live system.  

1. Log on to Microsoft Dynamics AX by using the Microsoft Dynamics AX Administrator account. Make sure that no other users are logged on to Microsoft Dynamics AX.
2. Open the Application Object Tree dialog box. To do this, use one of the following methods:
   • On the Standard toolbar, click Application Object Tree.
   • On the keyboard, press Ctrl+D.
   • On the File menu, point to Open, and then click Application Object Tree.
3. In the Application Object Tree dialog box, click Import on the toolbar.
4. Click Browse, and then locate the .xpo file.
5. In the Open dialog box, click the .xpo file, and then click Open.
6. Click OK to complete the import process.
   
   Note You may have to complete a forward compile or a full Application Object Tree (AOT) compile process.

How to install hotfixes that are released as DIS-layer or DIP-layer files

  To install hotfixes that are released as DIS-layer or DIP-layer files, follow these steps: 

1. Extract the files from the hotfix package.
2. Before you copy the files that are included in the hotfix to your computer, use your usual backup processes to back up the application folder and the server files that are affected by the hotfix.
3. Test the hotfix in a test environment. Then, schedule downtime when no other users are on the system.
4. Exit all the Microsoft Dynamics AX software clients. Then, shut down the Application Object Server instances that are connected to the production program file share.
5. Copy the AxDIS.aod file and the AxDISen-us.ald file into each application folder where the other .aod files exist. By default, this folder is in the following location:
   \application\appl\standard
   Note In this step, always use the copy function. Do not use the move function. When you move a file, the permissions of the source folder will be taken for this file. When you copy a file, it will take the permissions of the target folder.
6. Make a backup copy of the Axapd.aoi file by renaming the file. Or, delete the Axapd.aoi file in each application folder.
7. Restart the AOS instance. Review the Application log on the server that is running the AOS instance to make sure that the AOS instance starts correctly. The AOS instance rebuilds the application object index. The Axapd.aoi file contains the application object index.
   
   Note Depending on the server hardware that you are using, the startup of the AOS instance may time out before the process is complete. This issue occurs because the process has insufficient time to rebuild the Axapd.aoi file.
   
   The AOS instance will remain in a starting status until the .aoi file is rebuilt. At that point, the AOS instance will have a "started" status. No additional steps are required. Wait for the rebuild to finish, and then review the Application log for an indication that the AOS instance started.
8. Use the AOS instance to log on to a client computer by using the Microsoft Dynamics AX 4.0 Administrator account. Next, connect to this AOS instance by using the client software to verify that you can successfully connect. Finally, verify that the changes were detected by Microsoft Dynamics AX and that they are visible in the AOT.
9. If an upgrade checklist appears, complete the checklist to make sure that there will be no additional issues. If no upgrade checklist appears, the DIS or DIP layer is not recognized. If the DIS or DIP layer is not recognized, use one or more of the following methods:
   • Create a new application folder. Then, copy all the files from the existing application folder to the new application folder.
   • Change the AOS instance configuration to use the new application folder. To do this, follow these steps:
     1. Click Start, click Run, type Control Admintools, and then click OK.
     2. Double-click Microsoft Dynamics AX Configuration Utility.
     3. On the Application Object Server tab, select the new application folder that you created in the application instance list.
     4. Apply the configuration, and then restart the AOS instance.
     5. Repeat step 8.
10. After the checklist is completed, recompile the whole application.
11. If you are using multiple application folders and multiple AOS instances, stop all AOS instances, and then restart all AOS instances.

Back to the top | Give Feedback

References

For more information about import options for an .xpo file, see the Microsoft Dynamics AX Developers Guide.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Back to the top | Give Feedback

POSTED BY MAXIM MICHTCHENKO  ON 25 JUN 2012 4:35 PM

I have a custom table and a SSRS report using this table on the executon of the report user is getting following error:

User 'ADMINIST' is not authorized to select a record in table 'LabelGroupDetailsTmp'. Request denied.

Cannot select a record in Product Label Group Table (LabelGroupDetailsTmp).

Access Denied: You do not have sufficient authorization to modify data in database.

i user is given the Admin rights in the system there is no error and report displays correctly.

i cannot find any way to fix this? any suggestions?

• POSTED BY RICKY SCOTT  ON 25 JUN 2012 7:16 PM SUGGESTED ANSWER

  Hi Maxim. Looks like you don't have permissions to the table in question and/or that custom table isn't part of a Privilege. Add your table to the proper privilege and your report should run.

Security Permissions Properties for a SSRS Report [AX 2012]

Overview

1. Modifying a report query based on the input data
2. Modifying report contract data based on the input data
3. Control a report parameters dialog
4. Open different reports/designs from the same menu item based on the input data
5. Reports that are opened from a form

Prerequisites

1. Microsoft Dynamics AX 2012
2. Reporting services extensions must be installed in Dynamics AX

Sample Controller Class

1. Create a new class. Open AOT → Classes
2. Right Click on Classes and select New Class. Name it as SSRSDemoController.



3. Open the Class declaration by right clicking on it and selecting View code.

 
4. Now write the following code:
1 2 3 4 5

classSSRSDemoControllerextendsSrsReportRunController   {   }

5. Create a new method and write the following code:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

publicstaticclient voidmain(Args args)   {   //define the new object for controller class   SSRSDemoController ssrsDemoController;   ssrsDemoController=newSSRSDemoController();   //pass the caller args to the controller   ssrsDemoController.parmArgs(args);   //set the report name and report design to run   ssrsDemoController.parmReportName(ssrsReportStr(SSRSSessionQuery,Design));   //execute the report   ssrsDemoController.startOperation();   }

Examples of Controller Class Usage

Based on different scenarios, different methods are overridden as shown in the following examples:

1. Modifying report query based on the input data

• Used in those scenarios where a report query needs to be modified based on the caller args parameters or recorded before the report parameter dialog is rendered.
• Override prePromptModifyContract method to modify the report query as shown below:

• Used in those scenarios where report contract parameters need to be modified based on the caller args prior to the execution of the report.
• Override preRunModifyContract method to modify the report contract as shown below:

• In some scenarios, a report parameter dialog should not be visible to the end user. Controller class is also used to control the visibility of the report parameter UI.
• Add the following code in the main method of the controller class before startOperation method call to hide/show the report parameter UI:

• It is used in those scenarios where different reports or different designs of a same report need to be opened from a same menu item depending upon the caller args.
• Write the following code in main method to achieve this scenario:

• Controller class is also used when reports are opened from a form and are needed to show selected record details.
• Use either prePromptModifyContract method or preRunModifyContract method to achieve this scenario.

Overview

Pre-requisites

1. Microsoft Dynamics AX 2012
2. Visual studio 2012
3. SQL Server report server must be configured
4. Reporting services extensions must be installed in Dynamics AX

Steps

1. First of all we need an AOT query which will fetch data from AX and display it in a report. For this tutorial, I am using an existing query in AX which displays a list of customers.
2. CustTableListPage query will be used in this tutorial. To find this query, open AOT àQueriesàCustTableListPage.
3. The development of the SSRS report is done in Visual studio. So a new project needs to be created in Visual studio.
4. Open Visual studio. Go to File à New à Project.
5. In the section Installed templates select Microsoft Dynamics AX and then select Report Model in the right pane. Name the project “QueryBasedDemo“. Press OK.
   
   
   
   
   
   
6. A new project will be created as shown below:
   
   
7. Now add a new report in the project by right clicking on the project QueryBaseDemo à Add àReport.
   
   
   
   
   1. A report will be added to the project with the name “Report1″. Rename the report toQueryBasedDemo.
   2. Now double click the report to open it.
      
   
   
8. The description of the individual node is given below:
   1. Datasets: Datasets retrieve data from the AOT query. It acts as a bridge between AX and the SSRS report. Only the fields added in the datasets can be used in a report.
   2. Designs: It defines the layout of the report.
   3. Images: It contains the images that you want to display in the SSRS report.
   4. Data Methods: It contains the business logic which can then be used in the report.
   5. Parameters: It is used to apply filtering to the data in a report.
9. First of all, we will create a dataset. Right click Datasets àAdd Dataset to create a new Dataset. Name it “CustTable”.
   
   
   
   
10. Select the data source and open the properties window. Make sure the Data Source Type is set toQuery. Then select the Query field. An ellipse button appears. Click it to open a dialog.
    
    
11. This dialog lists all the queries present in the AOT. Select CustTableListPage and press Next.
    
    
12. Select the fields you want to display in the report and press OK. Only the selected fields in this dialog can be shown in the report.
    
    
13. There are two types of designs that can be created in a SSRS report:
    1. Auto Design: Visual studio automatically creates a design based on the dataset provided. Auto design is the preferred method because it is easy and usually fulfills the requirements for the majority of scenarios.
    2. Precision Design: It is used when you need custom placement of fields or the layout of the report is too complex.
14. In this demo we will use Auto Design. Now right click the Designs nodeàAdd àAuto Design. A new design is added. Rename it to Design. It is recommended that you set the name of the Design to either ‘Design’ or ‘Report’
15. Now drag CustTable form the Datasets node and drop it on the Design node. A table will be created which contain all the fields present in the data set. These fields will appear in the same order in the report. So if you want to arrange the fields, right click the field and select either move up or move down.
16. The final design will look as shown below
    
    
    
    
17. Now we have to define the layout of the report. Visual studio provides built in templates. Select the Design and open the properties window. Select ReportLayoutStyleTemplate in the LayoutTemplatefield. Give a suitable title to the report.
18. Select the CustTableTable under the Design node and open the properties window. SelectTableStyleAlternatingRowsTemplate in the Style Template field.
    
    
19. Report is now completed can be viewed. To preview the report, select the Design node, right click it and select preview. A preview window opens.
    
    
20. Select Report tab. The report appears as shown below:
    
    
21. To view this report from AX, it needs to be added in the AOT and deployed at the report server.
22. Open the solution explorer and right click the project. Select Add QueryBasedDemo to AOT. This will add the report to the AOT. It will also add the project in the AOT with same name so if you want to modify the report in future, you can use that project.
    
    
23. Now open AOT in AX. Go to SSRS reports à Reports à QueryBasedDemo. Right click the QueryBasedDemo Report and select Deploy Element
24. A success message will appear if the report is successfully deployed.
25. To open the report in AX, a menu item is required. Create a menu item that will open the report from AX.
26. Go to Menu items à Output. Right click Output and select New Menu Item
27. Set the following properties on the menu item as shown below.
28. Right click the newly created menu item and select Open to view the report
29. A parameter form will open. If you want to add parameters to report, you can add it by clicking Select. Press Ok to continue.
30. The report is displayed as shown below.

• POSTED BY DANIEL ESSER  ON 5 OCT 2012 12:20 PM  VERIFIED ANSWER VERIFIED BY PEDRO RODRIGUEZ

  I think user input are defined as filters in the query.

  try this:

  static void getQueryRanges2(Args _args)
  {
   Query query;
   QueryRun queryRun;
   QueryBuildDataSource qbd;
   QueryBuildRange range;
   QueryFilter filter; int cnt, filtercnt, i,j, k;
   DictTable dictTable;
   DictField dictField; str fieldLabel;
   ;
   query = new query(queryStr(smmSalesCustItemStatistics));
   queryRun = new QueryRun(query);
   queryRun.prompt();
   query = queryRun.query();  for(i = 1; i <= query.dataSourceCount(); i++)
   {
      cnt = query.dataSourceNo(i).rangeCount();
      filtercnt = 0;    if(!query.dataSourceNo(i).embedded())
      {
          filtercnt = query.queryFilterCount(query.dataSourceNo(i));
      }
      dictTable = new DictTable(query.dataSourceNo(i).table());     for (k=1; k<= filtercnt; k++)
      {
          filter = query.queryFilter(k, query.dataSourceNo(i));
          dictField = new DictField(query.dataSourceNo(i).table(), fieldname2id(query.dataSourceNo(i).table(), filter.field()));
          info (strFmt("%1, %2. Range = %3", dictTable.label(), dictField.label(), filter.value()));
      }    for (j=1; j<=cnt; j++)
      {
          range = queryRun.query().dataSourceNo(i).range(j);
          dictField = new DictField(query.dataSourceNo(i).table(), fieldname2id( query.dataSourceNo(i).table(), range.AOTname()));
          if(range.value())
          {
              info(strfmt("%1, %2. Range = %3",dictTable.label(), dictField.label(), range.value()));
          }
      }
   }
  }

  
  

  Reply

• POSTED BY MARTIN DRÁB  ON 5 OCT 2012 6:36 AM

  You need the actual query used in the report (ReportRun.query()), not just the query as defined in AOT.

  Martin "Goshoom" Dráb | UK/Czech rep. | Goshoom.NET Dev Blog

          

  Reply
• POSTED BY DANIEL ESSER  ON 5 OCT 2012 12:20 PM  VERIFIED ANSWER VERIFIED BY PEDRO RODRIGUEZ

  I think user input are defined as filters in the query.

  try this:

  static void getQueryRanges2(Args _args)
  {
   Query query;
   QueryRun queryRun;
   QueryBuildDataSource qbd;
   QueryBuildRange range;
   QueryFilter filter; int cnt, filtercnt, i,j, k;
   DictTable dictTable;
   DictField dictField; str fieldLabel;
   ;
   query = new query(queryStr(smmSalesCustItemStatistics));
   queryRun = new QueryRun(query);
   queryRun.prompt();
   query = queryRun.query();  for(i = 1; i <= query.dataSourceCount(); i++)
   {
      cnt = query.dataSourceNo(i).rangeCount();
      filtercnt = 0;    if(!query.dataSourceNo(i).embedded())
      {
          filtercnt = query.queryFilterCount(query.dataSourceNo(i));
      }
      dictTable = new DictTable(query.dataSourceNo(i).table());     for (k=1; k<= filtercnt; k++)
      {
          filter = query.queryFilter(k, query.dataSourceNo(i));
          dictField = new DictField(query.dataSourceNo(i).table(), fieldname2id(query.dataSourceNo(i).table(), filter.field()));
          info (strFmt("%1, %2. Range = %3", dictTable.label(), dictField.label(), filter.value()));
      }    for (j=1; j<=cnt; j++)
      {
          range = queryRun.query().dataSourceNo(i).range(j);
          dictField = new DictField(query.dataSourceNo(i).table(), fieldname2id( query.dataSourceNo(i).table(), range.AOTname()));
          if(range.value())
          {
              info(strfmt("%1, %2. Range = %3",dictTable.label(), dictField.label(), range.value()));
          }
      }
   }
  }

  
  

  Reply
• POSTED BY PEDRO RODRIGUEZ  ON 5 OCT 2012 3:08 PM

  Thanks!