ICRW troubleshooting quick tips
This topic provides quick tips for some common issues that you might encounter with Interactive Custom Report Writer (ICRW) reports.
| Subscription | Interactive Custom Report Writer
Platform Services |
|---|---|
| Regional availability |
All regions |
| User type | Interactive Custom Report Writer: Business, Project Manager |
| Permissions |
Interactive Custom Report Writer: Run, List, View, Add, Edit, Delete Platform Services: Run, List, View, Add, Edit, Delete
|
Some user-defined dimensions (UDDs) don't appear in a report while other UDDs with the same configuration do appear.
This problem occurs after a UDD has been deleted and you create an exact replica of the UDD that was deleted. ICRW will not recognize the newly created copy of a deleted UDD.
Workaround: Create a new UDD with unique specifications to replace the deleted UDD.
In many cases, slow-running reports are a result of where the report designer pulled the columns from in ICRW. Whenever possible, use columns from the 'Attributes' or 'Measures' folders within the reporting area.
For example, in the Attributes folder of the GL Detail reporting area, there is a column called Location ID [General Ledger Detail]. The same column is also located under Dimensions...Location and is called ID [Location]. A report that uses the column from the Attributes folder, in many cases, will run significantly faster than an otherwise identical report that uses the same column from the Dimensions folder.
A dashboard filter won't show results for one project, yet shows results for other projects. Upon inspection, the project with the issue had an excessive number of filter values.
The list of values generated by the dashboard filter can't exceed the maximum number of values (100) that can be passed to ICRW.
ICRW automatically trims off any trailing blank spaces at the end of a name (job, vendor, etc.). When you filter on a name that ends with a trailing space, the filter does not return any results. It's recommended that you do not include trailing blank spaces at the end of any names in your data.
If you are editing an ICRW report created with custom SQL, the results might not change as expected. Typically this is due to the return of cached results. You can verify and change the cache setting in the following ways:
-
Open ICRW , find the report in the list and select Advanced Settings. Then scroll to Refresh Cache, select Always Refresh, and Save the report.
-
Go to the Custom tab, look for the cacheControl=”bypassCache” string in the top line of XML. This string indicates that the Always Refresh option is set. If you do not see the string, add cacheControl=”bypassCache” at the end of the first line of XML, left of the >, as shown in the following example. Then select Apply XML and Save the report.
<saw:report xmlns:saw="com.test.analytics.web/report/v2.1" xmlns:sawx="com.test.analytics.web/expression/v2.1" xmlns:xsi=http://www.test.org/2023/XMLSchema-instance xmlns:xsd=http://www.test.org/2023/XMLSchema xmlVersion="2" cacheControl="bypassCache">
For more information, see Use Apply XML to modify custom SQL reports.
An error message points to a problem located near a string in the Report XML. However, when you search for that string you find multiple occurrences and don't know how to identify the one associated with the error.
In ICRW, column names are not case sensitive. ICRW treats all versions of a column alias as the same, whether it's CustVend, custvend, or cUsTvEnD. However, the error message shows the string exactly as it is spelled in the SQL.
To identify a specific occurrence of a string, such as CustVend, change the spelling in the report so that each occurrence has a different (case sensitive) spelling. For example, you would change the occurrences of Custvend to CUstvend, CUStvend, CUSTvend, and so forth. Then when the error message is displayed, the string in the error appears exactly as spelled in the SQL, pinpointing the location of the error.
Interactive Custom Report Writer might time out sooner than your company timeout settings. This is because the ICRW default timeout is 1 hour. Make sure to frequently save your report.
Use Run Interactive to run ICRW reports that use filters on concatenated fields.
An Interactive Custom Report Writer filter returns incorrect results, or no results at all. This can happen when one or more fields used by the filter changes after the ICRW filter was created. Edit the filter, delete the fields that are not working correctly and reapply a newer version of each problematic field.
For information on how to solve other problems you might encounter with filters, see Troubleshooting report filters.
When you make multiple changes to a report, the cache increases. If the cache fills up and is unable to accept any more changes, you receive an error. You can avoid this by frequently saving your report.
Browser cookies can prevent Interactive Custom Report Writer reports from displaying correctly. For example, column names for dimensions display incorrectly or reports do not appear upon editing or running. If you try to run or edit a report and the report does not display correctly, remove the -crw.intacct.com cookies from your browser.
When you export a report to Excel, the maximum number of rows that are exported is 65,000. You can export a report to CSV format which has a maximum of 500,000 rows.
When you run a report that contains standard periods and the report is memorized, scheduled, or part of a report group, the generated report produces incorrect results.
To fix this, edit the report and remove the standard period filter. Then add a date calculation on a date column.
Add a runtime prompt on a date column
A date prompt provides users with the option to run a report for a specified date range or a selected period, such as month or year. You can add a runtime prompt on any date column included in a report.
See Runtime prompts on date columns for information about runtime prompts.
Add a filter on a date column
Using filters can help to limit data to the specific criteria you choose for a date column. See Filter a report by column—ICRW for information about filtering a report.
Add a filter to a column to display all the entries with the Entry Date between January 1, 2023 and January 1, 2024. Set the following values for the filter:
| Filter | Value |
|---|---|
| Operator | is between |
| First Value | 01/01/2023 |
| Second Value | 01/01/2024 |
Add a date calculation filter on a date column
You can add a date calculation filter to a column if you want specific calendar results. For example, you can add the "first day of the year" or "last day of the current month" to the report. See Work with ICRW calculation columns for information about calculated columns and Example calculations—ICRWfor example calendar functions.
Report names should be unique between ICRW and IVE. If you create an ICRW report with the same name as a visual board in IVE, you receive a notification that the report name already exists in IVE. Enter a new name that does not exist in IVE.