Facing issue loading and unloading the Datatable in SAS VA

[SatishR]

Hi Team,

I have scheduled below code to load and unload the data in caslib

PROC CASUTIL;
droptable CASDATA="Event_calltype_analysis_rpt"
INCASLIB="Mers_Report";
QUIT;

proc casutil;
load data=Report.Event_calltype_analysis_rpt promote; /* 2 */
contents casdata="Event_calltype_analysis_rpt";
run;

However, whenever I used above code to load the data then my Marathi font data got missing while visualisation data. I have attached snap of this scenario.

And whenever I am doing data loading by manually then this data reflecting properly.

why this happening. (same screenshot attached. This is expected output)

[Madelyn_SAS]

If you run the code and then view the loaded table in SAS Studio, do you see the same problem? 

Also, what are you doing when you load the data manually, and which version of  Visual Analytics are you using? 

[SatishR]

After Loading data from SAS Studio  then only I am facing issue. since I am using SAS 8.5.2 Version of SAS VA.

For Manual loading of data,  I am unloading first from Manage Data Tab,

then load same table.

Hope you are understood the my concern.

[BrunoMueller]

In the code provided you are loading from a SAS library (load data=). If you do it in the visual interface, you are loading from the caslib physical level (in CAS called file).

So I would change the code similar to this:

proc casutil;
  droptable incaslib="casuser" casdata="sugus_citiday" quiet;
run;
  load
    incaslib="casuser" casdata="SUGUS_CITIDAY.sashdat"
    outcaslib="casuser" casout="sugus_citiday"
    promote
  ;
run;
quit;

You will need to adapt it to your case: caslib name, file to load, name of CAS table. Please note for the casdata= option the file name is case sensitive. You can use this code to see all the files in a caslib:

proc casutil;
  list files incaslib="casuser";
run;
quit;

[Patrick]

Your code drops and re-creates the table in CAS. 

With a VA report linked to a CAS table I wouldn't re-create it but truncate it instead before re-loading. Truncate Table CAS Action

Not sure if this will resolve the issue you're facing but I'd consider truncate instead of drop "best practice" for your use case.