Currently (as of Viya 2026.10), a Data-Driven Content (DDC) object can interact with other objects only if they are on the same page (via Object Links). However, there are plenty of use cases where you may want to trigger actions on objects located on another report page (via Page Links), in another report (via Report Links), or even on another website (via URL Links). Let's look at the example with well-known sashelp.cars data. A) a page with native VA objects     vs.     B) a page using DDC objects Which one do you prefer? 😉 There is also a Detail page that provides additional information about a selected car. How can a user navigate to it? A) Double-clicking a car in the List table navigates the user to the Detail page (via Page Links). B) Double-click navigation is not available because DDC objects do not support Page Links. What a pity! To see it in action, watch this video.   An Ugly Workaround There is, of course, an ugly workaround. Since a DDC object cannot navigate directly to another report page, we need to put a native VA object in between. In our example, we use a Key Value object and configure it to look like a button. First, we use Object Links to trigger an action from the DDC object to the Key Value object. Then, we use Page Links to trigger an action from the Key Value object to the Detail page. With a few additional tricks, we configure the Key Value object to display its button label ("Go to Detail") only when exactly one car is selected. Otherwise, displaying the button would not make sense.   However, this workaround has several drawbacks: It is not intuitive from the user's perspective. The navigation mechanism is far from obvious. An ugly warning appears when no single car is selected. The button label is not displayed, but a small information icon appears with the message: "The key value encountered duplicate category values and cannot be displayed." The button is usually too big. It takes up too much screen space. You cannot set its height and width to less than 10%. It wastes screen space. You want to place the button close to the DDC object. However, since you do not want the button to be too large, you end up creating an empty space next to it as an unwanted side effect. The Feature Request Data-Driven Content (DDC) is a great feature that extends the visualization capabilities of SAS Visual Analytics and makes reports more appealing and engaging. I am sure that adding the ability to link DDC objects to other objects beyond the current page would make VA reports even more powerful and user-friendly. Please consider making Page Links, Report Links, and URL Links available for Data-Driven Content objects!   ... View more

Suppose you're building a logistic regression model to predict a binary outcome such as whether a patient has diabetes. How do you know whether age should enter the model as a simple linear term? How do you know whether body mass index needs a transformation?   These questions matter because the functional form of a predictor affects both model fit and predictive performance. Examining the shape of a predictor's relationship with the outcome can help determine whether a linear term, a quadratic term, or a more flexible approach is appropriate.   In this post, we'll use empirical logit plots to investigate the relationship between several predictors and diabetes status in the Pima data set. The results will help us decide which modeling strategy may be most appropriate for each predictor. ... View more

I open SAS.   I submit a macro (just submit it, so nothing happens except it puts the macro into memory).  A line in the macro points to a formats library.   I call the macro, so the guts of the macro runs.   When the macro runs it creates a dataset.  After running the macro I do a PROC FREQ on that dataset.  All the formats are applied correctly.   Then I call the macro again.  I do not submit the macro itself again, rather I just call (run) it.  I change nothing and I do nothing else.  All I do is call the macro a second time.   Then I do that same PROC FREQ mentioned above and this time some...not all, but some...of the formats are not applied.   So the 1st time I run the PROC FREQ I see all words (the formatted values) instead of their underlying numbers.   And the 2nd time I run the PROC FREQ I still see mostly words (the formatted values), but for some of them I see their underlying numbers instead.   And every subsequent time I run it I see the mostly words but some underlying numbers instead.   IOW, it works properly after I open a new SAS session and run it for the first time.   And it doesn't work properly every subsequent time I run it.   Any idea? ... View more

Join this webinar to explore the current capabilities of SAS®9 and plans for the upcoming SAS 9.4 M10 release.   You will learn about: Current SAS®9 capabilities. Product plans for the upcoming SAS 9.4 M10 release. The SAS 9.4 product strategy. Register Now ... View more

Join this webinar to explore the capabilities of SAS Viya and how to put them to work for you.   You will learn to: Understand the core qualities and basic architecture of SAS Viya. Use the suite of SAS Viya applications to manage and explore data, develop models and deploy insights. Develop code using either SAS or Python in SAS Viya. Use SAS Viya Copilot to accelerate development with AI-assisted code generation, explanations and productivity enhancements. Register Now ... View more