Reports may need to focus on different data sets depending on who is running the report. To this effect the new reporting tool provides the "Ask User Later" option so that individual users can define their own criteria for a given filter. However this has one major drawback, the user cannot choose to ignore one or more filters which are not applicable to their reporting needs. For example, if a report is outputting billing information by account, depending on who is running the report they may want to filter by Account, Invoice, or Rate Plan Charge level information. By building these prompts into the report with the "Ask User Later" when the report is run, the user will get a pop-up something like this: However If a user is only interested in filtering by one of these fields, they cannot populate only one value ignoring the rest. Since all filters must have values (cannot be blank) and select lists do not have an All or None option this issue affects the report regardless of if the filter conditions are set using "AND" or "OR." If the filters are set with "AND" and any of the filter criteria are invalid, such as leaving the Source ID with the default "Enter Text," then the report will not return any results since there are no Bill Runs with the Source ID of "Enter Text." At the same time if the filters are set up using "OR," if any additional filters are valid, such as setting the Billing Batch to "Batch5" but leaving the Invoice Date as "Is during Current Month," it will include results based on all valid filters not just the one needed for the report. In the Old Reporting tool if a value was not set for a filter it was ignored as a condition. Since the new reporting tool requires a value for every filter, the solution here would seem to be to add a checkbox at runtime for each filter which has "Ask User Later" to allow the end user to ignore the filter condition for their report.
... View more
In the old reporting tool there was an option to have 0 or more values per filter and each one would be evaluated based on the filter Operator. This was critical to our business process as each user running a given report has different requirements for what they need in the results. Some users would require the report to provide all data from the system, and some would require anywhere from 1 - 100 filter values. In the new reporting tool the only way to have multiple values per filter is to use the "In" operator which requires an exact match, and if there is a filter a value must be entered to return results. This is a problem when the full value is unknown or if there are no filter values needed. eg. If I have 30 accounts which have variations of the same account name "Spam Eggs and Spam" and another 30 with variations of "Meridian Memories Photography." If I want to pull back all accounts which have "Eggs" or "Memories" in their names I would need to use the "Contains" filter on these words.In the current reporting tool I would be able to add both of these as Filter Values at Run-Time and would get a single report containing all 60 accounts. However since the new reporting tool only allows a single value to be used for the "Contains" operator, these would need to be run as separate reports. Alternately if I wanted to use this same report and return All accounts in the system, I would have no way to do so since if the filter is left blank the report will not return any results and there is no way to omit a filter at Run-Time. Since there is no way to know in advance how many filter values need to be added (or if they are needed at all), we need the ability to either leave the value blank or have multiple values for a filter regardless of the operator type or filter key.
... View more
If Gateway reconciliation is enabled on a tenant, and some job encountered an error, then in the reports done on the objet "Gateway Reconciliaition Job" it is implossible to display the jobs in error. Whatever the filter your are applying, you can show these jobs in error.
This could be interesting to have these job in the reports, and of course with additional informations regading the failure's cause.
... View more