We're using SAS 3.5 VIYA; user's account account are from our company LDAP. When a user connect to our SAS, due to LDAP specificity, the account domain may be lower case our upper case (depending from connection method) This is currently not handled by SAS: some functions are case sensitive, some other case insensitive. We suggest than adding a configuration to manage this.   More details : case CS0064251 ... View more

There is any functionality to enable 'CLICK TO COPY TO CLIPBOARD' for transaction fields in SAS FM UI.  Right now Ctrl+C or right click to copy is working. However, its request from business user .   Please suggest   Kindly find the screenshot, transaction file and contents needs to be copied using 'CLICK TO COPY TO CLIPBOARD' instead of Ctrl+C ... View more

I'm fairly consistent with how I set up my SQL joins and for some reason the auto-complete on the from line below, will expand to AS BETWEEN. I'm ending the line on AS B but the enter key always completes BETWEEN. I'm wondering if it would be possible to make an exception to the auto-complete in this common scenario and not have B autocomplete to BETWEEN. This is more of an annoyance but I could imagine how many folks are having the same issue.    PROC SQL; CREATE TABLE CM_STATS_JOIN AS SELECT A.*, B.CN AS TOTAL_CM FROM SW_STATS AS A LEFT JOIN CM_COMBINED AS B ON A.'PUBLIC HEALTH REGION'N=B.REGION; QUIT; ... View more

Microsoft does have its co-pilot, and there is IntelliSense (code suggestions as you code), but I think there can be something more profound.   Let's call it SAS Guru.   As you are coding in the various interfaces, SAS EG or SAS Studio I think you could score the code (maybe even using some statistics!) and when you find code that seems to be not efficient (such as repetition of terms, profoundly short variable names, lack of comments, lack of coding structures, long procedural style code, etc) you can send badly scored pieces of code in real time to a generative AI sidebar that can make real time contextual suggestions for code enhancements. "SAS Guru: It appears that this function is doing an average payment calculation consider renaming variable "c" to "cAvgPmt" for clarity." "SAS Guru: This code could be rewritten to enhance maintainability by creating variables for these values, and rewriting it with a %do loop, see this rewritten code suggestion...   %do ... "   Similarly, when leveraging a data access method or doing a proc sql / datastep you can send the query / datastep to AI to suggest enhancements.  When you do this though you can send in real time the underlying table configuration, etc, to give the best possible answer, ie. knowing the data types, knowing the database interface, knowing the table structure, understanding context of those structures (to suggest in db analytics) and knowing what is indexed.  (things that a non-integrated AI wouldn't be able to inherently glean) In the same vein it can know when you're merging data between data sources and suggest more optimal ways of doing it.   When code is running you could use AI to give an analysis of the log results or the overall code. (Build information about iterative run and present back that AI generated analysis) "SAS Guru: This run was faster than your last run, on December 3rd at 6am by 18 minutes, that's 10% faster, the performance of all successful runs to date is between 1 hour and 1.5 hours.  Your fastest runs occurred between 5pm and 6pm, and your slowest runs occurred in the mornings.   Your overall program took 45 minutes to run the 4th procedure (PROC SQL - ...) took the longest time (40m), it brought in 100 columns and 1m records, however your program only uses 35 of these columns and 20,000 rows.  (using AI to suggest a resolution)   First Consider Using mod(account_number,50)=0 in the WHERE close to build a sample set without importing all the data.   Next Consider Updating the select with these (...used columns...) will drop your data import by approximately 70%.  Consider moving your 6th procedure into the "whatever database" using this suggested code rewrite, this will save 6 minutes and reduce your data import by 20%.   I'm a performance guy you could definitely use this to suggest parameters to functions, or better functions, etc.   If using AI is a stretch, doing some post analysis/suggestion based on the log (or iterative logs) would be a really nice enhancement. ... View more

Recently, to resolve issues that I have encountered with Viya 3.5, I have had to add multiple entries into the logging.level definition, to generate debugging information in various logs.  After the issues were resolved I had to set the logging level for each new configuration item to OFF.  I was surprised to discover that there was no way to delete the items.  This seems like a needed feature, the ability to delete configuration items in general, if not from the logging.level specifically.   Thank you. ... View more

What Model Manager is missing Information about the state of the VTA Project configuration (e.g. Concept Definitions) at time of model registration. Once a model is registered, cannot change the VTA project config that feeds that specific model. If a VTA project is changed after the model has been registered, no way to revert state of the VTA project to bring it back to the time of model registration. Ability to generate scoring results in “offset” format (this might be a possibility, but not from what we’ve seen) Would require additional development & processing time overhead to manipulate scored output into a useable format ... View more

Third party tools like Sonar Cloud do not offer SAS code connectors, that means that it is not possible  to review customized SAS code on vulnerabilities and or quality. To be sure that we deploy and expose secure code it would be beneficial to have a code review tool from SAS.      ... View more

Hello everyone One of our main customers complains about the difficulty of reading the name of the reports in the Open New Report window. This is because the "Name" column where we have the list of reports is very small and to find a correct one to open, we have to manually adjust the width of the column. My suggestion is that the "Name" column in the Visual Analytics "Open" window is automatically adjusted in size so that you can see the full name of the reports   Grazie Michele ... View more

Visualisation tools such as Tableau, allow a drop down list that is multi select, and has a text search box within it. Can this be implemented for SAS VA. The current List Control in SAS VA is not design friendly on a dashboard, as it takes up too much space, and cannot be text searched. In Tableau, a dashboard could have 10 or more drop down lists in a small area of the dashboard, because they collapse, and are useful for finding an ... View more

PROC SGPANEL is a module with deficits. First, the user cannot specify the number of graphs in each row. Second, the graphs are automatically left-justified, with no way to correct them in the module. It is therefore especially embarrassing when I am putting five graphs in one panel. PROC SGPANEL automatically assigns three graphs in the first row and two in the second. I cannot change the arrangement into two in the first and three in the second row. What is more embarrassing is that the graphs in the second panel are automatically left-justified and there is no way I can tell SAS to change the alignment the graphs in the second row to middle-justified in PROC SGPANEL. What is more, PROC SGPANEL seems to be the only module capable of putting multiple graphs in one panel when there is no way of drawing them in statistical analytic modules. In fact, I am drawing calibration plots of logistic regression models. With an older SAS version (TS1M5), I cannot do this in PROC LOGISTIC, so PROC SGPLOT and PROC SGPANEL are the only two modules I can resort to. But PROC SGPLOT does not support putting graphs in panels while PROC SGPANEL does not support the functions I mentioned above. It is really frustrating. ... View more

The CALL SORTN Routine sorts array elements in the DATA-step.   Suggestion:  Implement a faster CALL SORTN routine. There are discussions in SAS Forums about this -   "the Quicksort Algorithm. The quicksort algorithm is popular, simple and very efficient.  Introduction here. The quicksort algorithm is cleverly implemented in the article Quicksorting An Array by Paul Dorfman. "   /Br AndersS (Anders Skollermo)   ... View more

Hi, we are running SAS 9.4 (TS1M7) on z/OS 2.5. We use the FILENAME statement to allocate a concatenation of datasets under the same fileref. The SAS limit for the number of concatenated datasets under the same fileref is 200. (see https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/hosto390/n0yrspsfthx1w5n1gyt6rgzh3qsu.htm ) Would it be possible for SAS to extend that to a larger limit in a future release please? I think the limit has been 200 for a long time now and 200 datasets is not that many nowadays. Thanks. ... View more

Hi, It will be helpful to be able to reach data from alerting_evet table in Visual Investigator. There is a crucial need to develop an API that these tables will be able to "talk-each-other" in order to implement use-cases of workflow(s) to be routed successfully as the end-user defines.   For example, I'm struggle to retrieve data on scenarios that emerge as an alert. I understand that different scenarios could raise an individual alert, but most of the time the alert that generated a scenario event with the higher score is the one that users want to know and to be routed by it.   Thanks ... View more

Dear all! There should be a possibility to have piece of sas code included in several process flows. Currently this is actively inhibited by EG (at least as of 8.2) and there does not seem to be a real reason for this restriction ... and yes, there is%include but this is not always applicable in certain setups/environments. Cheers ... View more

Dear all! I would really fancy the opportunity of customizing the fonts used in dialogs. I find the font used in the query builder for advanced expressions expecially hard to read. Cheers ... View more

Dear community!   It appears to me, that the use of modal dialogs/windows in EG is unneccessarily high and could be reduced. This bites you when you need to look up information in some other part of EG to fill in a form in the foreground.   Cheers Fja ... View more

Sometimes you accidentally open one or more pieces of code into EG and they appear in the wrong process flow. Why can't you items between one process flow and another? ... View more

HI, you should be able to export from an EG project file stored processes, including prompts, to a file (a SAS package?), and then reimport it into another project, prompts intact. It seems like a pretty strange oversight that you can't do this. ... View more

    Hi all,   I know I've not that much experience, in the whole SAS environment and in SAS programming too but, since the time I started working with SAS EG projects, looking into SAS Community and in the net, I'm seeing a lot of questions (and great confusion, where I can also add mine) about "type casting", an area where, in other languages like C, there is no confusion at all: nearly all mature languages have their own typecast functions, explicit (java, C, etc.) or implicit (python) which "take care" to make the data having a "safe landing" into the target variables (or throw errors, if impossible or leads to data loss).   What I mean is: if some topic, main documentation apart, needs a so broad amount of "guides" and documents further explaining it (which I really never seen, in all my life, among other languages) there should be something wrong in the way it have been thought: apart the initial read I gave to the docs, I never needed to further read how to cast an int into a long, or have to take personally care about how var(string_value) decided to work on "3,14" to have 3.14 assigned to my num_short_pi numeric variable.   While using SAS I'm constantly banging my head against "typecast walls", all the time having to PUT something into my INPUT to have it converted etc. etc... so, after some time (as I initially thought it was my problem), I asked to myself "why not having an "intelligent typecast" function, which reads the source variable's type and, working behind the scenes, converts it into my target variable wanted data type?"   Thus this proposal: I know there is a CAST() function already but, from the few I read, it seems more related to proc sql (and even not all of it: works into FEDSQL), the proposal is to have it available "everywhere" (so even outside PROC SQL), in base SAS, as an alternative to PUT/INPUT. Then, with time, if SAS devs will see users using it more than original PUT/INPUT, they could decide to keep CAST only... or to remove it if, to the contrary, it won't be used at all.   Syntax: CAST(source variable, target variable, target variable desired type, [target variable format]);   source variable: any type (numeric or char) source variable name target variable: target variable name target variable desired type: wanted target type (numeric or char), if not defined before (optional) target variable format: the target format to apply to target variable desired type   As I'm not a SAS expert, even if I believe there shouldn't be problems in converting char-to-num or num-to-char, some problems could arise: this is why I wrote "target variable desired type": if desired type can't be achieved, e.g. there is data loss in the conversion, a warning should be raised, if the conversion can't take place at all, an error should be raised. As I told, I'm no expert, so feel free to improve this proposal with your expertise, which it's for sure far greather than mine. ... View more