Comparing with traditional SAS library, the LASR data source consumed by VA also host locale info while a table is loaded into LASR server; Any SAS supported encoding data can be loaded into memory as you wish, but during the table loading, you must load it via appropriate SAS session with specific locale/encoding. After a data is loaded into memory, it will not change anymore except it's re-loaded.
In fact, SAS Visual Analytics can consume all data source defined on SAS metadata server as a flat list. SAS LASR server was born to support Unicode data. A customer may collect data from its child companies all over the world, the dataset may be very big and contains multiple lingual data. SAS Unicode dataset can contain all languages data as wish, while it's being loaded to LASR server, we usually choose en_US as the neutral locale to prepare data.
Customer may choose different locale in SAS Visual Analytics client preference dialog to control UI language and formatting, but the locale of the data source on SAS LASR server also would impact SAS Visual Analytics behavior, e.g. data item sorting etc.
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
Data Literacy is for all, even absolute beginners. Jump on board with this free e-learning and boost your career prospects.