The solution is to reorder the columns so that the column to be suppressed is among the leftmost columns in the output. This was mentioned in another submission on this forum.

Marco One discovery is that applying an aggregate formula to the date column converts it to the format YYYY/MM/DD HH:MM:SS Without applying the aggregate formula, the format is DD-MON-YY Jim

Marco Thanks for the note... The objective is to display a column ( "care days" ) only once for each vendor/billing date when there are multiple payment transactions for that vendor/bill date. Otherwise, the column is repeated with the same value and the aggregate value for the column is over stated. The documentation…

Christian The analysis generates 25+ output columns detailing payments to each vendor for a date range. There may be 25 payments to each vendor, but the requirement is to report the "care days" for that vendor/date range only once with the other rows showing null values to avoid overstating that value in the aggregate. I…

Christian The same column in both analyses. Note that the second analysis invokes the MIN aggregate function on the date column. This would allow me to identify one transaction among many payments to a vendor where I could display a 'care days' column only one time rather than repeating it. The 'suppress' option does not…

Christian The same column in both analyses. Note that the second analysis invokes the MIN aggregate function on the date column. This would allow me to identify one transaction among many payments to a vendor where I could display a 'care days' column only one time rather than repeating it. The 'suppress' option does not…

Each vendor will have multiple payment transactions for a given billing period that are visible in the report, but I only want to display the column in question( care days ) once for one of the transactions for that vendor/billing period. The other transactions for that vendor should show a null value for that column. Note…

I implemented the suggestion submitted by Christian and that works fine...thanks much !

My version # is 11.1.1.7 The suggestion to make 5 rows of 5 prompts each makes sense. I will plan on implementing that change and report back on 4-9...thanks much for the suggestion.

Jerry Thank you for your input !!! The alternative syntax you suggested that precedes the presentation variable name with the keywords "dashboard.variables" is working ! I am grateful for your insights ! Jim

Thanks for the quick responses... Note that I was using the correct syntax in troubleshooting this, but when I was embedding the screen capture of the dialog, I inadvertently typed the date value rather than the variable name. Therefore, the problem I am reporting is still an issue for me. I am including the correct screen…

Thanks for the feedback. I am waiting for the DBA to respond regarding access to the Admin tool I included the window where the presentation variable is defined and the filter window. Activity begins with M910 AND "CCRS Activity Monthly"."Activity Date" > TIMESTAMPADD(SQL_TSI_MONTH, -6, @{PV-START}{DATE'2010-11-11'})

I was away the week of 8-26. While waiting for action to be taken on the upgrade to version 12C, I am still troubleshooting the issues where I cannot refresh the analysis and the default parameters are overriding the values defined in the catalog object.

Unfortunately, I do not have a 12C test environment as you recommend.

Thank you for alerting me to the fact that the version I am using is obsolete. I reported that info to the DBA. My assumption is that the two issues I am troubleshooting would still be evident in he 12c version. The two issues being the inability to refresh the output and the filters not referencing the catalog object date…

In response to suggestions, I removed the "correct" response from my earlier thread. I am still requesting ideas on why modifying the presentation variables does not trigger the analysis to launch. I am also experiencing the scenario where the initial launch of the dashboard page is bypassing the presentation variable…

Thank you for your suggestions... I am using version 11.1 & the analyses are from the same subject area. Note that his discussion thread is related to an earlier discussion thread where the filters are based on earlier analyses. The objective is to identify customers who opened an account during a calendar window that…

I created a new dashboard and added the same analysis that was triggering a 'hang' condition in the other dashboard. The analysis launched successfully in the new dashboard. I am not sure what triggered the 'hang' condition in the other dashboard, but one factor may have been that the presentation variables were not…

I am still troubleshooting this issue. The logs provided by the DBA indicate that the request is not being forwarded to the server. I infer this due to the absence of entries generated by the OracleBIServerComponentt that show diagnostic messages with timestamps that are normally generated based on earlier logs I have…

Jerry I was able to implement the condition based on your instructions and it worked....thanks.