If I understood correctly, you want to filter the data in a report using specific filters. Let me try to provide some context with an example, okay?   I have a report that displays several charts for various cities in a state. However, I want the report to show only specific cities.   If this is your scenario, here’s how you can solve it: In your Visual Analytics report, go to Data > Click the icon on the right side next to your data source called Data Source Menu, and then select Apply Data Filters.... A condition screen will appear. In the scenario we imagined above, the filter would be for cities. So it would look like this: ( 'ID_CITY'n In ('10', '11', '12') ) Done! You have filtered your report by the city IDs you want to display. ... View more

Only works on SAS Viya 4? ... View more

From what I understand, you created a hierarchy between categories. However, I don't understand why you can't use the same hierarchy in both charts. That is the only way to make this work. ... View more

I don't know if this will help you in Model Manager, but when I have an issue with a table that has more than 32 characters, I use the following macro in Studio:   /* Define the macro variables */ %let incaslib = ; /* CAS library where the table is located */ %let casdata = ; /* Name of the CAS table you want to rename */ %let casout = ; /* Name of the table you want to set in CAS */ /* Macro to load and promote a table in the CAS environment */ %macro sas_load_promote_cas(casout=, incaslib=, casdata=); /* Drops the table in the CASLIB and loads the table into CAS */ proc casutil; droptable incaslib="&incaslib." casdata="&casdata." quiet; load casdata="&casdata." incaslib="&incaslib." outcaslib="&incaslib." casout="&casout."; run; /* Promotes the table to the CASLIB */ proc casutil; promote incaslib="&incaslib." casdata="&casout." outcaslib="&incaslib." casout="&casout."; quit; %mend sas_load_promote_cas; /* Call the macro with the defined variables */ %sas_load_promote_cas(casout=&casout, incaslib=&incaslib, casdata=&casdata); This way, I rename the table to a shorter name so it can be used within the SAS environment. ... View more

This error is related to collective operations in a distributed CAS (Cloud Analytic Services) grid environment in SAS, where synchronization between nodes was interrupted. This can happen for various reasons, such as conflicts in simultaneous operations or communication issues between grid nodes.   Here are a few steps to diagnose and potentially resolve the issue:   Check for concurrency: The error indicates that a collective operation conflicted with another on a different node. Check if the code is being executed in parallel or if other processes are accessing the same data sets or CAS tables at the same time. If possible, try running the operation in a less busy environment or when there are no other ongoing operations. Restart the CAS grid: It may be necessary to restart the nodes or repair the communication between nodes in the CAS grid. The CAS administrator can help check the grid status and restart the services if needed. Check data consistency: Ensure that the data being updated hasn't been corrupted or is being used by another process that could be causing a conflict. If possible, try isolating the table being updated to ensure that no other processes are trying to modify the same table simultaneously. Run in a test environment: Try running this operation in a controlled environment with less workload (fewer users, fewer simultaneous operations) to see if the problem persists. Adjust the code: Check the variables used in the WHERE clause. There might be issues related to case sensitivity or string formatting, which could cause unexpected behavior. Make sure that the value of &value. is being interpreted correctly and that the parameters &form_fileref, &form_mail, &form_caslib, and &form_table have valid values. You might also want to test this code in a non-grid environment to determine whether the issue is with the code or the distributed CAS configuration.   If the problem persists, you may need to check detailed CAS logs and consult SAS technical support to investigate the issue in the infrastructure. ... View more

Thanks for your answer! The problem is that I am using Job Execution in SAS Viya to send the XML file and in this context I cannot use the HTTP PROC directly or the suggestion you made since the system creates a URI. So since the process is executed inside the Job Execution I need to work with the URI of the XML file and that is where my difficulty lies. ... View more

Anyone? ... View more

Yes, it can be done through PROC HTTP, but the problem is downloading via the URI.   In the case of PROC HTTP, I would have to include other SAS parameters like token or webusername, but that’s not the case here.   I need to access the XML file through LIBNAME XMLV2 via the URI. ... View more

So it will only work on Viya 4, correct? ... View more

3.05   ... View more

I made the changes, but it still didn't work. I put some images to exemplify the problem. It's as if there were no JS files.   ... View more