I don't like the duplicate metadata registration.   I built my own (very limited) table loader transformation to: - skip unmapped columns - optionally add the NOWARN option to PROC APPEND   For what it's worth, the code I currently have (which will surely evolve when I find errors in it and need additional options).   %macro x; %let rc = 0; %if (&loadstyle = REPLACE_DROP) %then %do; %if (&_OUTPUT_engine. = SAS) %then %do; proc sql; drop table &_OUTPUT.; quit; %end; %else %do; %put ERROR: REPLACE_DROP is only allowed for SAS data sets.; %let rc = 4; %end; %end; %if (&loadstyle = REPLACE_DELETE) %then %do; proc sql; delete * from &_OUTPUT.; quit; %let rc = &sqlrc; %end; %if (&loadstyle = REPLACE_TRUNCATE) %then %do; %if (&_OUTPUT_engine. = POSTGRES) %then %do; data _null_; call symput('postgres_table',strip(scan(scan(symget('_OUTPUT'),2,'.'),1,'"'))); run; %put NOTE: &=POSTGRES_TABLE; proc sql; connect to postgres (&_OUTPUT_connect); execute ( truncate "&POSTGRES_TABLE" ) by postgres; disconnect from postgres; quit; %let rc = &sqlrc; %end; %else %do; %put ERROR: REPLACE_TRUNCATE is only allowed for Postgres tables.; %let rc = 4; %end; %end; %if (&rc = 0) %then %do; proc datasets lib=WORK nolist nowarn; delete __LOAD; run; proc sql; create view WORK.__LOAD as select %let first = 1; %do i=0 %to %eval(&_OUTPUT_col_count. - 1); %if ((&&&_OUTPUT0_col&i._exp. ne ) or (&&&_OUTPUT0_col&i._input_count. > 0)) %then %do; %if (&first. ne 1) %then , ; %else %let first = 0; %if (&&&_OUTPUT0_col&i._exp. ne ) %then &&&_OUTPUT_col&i._exp; %else %if (&&&_OUTPUT0_col&i._input_count. > 0) %then &&&_OUTPUT_col&i._input; as &&&_OUTPUT_col&i._name %if (&&&_OUTPUT_col&i._type. = $) %then length=&&&_OUTPUT_col&i._length.; %if (&&&_OUTPUT_col&i._format. ne ) %then format=&&&_OUTPUT_col&i._format.; %if (&&&_OUTPUT_col&i._informat. ne ) %then informat=&&&_OUTPUT_col&i._informat.; %if (&&&_OUTPUT_col&i._label. ne ) %then label="&&&_OUTPUT_col&i._label."; %end; %end; from &_INPUT ; quit; proc append base=&_OUTPUT.( %let first = 1; %do i=0 %to %eval(&_OUTPUT_col_count. - 1); %if ((&&&_OUTPUT0_col&i._exp. eq ) and (&&&_OUTPUT0_col&i._input_count. = 0)) %then %do; %if (&first. = 1) %then %do; drop = %let first = 0; %end; &&&_OUTPUT_col&i._name %end; %end; ) data=WORK.__LOAD %if (%upcase(&warn) = NOWARN) %then NOWARN; ; run; %end; %mend x; options mprint; %x; ... View more

I tested a duplicate metadata registration of the Postgres table without the SERIAL column (__screening_id). This does not help (with proc append anyway), behind the scenes SAS queries the target table and generates Postgres SQL insert code for all columns:     POSTGRES_49: Prepared: on connection 4 INSERT INTO "DQ_SCREENINGS" ("__screening_id","__screen_id","__screening_job_run_id","__screening_object","__screening_dts","__screening_result","__screenin g_msg","__update_user","__update_dts") VALUES ( ? , ? , ? , ? , ? , ? , ? , ? , ? )   I tested IGNORE_READ_ONLY_COLUMNS=YES, which also did not work. It looks like SERIAL data type in Postgres is not read-only and so the libname engine does not recognize it as such.   What I found does work is specifying the (drop=serial_column) table option on the output dataset: The generated code is then:     proc append base = WIKCNTL."DQ_SCREENINGS"n(drop=__screening_id) data = &etls_lastTable (&etls_tableOptions) force ; run;     But then this gives a warning (unacceptable in our batch) and I can't find a way to have the table loader add the NOWARN option to PROC APPEND. Any (other) ideas? ... View more

Hi,   I have one 94M3 environment that does not allow two domains with the same login without setting Outbound to Yes. I have another 94M3 environment that does allow two domains with the same login without setting Outbound to Yes.   What can be the difference?   Bart     ... View more

Hi Juan,   Thanks but that is still not what i want because then i must do this manually for every new table that any user loads. I want to do this programmatically, just like you can do interactively in the SAS VA Administrator hub by clicking all tables and selecting the Reload icon.   Looking in metadata I got pretty far, up to the point where the data query code is stored in SAS metadata and not being able to extract that from metadata.   Regards, Bart ... View more

Hi Juan,   I don't mean a data query as created through the prepare data application. I load a data set from the SAS VA Administration application (RMB on table-> Load a Table...) For this action, VA creates a Visual data query that it stores alongside the LASR table metadata registration. It is also this data query that is executed when i click Reload on the table in the LASR Table webpage.   It is this data query that i want to obtain the SAS code from, programmatically.   Thanks, Bart ... View more