All idea exchange posts in SAS Support Communities

Re: Add proc http examples to SAS Rest Api-site for developers - Status changed to: Suggestion Under Review

joeFurbee — Mon, 29 Apr 2024 17:39:33 GMT

This request has been made a couple of times in the past. We have a story in our backlog. It will get reviewed an prioritized.

Add proc http examples to SAS Rest Api-site for developers

MAGDN — Thu, 25 Apr 2024 14:51:52 GMT

The new (and former) site SAS for Developers does not contain proc http examples when using the rest api's

I think this is a great omission sincs many customers uses this api's from whitin.

Re: SAS option to run from cursor - Status changed to: Suggestion Closed

Wilbram-SAS — Wed, 24 Apr 2024 07:31:00 GMT

Thank you for your product suggestion for SAS Enterprise Guide. All focus is on completing integration with SAS Viya 4 and integration with new components in SAS Viya 4, like SAS Viya Workbench. We don't have any plans for adding any other new features in the foreseeable future.

SAS option to run from cursor

rsmith1 — Tue, 23 Apr 2024 08:31:52 GMT

Sometimes when a SAS program fails you only want to run from the failing point, it would be nice if there was the functionality in SAS EG to run from where the cursor is to the end of the program. At the moment you have to select the bottom half of the code which is a bit of a faff in a big program.

Re: How do I connect SharePoint file system to VIYA file system

umersyed — Tue, 16 Apr 2024 16:54:06 GMT

We are also looking to have this capability in place for our SAS Viya.

Git functionality within SAS Studio for Solaris OS

avi77 — Mon, 08 Apr 2024 20:08:51 GMT

Hi Team

We are big SAS customer running our SAS on Solaris OS. Currently GIT functionality with in SAS Studio is not supported for Solaris OS.

We need this feature.

Thank you

Re: The disposition list should contain only the button list that authorized by user's queue

Maarten_at_SAS — Fri, 05 Apr 2024 10:36:23 GMT

Thank you for submitting your request. A very similar request was submitted in the past and related stories were added to the AML and Visual Investigator product backlogs for future consideration.

If you have access to teh SAS JIRA system you can track these items by making yourself a follower to the following tickets:

[PMAML-210] FUNC_VIPL | Restrict dispositions by user group - SAS R&D JIRA

[PMVIPR-187] Restrict Dispositions by Users/Groups - SAS R&D JIRA

We have linked your request to these stories.

Thanks

Request: Improve Column Insertion interface in SAS-Viya/SAS Studio QUERY

Erik_W — Thu, 04 Apr 2024 19:13:37 GMT

Currently in the SAS-Viya/SAS Studio (Version Stable 2024.02) QUERY interface, it is difficult to control where new columns are inserted in the Query column listing.

The interface is set up for a user to drag a new column from the tables/Columns window on the left into the QUERY>SELECT>Columns Tab on the right for insertion. It highlights the row the user hovers over, but upon insertion, the new column is not inserted there. Instead it shows up at the bottom of the Query column listing. SAS Technical Support informs me this is the "expected" behavior in the current version.

Request:

Please improve this interface to allow users to insert new columns where they are desired in the overall Query column listing. i.e. provide ability to:

- Select where in the column listing to insert new column(s) and put them there when executed.

- Allow selection of multiple columns by holding SHIFT or CNTRL keys and selecting them. Then allow user to drag them to the desired position in the listing.

- When insertion/move occurs, leave the display showing the same section of the column listing so the user can confirm where they went. Currently, when a move is done, the entire listing changes to a different view so you have to go looking for what was done.

Global language setting in SAS VI / LEI

Michael_Steer — Thu, 04 Apr 2024 07:59:00 GMT

Date formatting in SAS VI / LEI is controlled by browser language settings. For example if your browser language setting is English UK then dates will be UK formatted in the UI. Whereas, if your browser language setting is English US then dates will be US formatted in the UI.

Clients don't always have access to change language settings on company laptops and therefore feel it would be beneficial for SAS VI / LEI to have a global language setting in VIYA / Environment Manager that automatically formats all dates to the preferred style of the client.

Re: Increase password standards for initial server-level policies for internal accounts

babusat06 — Wed, 03 Apr 2024 09:12:36 GMT

Hi Team,
Any further update on this request

Re: Introduce explicit pass-through option in Cloud Data Exchange - Status changed to: Suggestion Implemented

rhmthomson1 — Fri, 29 Mar 2024 10:48:07 GMT

As note below, method to do this is now documented at SAS Help Center: About PROC SQL and Explicit Pass-Through.

If any issues as noted on specific cases that dont work, please raise with support.

Re: Allow adding a note as metadata on a SAS data file

MattJans — Wed, 27 Mar 2024 18:07:21 GMT

Ooo! Thanks, @LinusH

Re: The disposition list should contain only the button list that authorized by user's queue

Wathana_S — Fri, 22 Mar 2024 08:34:39 GMT

The Disposition in Alert screen below.

Re: The restriction on Calendar control on VI10.8 (Review Time Period in AML8.3)

Maarten_at_SAS — Thu, 21 Mar 2024 13:29:25 GMT

Thank you for submitting your request. We appreciate and review all feedback we receive, but at this time we have decided not to move forward with this request. Due to the volume of requests, we are unable to implement every request, and have to prioritize those that will have the most impact to our customers and business. If you have additional details/information that was not originally part of the request that you believe should cause us to reconsider this decision, please resubmit.

The review time period allows investigators to indicate when their review activity started and when it ended. These dates are not driving the next review date. As we want to allow end users to indicate a start and end date in the past, in the case the update these fields afterwards, the solution must and does allow for this and not restricting the end user.

Re: View the CDD and AML Alert purpose should be only for review, not for disposition (AML8.3)

Maarten_at_SAS — Thu, 21 Mar 2024 13:21:13 GMT

Re: Introduce explicit pass-through option in Cloud Data Exchange

Patrick — Thu, 21 Mar 2024 01:01:23 GMT

@RichardHorgen Given that the double hop approach is now documented here I suggest you raise this issue with SAS Tech Support.

Make sure you are very clear when describing the behaviour you observe and the impact this has.

Re: The disposition list should contain only the button list that authorized by user's queue

ballardw — Wed, 20 Mar 2024 13:40:05 GMT

In case "disposition list" is used in more than one place you should provide a clear description of which SAS application, activity and/or windows this button applies to.

The disposition list should contain only the button list that authorized by user's queue

Wathana_S — Wed, 20 Mar 2024 11:52:29 GMT

The disposition list on Alert detail screen should contain only the list that authorized by user queue.

For example

The Manager group queue and Manager Employee queue are in the same Strategy. Our user expect that the disposition button list should be displayed only disposition of that user's queue. The attachment is the Manager's screen, our user expect that the gray button will not be displayed.

Re: Set group restriction on each workflow page on AML8.3

Wathana_S — Wed, 20 Mar 2024 08:45:31 GMT

We would refer to 'Manage Investigate and Search' screen, there is the workflow page which our user use to 'Cancel workflow'. Currently, we cannot select the authorization settings to separate AML and CDD user.

Example

We add the authorization for AML and CDD Manager to 'Cancel workflow' which is using workflow page in 'Manage Investigate and Search', anyway we cannot set the restriction for AML Manager and CDD manager according to their group.

Re: Introduce explicit pass-through option in Cloud Data Exchange

RichardHorgen — Wed, 20 Mar 2024 09:00:28 GMT

@rhmthomson1

The suggestion to use a "double hop" suggested by @Patrick works quite well for explicit pass-through that lifts data into SAS. However, when I try to perform an execute( -statement it seems this approach has some shortcomings.

The following execute statement works in terms of creating a table on the Teradata-server we have, but when the table is created the session still runs as the cde-engine does not allow me to add "disconnect from teradata" into the inner execute-statement.

proc sql;
connect to cde (dataAgentName="cde" dsn=teradata bulkload=yes );
execute(
execute(
CREATE MULTISET TABLE v.newTable AS (
SELECT

from x.OldTable

)with data;

) by teradata;
/* disconnect from teradata; */
) by cde;
disconnect from cde;
%put &sqlxmsg;
%put &sqlxrc;
quit;