DeepSee has a pretty good Developer Tutorial in the Documentation. This is a very good place to start. There are also the "HoleFoods" and "Patients" cubes in the SAMPLES namespace that you can take a look at and play around with to see some of the basic features of DeepSee

Documentation says that if you use Target=* on your print PDF control, you can "print your dashboard". This option will simply create one PDF that contains each of your widgets printed as they would normally print. So if you are looking for 1 PDF, this may be the option for you. If you want to save an exact copy of what you see on your dashboard, as Alessandro points out, the browser Print option may be best.

I am not sure if you have already explored this or if you had a print control on each widget previously.

Hi Derrek,

I suggest taking a look at the IIF Documentation. I think this is what you are looking for. Here is an example:

>> WITH MEMBER [Measures].[TestIIF] As 'IIF((([Measures].[Amount Sold]>500) AND ([Measures].[Amount Sold]<3000)),[Measures].[Amount Sold],"")' SELECT {[Measures].[Amount Sold],[Measures].[TestIIF]} on 0,NON EMPTY [Product].[P1].[Product Category].Members ON 1 FROM [HOLEFOODS]
 
                             Revenue              TestIIF
1 Candy                       $162.49                    *
2 Cereal                      $402.61                    *
3 Dairy                       $105.95                    *
4 Fruit                       $977.62               977.62
5 Pasta                     $1,408.68             1,408.68
6 Seafood                     $238.70                    *
7 Snack                     $4,195.20                    *
8 Vegetable                   $552.95               552.95

Unfortunately, from what I can tell, it does not seem like we parse the TARGET setting. This means that if you want to apply the setting to multiple Widgets, you will need to create multiple SETTINGS parameters

basic_dashboard_url&SETTINGS=...;&SETTINGS=...;&SETTINGS=...;...;

This being said, if you want the setting applied to ALL widgets, removing TARGET will apply the setting to all widgets. You can also set TARGET=* to apply to all widgets as well.

Hi Derrek,

I generally recommend using the "All Member". This will allow the proper aggregation function from the measure to be applied to your total. This may cause your % of Total to not display the desired results and you may be required to create a new measure to display the % of Total instead of using the column summary option. The summary options will base their results on the data inside of the table, not on the data behind the table. In some basic cases, they summary options will give the desired results, but in more complicated queries, they will not.

Have you tried creating a "Searchable Measure"? This may partially solve your problem. Checking the "Searchable" option in Architect for a measure will make the measure available within a Named Filter. It will also allow you to create a filter control on a widget with the measure.

This is not available for calculated measures because creating a "Searchable" measure creates a special index on that measure (this index is populated at build/synchronize time).

Samuel is correct, using NOW-1 on a Day level will give you the information from yesterday.

For the second part, please see the following two queries:

>>select PERIODSTODATE([DateOfSale].[Actual].[MonthSold],[DateOfSale].[Actual].[DaySold].[NOW]) on 1 from HOLEFOODS
 
 
1 Mar 1 2017                              *
2 Mar 2 2017                              *
3 Mar 3 2017                              *
4 Mar 4 2017                              *
5 Mar 5 2017                              *
6 Mar 6 2017                              *
7 Mar 7 2017                              *
---------------------------------------------------------------------------
Elapsed time:       .009242s
>>select COUNT(PERIODSTODATE([DateOfSale].[Actual].[MonthSold],[DateOfSale].[Actual].[DaySold].[NOW])) on 1 from HOLEFOODS
 
 
COUNT                                     7
---------------------------------------------------------------------------
Elapsed time:       .006043s