Hi SASJedi,   As suggested, I shall check the .json files and get back to you.    Thanks Rajesh A     ... View more

Hi Chris,   By default, SAS is picking up UTF-8. I tried changing the encoding= option via options and DATA step. But it wouldn't work.   Do you suggest any other alternative for this ?   Thanks Rajesh A ... View more

Hi Jedi,   Here is the code. Hope this gives you some understanding now of what I am trying to achieve.   %let nextLink = https://api.xxxxx.io/api/v2/&module./&relns.;                  %let batchnum = 1;   /* flag_url is count of records where there is nextlink */   %do %until (&flag_url.=0);    /*Handle special characters section starts*/   filename outfield "&config_root./json_in_files/xxxxx_data.json";   filename out_&mapmod. "&config_root/json_map/out_&mapmod..map";         proc http url="&nextLink."          oauth_bearer="&access_token"          out = outfield;     run;          /*this section handles the special characters in the data that will not come in via JSON */                    %sysexec  cd &config_root./json_in_files;      /*replaces two types of special char with space in the new file */      %sysexec cat xxxxx_data.json | sed 's/\\u2022//g; s/\\uf0a7//g; s/\\u//g' > xxxxx_data1.json;        /*uses new file for libname */      filename fields "&config_root./json_in_files/xxxxx_data1.json";      filename out_&mapmod. "&config_root/json_map/out_&mapmod..map";      libname jresp json fileref=fields map=out_&mapmod.;       %if &batchnum=1 %then %do;  %if (&module.=maxxxx) %then %do;   data &module._us_data;  set jresp.us_data; run; %end;   %end; %else %do;     %if %sysfunc(exist(jresp.&mod._data)) %then %do;     data &module._data&batchnum. ; set jresp.&mod._data; run;     %end;         data &module._data;     %if %numobs(&module._data) > 0 %then %do;          set &module._data &module._data&batchnum.;        %end; %else %do;        set &module._data&batchnum.;     %end;       run;   %end;   /*resets nextlink and batchnum */    %let nextLink=;    %let flag_url=;   /*gets the next URL to pull the next 200 records */    data s_ ;       set jresp.links ;       call symputx('nextLink',next);      run;   /*sets count so the do until will stop when no more nextlinks are available */           proc sql ;       select count(*) into: flag_url       from jresp.links          ;     quit;   proc print data=jresp.links;run;   %put flag_url=&flag_url.; %put nextLink=&nextLink.; /*updates batchnum and clears names for next run */          %let batchnum = %sysevalf(&batchnum. + 1);    %end;/*DO - UNTIL loop*/ ... View more

Hi SASJedi,   Thanks for the clarification on character encoding. I could see that we are currently using UTF-8 encoding option.    I am making the API calls using the config files and tokens. The first time, when I call the URL, I pass the very first link as  nextlink=https://api.xxxxx.io/api/v2/&module./&relns. This link works fine and fetches data which has 50 records in it.    The successful URL built is as below :  proc http url="https://api.xxxxx.io/api/v2/xxxx/?fields[xxxx]=us" oauth_bearer="xxxxxxxxx" out = outfield; run;   When the above URL is set, the JRESP.LINKS dataset fetches the next field with link to the next set of 50 records. Using this next field, I am creating a macro variable and pass this URL to create another data pull.   Below is URL which gets constructed and is creating issue : proc http url="https://api.xxxxx.io/api/v2/xxxx?fields%5Bmass%5D=us0026page%5Boffset%5D=50" oauth_bearer="xxxx" out = outfield; run;   I checked the URL in Postman to verify and postman gives me  https://api.xxxx.io/api/v2/xxxx?fields%5Bmass%5D=us&page%5Boffset%5D=50.   Do you think I should overwrite the encoding option or suggest anything better?   Let me know if I wasn't clear in explaining you the situation.   Thank you. ... View more

Hi All I thank you for your valuable suggestion. Finally, we were able to identify the resolution for this issue. As mentioned that  our SAS applications are ThinApp'ed. So there was a problem with user settings and the sandbox properties are getting created/stored properly for the users. The server team has identified the issue and it is NOT a SAS issue. The users AD profile has been recreated and all seems to work fine now. Thanks Raj ... View more

Hi Team Do you have any other suggestions. I am still stuck with this one. Raised a ticket with SAS and awaiting their reply. Thanks Raj. ... View more

Hi Ballard got it .... Thanks Raj ... View more

Hi Kurt Apologies if my question was stupid, but I am new to SAS Administration. I have checked the credentials on SAS server and it is fine. I have checked the Metadata Logs and log says " UFNE The requested user folder 'My Folder' does not exist for user" ..... but I can see that a "My Folder" was created for that user in Management console. Please let me know if there is any other place that I can check. Thanks Raj ... View more

Hi Mark Thanks. I have raised a ticket with SAS and see what they would suggest. Will update you on the outcome of this issue. @ Casey - Thanks to you as well for the prompt response. Thanks Raj ... View more

Hi Casey/Mark We use the SAS applications which are ThinApp'ed. So, if the applications are Thinapp'ed we won't be able to test the server connections functionality. It is only one user who is facing this issue and not sure what is stopping her from connecting to the profile. Request you to advice. Thanks Raj ... View more