I have an API that works just fine. However, when i attempt to call the API several times within a Macro, after about the 4th call of the API, I get a data error that the dataset is not found. I've put it in a do loop and then more simply put it in code such as this:
%macro one(macvar);
filename rsi "\\mypath.json"; proc http url="https://my API &macvar" out=rsi; run; libname rsi json "\\mypath.json";
%mend; %one(A); %one(B); %one(C); %one(D);
when it gets to D, i receive an error that the data set 'Results_Values' does not exist. wondering if i am hitting the API to many times to fast with the macro. If I run D on it's own it will work just fine. Has anyone else experienced this and is there a known workaround? I am using SAS Enterprise Guide 8.3.
... View more
Can SAS import .csv.gz files instead of CSV files? My CSV file is so large that I therefore have to compress it to .csv.gz files and import them directly into statistical softwares. In addition, the file is so large that I have to select columns and rows with specific features in the course of import or else my computer would run out of memory. Can SAS do that?
... View more
I am trying to automate a model-creation process in SAS Enterprise Miner, meaning I can enter a variable as "ABC", click run and it will query appropriate data, build the models, and the final step of the flow is to register the new model on the Metadata Server by name. Let's call it "Model ABC". This process works well, but the problem is that if I run this flow again, a new "Model ABC" is registered to the Metadata Server, in addition to the previously-created "Model ABC"s. So, if I look at the Metadata Server using the Management Console, I can see both "Model ABC" objects. SAS doesn't overwrite registered models even if they are identically-named. If I right-click on their properties, both models have identical properties with the exception of: ModelKey MetadataUpdated MetadataCreated Id This model-creation flow will be run frequently going forward for a wide range of input values (in addition to "ABC"), so I would like to avoid a massive builduip of identically-named models by deleting (via SAS Code node?) all models with name="Model ABC" from the Metadata Server prior to registering the model via the Register Model node. I know that models can programmatically be registered to the server via this macro: SAS Help Center: %AA_Model_Register Autocall Macro But the only options I have been able to find for deleting a registered model is via the SAS EM or Management Console GUI: SAS Help Center: SAS Enterprise Miner Model Package Registration Does anyone know of a way to programmatically delete models from the Metadata Server?
... View more
Disclaimer: I did not go to school for data science, computer science, artificial intelligence, machine learning, and/or software engineering... Greetings SAS Community, I have downloaded datasets from the National Data Archive of Child Abuse & Neglect (NDACAN), as well as from Data.gov and Children's Bureau of An Office of the Administration for Children & Families. 1st - I am trying to upload the NDACAN dataset into SAS Viya Workbench Visual Studio Code. But ran into problems, obviously. The dataset is in my external hard drive. File types: SAS, SPSS. DTA, SAV, DAT, BDAT, XPT, POR, SAS7BDAT, SAS7BCAT, DO, TAB, TRN, SPS. 2nd - I am trying to upload these external datasets into SAS in order to create historical volatility index limits for the BioFam Services startup I am trying to secure funding for [ https://linktr.ee/BioFamServices ] *** Yes, I have tried to use various online sources (typed words and video tutorials) but to no avail... *** Since I am new to SAS, I am having difficulties locating the various tools, options, etc. suggested in the online resources.
... View more
Hi Experts! As this is a product functionality question, parking my question here hoping some experts have also faced a similar requirement. We have 2 entities EntityA and EntityB that all user groups must be able to view. We have 2 data sources for relationships, PublicRelationships and ConfidentialRelationships. We have 2 user groups, PublicGroup and ConfidentialGroup. ConfidentialGroup should be able to see the relationships from both PublicRelationships and ConfidentialRelationships Source, while PublicGroup must only see the relationships coming from PublicGroup. Is there any way to implement this? Somehow the Conditions tab under Relationships seem to point more to link display design colors rather than as "Filter Conditions". Looking forward to some guidance!
... View more
Watch the live Hackathon Kickoff to get all the essential information about the SAS Hackathon—including how to join, how to participate, and expert tips for success.