Hi, Would like to insert content of small SAS table with one column into one excel cell, each of SAS tables row should be pasted directly after previous into one cell,manually it achives by ALT+ENTER (new line in excel, or char(10) in vba). But I would like not to use additional vba scripts for formatting inserted text, so is there some work around? I tried to concat all rows data into one column(catt(...)) with all possible delimiters('0D'x or '\n' etc.) but anyway data in excel stores in one row, no automatically move to row down, what I would like to achive... For example: data test;       length a $ 32767;       a=catt("test      ",'0D'x,"   test1"); run; proc export   data=test   dbms=xls   outfile="…\test.xls"   replace; run; Will b e appreciate for any help. ... View more

Hi all, There is a possibility of creating spk files from command line(or bat file), using export command like that: ExportPackage -profile "profname" -package ...-objects "/folder1/folder2(Folder) /folder1/folder2/tabname(Table)..." But if there a re a lot of jobs/tables to export - export command will be long and exceed maximal line length of command:~8192 chars. So is there some workaround? I suppose that should be possibility put some file with parameters instead of listing each parfameter separately, but don't see such possibilitie from SAS documentation regarding batch export: http://support.sas.com/documentation/cdl/en/bisag/65422/HTML/default/viewer.htm#n1nkrdzsq5iunln18bk2236istkb.htm#p09ddp3kqzyje9n1rrrv67y0o8kh From another hand, if make spk package manually from DI studio for example, it allows to create spk from many meta-objects without any issues, so probably should be some possibility to do it also from batch export command... Thanks! ... View more

Hi all, Here is small description of problem: I tried to export big flow with a lot of src/trg tables from one environment to another. Folder structure same on both servers. Initially I tried to do it usual way - create spk manually from DI studio,by check-in needed ETLs and related src/trg tables. But obviously all that process takes time and very easy accidentially lost something , due there are really a lot of Jobs and related tables to the flow. So I find info that SAS provides "Batch Export Tool" that can automate similar process. So what I already did: I created small  macro with proc metadata, xmlmaps/xpath syntax, and that macro by flow name extract from metadata list of flows ETLs and targte source tables , soon will finish code that will also add pathes(folders) to that meta-objects. Then I tried to make spk not manually ,but using simple batch export tool syntax , smth. like that: ExportPackage -profile "profName" -package "c:\Documents and Settings\...\test.spk" -objects "/sasproject/.../tablename1(Table)" "/sasproject/.../tablename2(Table)" -types Table –excludeSubTypes -log "c:\Documents and Settings\...\test_log.log" And that command executes ok from command line, spk package creates normally and contains metadata for needed 2 tables(tablename1 and tablename2),BUT, after I tried import that package to be sure all is ok with it - I mentioned that folders structure lost, only root folder stais(sasproject). It's not acceptbale for me, due target spk will contains a lot of tables/jobs from different meta pathes. So I suppose should be some option that will "save" pathes to meatobjects in target spk packages. I tries subprop option, but it doesn't help... Whould be appriciate for any help! Thanks! ... View more

  Hi all, I've found probably general issue in ETLs that have SQL join transformation with sub-query ,such ETLs can't be promoted correctly to another servers or even same server due SPK packages from such jobs are damaged. I reproduced the issue on small test job. OS - AIX, SAS 9.3. So correct etls looks like in attached image correctETL.bmp (I erase table names due high security on company:) Correct SQL code from SQL join transformation  with subquery  looks like that:correctSQL.bmp After import export, or even after simple Copy such ETL to same folder in DI studio, etls demages and looks like that:incorrectETL.bmp And SQL code loses subquery after IN clause:incorrectSQL.bmp Export command itself looks like that:   ExportPackage -profile "..." -package "C:\...\package.spk" -objects "/.../.../test(job) -subprop -types "Condition,BusinessRuleFlow,ExternalFile,Cube,SearchFolder,Table,GeneratedTransform,OLAPSchema,InformationMap.OLAP,Measure,Column,Job.CubeBuild,Action,Library,MiningResults,Hierarchy,DeployedJob,CalculatedMeasure,InformationMap.Relational,RootFolder,Document,ConditionActionSet,Prompt,Dimension,Note,StoredProcess,PromptGroup,Job,MessageQueue,Service.SoapGenerated,Level,SharedDimension,DeployedFlow" So maybe some type of meta-object that needs to be exported omitted(lost), not sure. It looks like Java/DI studio issue, maybe some hotfix can fix it. Offcource almost each subquery can be replaced by inner join etc., but anyway - if somebody experienced same error - please share how it can be fixed. Thanks! ... View more