Last week I provided the steps for how to go on a date, at least by using dynamic prompts in BI Dashboard. Now that you have seen how to create them, lets discuss making them smarter. For this example, the customer is asking for two prompts to affect a single
Wizard Harry Potter makes magic just waving his wand around and shouting out spells. Using SAS Enterprise Guide (and you are welcome to shout out your own commands too) you can create some magic, allowing the Stored Process Wizard to code for you. On Step 2, the "Include code for"
Stored process code can exist within the metadata itself for version 9.3 (the benefits of which I discussed earlier). But for all other versions (and as a option in version 9.3) the SAS code is stored as a .sas file within the server's file system (or mapped folder/drive structure). When editing
The date prompt from SAS Prompt Framework provides the options of single selection or a range, however what if you need to select multiple individual dates such as Monday (May 28), Wednesday (May 30), and Friday (June 1) of last week? There are a few alternatives to accomplishing this. Option
What if you would like to make a copy of an existing stored process to test out your changes before making them live? The copy command is available from within SAS Management Console or from the SAS Enterprise Guide Open Stored Process GUI as seen below (note you can only
This past Monday, Tricia and I released our 2nd book this year. "The 50 Keys to Learning SAS Stored Processes" provides a step-by-step approach to transitioning from SAS code into user driven (prompted) stored processes. Trimming down all the things you can do with SAS Stored Processes is next to
PROC STP is a new procedure for SAS 9.3 Stored Processes. It's so new and different that I have not had the opportunity to use it yet in a customer engagement. When writing about it for the now released "The 50 Keys to Learning SAS Stored Processes" book, I had
Functionality to upload files onto the SAS server (from 9.2 on) is available using stored processes and an html input type="file". I introduced this topic last year in my blog post using the SAS Stored Process Developer Guide sample. Of course, it is never as easy as the sample is
The ODS ExcelXP tagset is pretty powerful stuff. Hidding columns, changing the print layout to landscape, updating the spreadsheet names, defining the default column width and row height, etc - it's all available using options within the ExcelXP setup. So the best thing to do is grab some documentation. Fortunetly,
The %STPBegin and %STPEnd macros are pretty powerful pieces of code for SAS Stored Processes. They embed all sorts of information on devices, where content is located, and just make everything work. However for creating those fancy custom HTML forms or layouts, ods html is needed instead. I've written about
