Ted,
Thanks for the reply and for passing it on to the team for review.
I am a bit concerned by the statement "PASS side it is targeting a more basic form of QR operation". IMHO there should be parity between PAX and PASS wrt any of the report types (QR or otherwise). This is critical because a disparity in capabilities causes a tremendous amount of trial-and-error discovery between them when developing reports.
In some cases, the development of a complex spreadsheet can take many hours to create, and then to find out it doesn't work when it is published, forces the user to track down the root cause. This is not always easy to do.
For example, in PAX, a dynamic report that has a DBRW formula which uses a value not in the TM1RPTTITLE of the TM1RPTVIEW function still renders properly. However in PASS, this is not the case. If the DBRW attempts to use a value outside of what is provided in the TM1RPTTITLE, it returns blank. With complex spreadsheets, this is very difficult to detect the source of the problem and users can spend hours, if not days, tracking it down. Oftentimes, people start creating the whole workbook over again, adding one step at a time to find out the root cause.
If you are going to allow DBRW in PAX to operate despite not being within TM1RPTTITLE, then do the same in PASS (or vice versa). Either way, make it consistent so that there isn't so much trial-and-error-testing involved.
Thanks again.
------------------------------
Steven Garno
Managing Partner
CarpeDatum Consulting
http://www.CarpeDatumInc.com------------------------------
Original Message:
Sent: Fri February 19, 2021 01:22 PM
From: Ted Phillips
Subject: Range Discrepancies between PAX and PASS for Quick Reports
PA Spreadsheet Services does not implement the full feature set of the existing Quick Reports technology, we are working to reconcile client support with the next version of Quick Reports to have stronger parity in both interfaces (PA Spreadsheet Services and PA for Excel). I'll make sure the feedback is passed along to the team to see about any interim relief/doc improvements, but on the PASS side it is targeting a more basic form of QR operation.
As always, forward facing statements are subject to change.
------------------------------
Ted Phillips
Original Message:
Sent: Thu February 18, 2021 12:03 PM
From: Steven Garno
Subject: Range Discrepancies between PAX and PASS for Quick Reports
I am having some troubles with differences in functionality between PAX and PASS regarding the treatment of named ranges for Quick Reports. Are any of these being addressed in the next release? (Currently I am using release 60 for Planning Analytics Local)
- PAX allows blank rows to exist within the named range, but PASS does not. The cellset stops updating at the first blank row.
- Manually updating the named ranges with full column (5:5) or full row (E:E) causes the sheet to not render in PASS (also happens if the named range is extends beyond what is populated i.e. NULL). I understand why this is the case, but can't this be determined based on where the sheet rows/columns end rather than just generate an error?
- PASS requires a sheet rebuild when changing the number of columns, but PAX does not. We need a way to specify on a sheet by sheet basis that a change in a dropdown Rebuilds (not just recalcs) a sheet.
- When changing the columns (based on a subset), from a smaller subset to a larger one, the cellset expands and fills in the screen properly. However, when going from a larger subset to a smaller subset, the data in the cellset remains. This works fine in PAX.
------------------------------
Steven Garno
Managing Partner
CarpeDatum Consulting
http://www.CarpeDatumInc.com
------------------------------
#PlanningAnalyticswithWatson