BookmarkSubscribeRSS Feed
Obsidian | Level 7

Dear colleague,


We know that SAS Content Assessment Report can be loaded into Viya4 and view the report in VA. The report's default location is in Public \ Content Assessment folder. Is it possible to load the report to another folder because of enhancing folder's authorisation? We do not want to put the reports and their data in the public area.


Does anyone have a similar experience and can share it with us?


Thank you.

Lapis Lazuli | Level 10

Hi @eddieleung305 ,


I have never tried changing the target caslib, but according to the importAssessment tool help below,

there is an option to choose a specific caslib instead of public :


#./importAssessedContent --help
 importAssessedContent - This application imports published tables and reports, assessed by SAS 9 Content Assessment, residing on the file system to SAS Viya 4 by datamart. Please note that any previously imported content from the specified data mart type will be overwritten by this process.


  importAssessedContent [command options...]

  Shows help.
  Specifies to prompt the user and create a SAS Viya command-line interface profile. Specifying this option will also result in the prompting for required values.
  Specifies a SAS Viya command-line interface profile to use during import. Specifying this option will also prompt the user for login credentials.
  Specifies the fully-qualified path to the SAS Viya Command-Line Interface.
  Specifies what type of data mart to publish. Valid values are: profile, inventory, codecheck, i18n, summarizelogs, embatchcode, appusage
  Specifies the destination caslib. Default value: public
  Specifies the destination CAS server. Default value: cas-shared-default
  Displays the application's version.

  This application makes use of the SAS Viya Command-Line Interface which can be downloaded from:

  After downloading the CLI, make sure to download its "CAS" plugin as well as its "transfer" plugin. See the "Additional Documentation" referenced below for more details.


Since it looks feasible to change your reports data caslib, you can also try to move the Assessement VA reports once created in Public folder into another folder, secured,

using VIYA Cli promote plugin :


Changing outright the destination Folder doesn't seem to be possible with the ImportAssessment tool (v 2023.04) ; posting a feature request to the team in charge might be useful also ;-).




Obsidian | Level 7

Hi all,


If I have more than one system and want to keep both system's reports and published data in a separate folder and caslib, does anyone have an idea how to do it?


I noticed that the importAssessContent will load the JSON file of the report in the package folder always has the same URI. So every time when running this command, the reports previously loaded into the system will be deleted and re-imported again.


As a result, the report location will be "reset" to SAS Contents > Public > SASContentAssessement.


Any suggestion I can do to keep both reports and data in different location?

The documentation seems to explicitly say this will overwrite any existing content assessment:

"The application overwrites any existing SAS Content Assessment data and reports."
Source: SAS Content Assessment - Executing the Import SAS Content Assessment Data and Reports Application - Details

The "Importing the Data Mart" section of the documentation mentions importing these manually through Environment Manager's import function:

Importing the Data Mart

Perhaps you could do that and specify the alternate paths / caslibs in the mapping?
Greg Wootton | Principal Systems Technical Support Engineer

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 3 replies
  • 1 like
  • 3 in conversation