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 work for fact tables based on documentation.

I was using Excel as a workaround as I was not able to find a way to display the 'care days' column only one time for each vendor.

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 can isolate the "care days" for the date range, but the challenge is to integrate that value into the main report as a single row  for each vendor.

Thanks for any insights you may have on a solution.

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 indicates that the suppress column functionality does not apply to "facts" tables.

One report would create one key for each vendor/bill date based on the a concatenation of the date and other columns using the aggregate function ( MIN).

The main report would perform the concatenation for  each row.  Using a "case' statement, I can populate the column when the keys matched and leave the column null when there is no match.

The two programs were not producing the same date format so the match was not working.

I can report back either 4-20 or 4-21 after further testing.

Jim