SAS Visual Investigator
for developers
Getting Started with SAS Visual Investigator
Combine large, disparate, structured and unstructured data sources to manage alerts and perform detailed investigations.
SAS VI related blog posts
-
[SGF시리즈#2] 인구이동분석, 접촉자 추적.. 팬데믹 극복을 위한 분석 기술
질병 확산을 억제하고 경제적 영향을 최소화하기 위해서는 인구가 어떻게 이동하는지 분석하고, 지역 내 접촉자를 추적하여 적절한 의사결정을 해야 합니다. 이번 SGF 시리즈에서는 인구 이동 분석과 접촉자 추적 등 SAS 분석 기술이 어떻게 팬데믹 극복을 위한 의사결정을 지원하는지에 대한 SAS 짐굿나잇 회장과 스티브 베넷 글로벌 정부기관 프랙티스 부문 이사의 세션을 소개합니다. [...]
The post [SGF시리즈#2] 인구이동분석, 접촉자 추적.. 팬데믹 극복을 위한 분석 기술 appeared first on SAS Blogs.
-
Es el momento de combatir la corrupción con analítica
Las técnicas creadas a partir del Big Data han revelado múltiples aplicaciones que han servido para poner sobre la mesa los fraudes y las filtraciones masivas de información sobre temas relacionados con, por ejemplo, paraísos fiscales y evasión de impuestos. A Latinoamérica, según reportes divulgados por Global Financial Integrity, la [...]
The post Es el momento de combatir la corrupción con analítica appeared first on SAS Blogs.
-
De la ficción a la realidad en el siglo XXI
Desde que era un niño, fui un apasionado por las series policíacas. Pero más allá de ver como se enfrentaba a la delincuencia e injusticia, me gustaba observar cómo se desarrollaba el marco investigativo hasta dar con los autores de hechos criminales, la metodología empleada y los diferentes medios y [...]
The post De la ficción a la realidad en el siglo XXI appeared first on SAS Blogs.
Latest from the SAS Community
- New Support for External OpenSearch Instances in the SAS Viya Platform New Support for External OpenSearch Instances in the SAS Viya Platform
-
External Replication Is Not Working as Expected in SAS® Visual Investigator
Starting in SAS Visual Investigator 10.7 and later, you can store replicated records or observations in an external table in a database. This practice is commonly referred as external replication.
If you encounter a configuration issue with external replication, see the Common External Replication Configuration Issue in SAS® Visual Investigator article.
However, you might encounter some of the following usage-related issues while using external replication for a flow:
After you configure the external replication table correctly in the flow, it might fail with the following errors when you run a published flow. Normally this issue occurs when your external replication table is in Oracle. The error appears on the Jobs tab of the Manage Investigate and Search interface or in the sas-vsd-service_<timestamp>.log file.
com.sas.svi.commons.cas.CASSession : xxx@xx(47a7beb5-d3f0-4d49-b35d-aa18bccd897b) CAS: save: Function failed. com.sas.cas.CASException: Function failed. (severity=2 reason=0 statusCode=310002) 3 NOTE: Performing serial SaveTable action using SAS Data Connector to Oracle. 5 ERROR: General error ORA-00910: specified length too long for its datatype 5 ERROR: Function failed. 5 ERROR: The action stopped due to errors. debug=0x80fff802:TKTS_ERROR The job failed for the flow "xxx". Error: The table "{0}.{1}" could not be created. CASException: Function failed. Performing serial SaveTable action using SAS Data Connector to Oracle. General error ORA-00910: specified length too long for its datatype Function failed. The action stopped due to errors.
Resolution: Complete the steps in SAS Note 66106. Note that the SAS Note is also applicable to SAS® Visual Investigator 10.8.
When you run a published flow, the generated alert's context record might contain an empty, blank, or null value for a column. It is expected for a value to be associated with that column. For example, in the following screenshot, you expect a value to be in the City column.
Resolution: The most likely culprit for this issue is that, for that specific column (City), you have defined an infinite length in your source and replication table. For example, you might have specified “VARCHAR" instead of "VARCHAR (100)". Columns must have a defined length according to the Administrative Tasks: Data Configuration Information section in the SAS Visual Investigator documentation for your version. Hence, you need to fix the column schema in your source and replication tables.
After running a published flow, context records might not appear in the UI for the generated alert, as shown below:
The following explain why you might encounter this issue:
- You might not have selected/enabled the Replicate records from scenario context option on the Properties tab for the desired scenario of the published flow.
- You might not have configured the entity correctly in SAS Visual Investigator.
- Upon further inspection, you might realize that context records are not getting populated in the configured external replication table. If the generated alerts are tied with the DATA step scenarios, then review the Using DATA Step Code to Design a Scenario section in the SAS Visual Investigator documentation for your version. Most likely you missed a requirement.
-
Front Line Monitoring - Use Case
Team Name
Front Line Monitoring Track Banking Use Case Carbon credit offset market research
Technology SAS VIYA
Region USA, AP
Team lead Josh Dalton
Team members
Alaric Del Rio
Carlo Enriquez
Mel Frago
Social media handles N/A Is your team interested in participating in an interview? Y Optional: Expand on your technology expertiseJury Video:
(view in My Videos)Pitch Video:
(view in My Videos)