SAS® Studio flows migrated from SAS® Enterprise Guide® projects might contain libraries that do not exist


An issue occurs with SAS® Studio 2022.11 and earlier flows in scenarios similar to the following.

You migrate a SAS Enterprise Guide project (.egp) that you created with a version earlier than SAS® Enterprise Guide® 8.6 to SAS Studio on SAS® Viya® 202x. The SAS Enterprise Guide project contains data sets that are located in libraries with different names than their librefs.

Importing the project on SAS Viya 202x completes successfully. However, the SAS Studio flow might contain tables located in libraries that do not exist.

Here is an example:

The following SAS Enterprise Guide project contains a data set located in the testData library. The name of the libref is testD.

A dataset located in the testData library and a libref named testD.

On SAS Viya 202x, the SAS Compute Server does not support projects with different library names and librefs. You can define only a library (not a libref) with a name that is no longer than eight characters. In this example, on SAS Viya 202x, the library contains a name equal to the SAS9.x libref “testD”.

The library contains a name equal to the SAS9.x libref “testD”.

However, when importing the SAS Enterprise Guide project on SAS Viya 202x, after you open the SAS Studio flow, the name of the library is displayed in the Table Properties instead of the name of the libref.

Consequently, in the SAS Studio flow, tables might be located in a library that does NOT exist.

"No columns were found. The table defined in the Table Properties may not exist yet."

Workaround

To work around this issue, do as follows:

    1. Open the SAS Enterprise Guide project in SAS Enterprise Guide 8.6.
    2. Establish a connection to the workspace server where the data is defined. You can establish the connection by running the flow, opening the data, or connecting to the workspace server through the Servers pane.
    3. Save the project.