SAS Viya Copilot for Code Assistance in SAS Data and AI Studio
Recent Library Articles
In this post, we’ll take a look at how SAS Viya Copilot for Code Assistance can help with some of those everyday tasks: understanding code, improving it, and making changes more confidently—all without leaving the SAS Data and AI Studio environment.
Already a SAS Viya user? Then you know you’ve got a wealth of capabilities at your fingertips. We’ll explore those together, giving you access to all the insights you’ll need. Join us on December 10 at 11 a.m. ET.
Hi, I'm prepping for the SAS advanced credentials with the SAS certified advanced prep guide. I found two answer choices that look the same for the Chapter 6, Question 6, except for the position of the asterisk. The solution in the book states that the answer is d. But I think the answer should be c, select *, instead of select*. I wanted to ask other members what you think of this. Also, I was wondering whether there is an errata list of quiz questions for the advanced prep book similar to the base prep book. Thank you in advance! the two answer choices that look the same are:
... View more
In SAS Visual Investigator 2025.09, the Keyboard Shortcuts window (user menu > Keyboard Shortcuts) lists Save as Ctrl+S. However, when a user edits an object (for example, updates a text field in edit mode) and presses Ctrl+S, the object is not saved. Instead, the browser's "Save As" dialog opens and offers to download the web page. To save the changes, the user must click the Save button in the object toolbar.
Users who edit many objects every day are used to saving with Ctrl+S in other applications. They expect the same behavior in SAS Visual Investigator, especially because the shortcut appears in the Keyboard Shortcuts window.
Requested Functionality:
When an object is in edit mode, pressing Ctrl+S saves the object, the same as clicking the Save button.
The shortcut works both when the cursor is inside a field (text, multi-line text, rich text) and when the focus is elsewhere on the object.
SAS Visual Investigator handles Ctrl+S, so the browser's "Save As" dialog does not open.
Validations (for example, required fields) run as they do when the user clicks Save, and errors are shown in the same way.
If Save (Ctrl+S) in the Keyboard Shortcuts window is meant for a different area, please indicate in that window where the shortcut applies.
Business Value:
Saves time for users who edit objects many times a day, reduces the risk of losing changes, and avoids confusion when the browser's "Save As" dialog opens unexpectedly.
Expected Behavior:
Example: A user opens a report, clicks Edit, updates the Content field, and presses Ctrl+S. The report is saved, exactly as if the user clicked Save, and the browser's "Save As" dialog does not open.
Steps to Reproduce (current behavior):
Open the user menu and select Keyboard Shortcuts. Save is listed as Ctrl+S.
Open an existing object and click Edit.
Update a content field, for example add text to a text field.
Press Ctrl+S.
Result: The object is not saved. The browser's "Save As" dialog opens and shows the computer's Downloads folder. The user must close this dialog and click the Save button in the object toolbar to save the changes.
... View more
In SAS Visual Investigator 2025.09, when a user relates the current object to another object (Relate To > [entity type] > Search...), the Relate To dialog opens with an empty search field. The user must search for the target object again, even if they opened that same object a few moments earlier.
In daily investigation work, users often open a background document (for example, an intelligence report), read it, and then want to link it to a case or a person. Today they need to remember its ID or keywords and search for it again before they can create the relationship.
Requested Functionality:
In step 1 (Search) of the Relate To dialog, show a short list of objects of the selected entity type that the current user recently opened (for example, the last 10).
Allow the user to select an object from this list and continue directly to the Relationship Information step, without running a search.
Keep the existing search field, so the user can still search for any other object.
Show only objects the user has permission to view.
Business Value:
Saves time and reduces mistakes when linking objects, because users do not need to search again for an object they have just worked on. This is especially useful for investigators who create many relationships during the day.
Expected Behavior:
Example: A user opens report 4512 and reads it. Then the user opens case 60 and clicks Relate To > Report > Search... The dialog shows a "Recently opened" list with report 4512 at the top. The user selects it and continues to Relationship Information, with no search needed.
Below is a screenshot of the current Relate To dialog in our environment. It opens with an empty search field and no list of recently opened objects.
... View more
I have input data that is the output of a catalog list (IBM z/OS, IDCAMS). The utility lists information about datasets. For those not familiar with z/OS or catalogs, they're something like a directory. There's a master catalog, and it usually has an 'Alias' that directs searches for individual files to a specific user catalog (sub-directory). A utility called IDCAMS manages a lot of work related to catalogs. The LISTCAT output I am reading lists all dataset entries in a specific user catalog. I'm looking for ones related to a files with the first qualifier of 'TABCDE' and getting the volsers (disk volumes) the data resides on. There are several types of records in this output. For now, I'm only interested in the 'NONVSAM' and 'CLUSTER' records. Each observation will have multiple lines. That number will vary. Among the data I want are volume serial numbers. There can be more than one volumes in an observation. Most of the time, datasets (or files, whatever term you prefer) will be on just one volume but the example I put in the attached file has several volumes. After the last volume line are a couple of more lines that included 'ATTRIBUTE' and 'ASSOCIATIONS'. I have no interest in anything after the last volume record. How do I tell SAS I'm at the end of an observation? I think I should be able to look at what I'm calling Line_ID and if the value =: 'ATTR' or 'ASSOC' that I'm at the end of the observation, whatever comes next is a new possible observation. Thank you
... View more
I, To show a data decreasing or increasing, I try to put an arrow on a chart on visual analytics.
But in text, ican only put Measure, not text. There is someone who can help me please.
... View more