Oh, I see. The problem is the nested operations when you have an aggregated measure (Distinct Count) in the expression. I think the best workaround is to pre-calculate the distinct count as part of your data preparation.   If you have the very latest version of VA (2024.05), you can work around this by calculating the distinct count as part of an expression-based parameter. ... View more

Hello,   Probably the issue is that your ID column has duplicate values. If you have permissions to perform data preparation tasks, then you could try generating a new ID column: https://go.documentation.sas.com/doc/en/dprepcdc/v_023/datastudioadv/n0ooiqdt13mn6sn1ejbeyv4ech8d.htm   It might also possible to create a calculated item with unique values within VA by concatenating your ID column with another one such as a date column. That would depend on your data.   You might want to create a list table of your data (including the ID column) and sort by frequency. That might help you find what the duplicates look like and determine how best to address them.   Let us know if that helps, Sam ... View more

As noted above, VA does not remove duplicates but it aggregates them.   If you want to see multiple instances of the same categorical values in a table in VA, enable "Detail data" on the Options pane. ... View more

Hello,   This is one of those things that feels more difficult than it should be. It is slightly easier in newer versions of VA.   The basic idea is that you will create a parameter that will store the selected date, and then use that parameter in an advanced filter in the target object(s). You do not want to put the selector control in the report prompt area or the page prompt area. It needs to be in the body of a page so that does not automatically act as a filter. (This would filter out everything but the selected month value.)   Due to some limitations, the filter selector needs to be something other than a slider control when a date parameter is assigned.   In the latest versions of VA you can use a filter expression like this: BetweenInclusive('Transaction Month'n, 'Parameter 1'p -31, 'Parameter 1'p) In 8.3 you would need a more cumbersome one:   ( 'Transaction Month'n BetweenInclusive(TreatAs(_Date_, ( TreatAs(_Number_, 'Parameter 1'p) - 31 )), 'Parameter 1'p) ) I don't have an 8.3 test environment at hand, but here it is in 8.5:   To be honest, I am a little confused about why this works as well as it does-- you would expect that subtracting 31 days from MAR2000 (which is treated as 01MAR2000) would include January because February only has 28 or 29 days. But as far as I can tell it is always returning only the desired "selected month and the one before".   A further workaround to make the filter selector a report-level control would be to filter on a second data source that is not mapped to the main one. That way you can set the parameter value but not perform automatic filtering.   Let us know if that helps. I can walk you through the steps in greater detail if needed.   Sam ... View more