Hi, I think that SAS Visual Analytics be enhanced to provide for up to three title lines on an object.   Under SAS Visual Analytics 8.5.2 we are only allowed to define a single title linefor a report object, such as a bar chart.   Whilst I know that titles should not be very wordy, sometimes it helps to have a little explanatory text as line #2 or even line #3 of a title.   At the moment I am stuck with something like the following screenshot of a chart using my favourite made-up data. The title for the report could be made more informative if the text could be split across several lines as I wanted them to be, not just auto-wrapped.     Vote for this fantastic idea, please ! Anything that encourages more people to use SAS Visual Analytics for more things, can't be all bad, right ?   Downunder Dave Wellington         ... View more

Hello, im suggesting that you implement some sort of overview of which variables that are used in a certain database for a SAS VA report.   For an example if you using a database with the paramaters a,b,c,d,e,f and are only using a,b,c, then a list that contains the used variables would be perfect (in this case only a,b,c). At the moment you have to go in on a report, click up the data and hover the mouse over each variable to see if it is used or not.  ... View more

Hi,   I'm suggesting if you could let the user add two legends to the Line-Bar chart as below screenshot: to show more details to the info based on two measures and two categories    ... View more

Hi Team We are big SAS customer running our SAS on Solaris OS. Currently GIT functionality with in SAS Studio is not supported for Solaris OS. We need this feature.     Thank you ... View more

If an external object (f.e. Custom Step) is added to the Flow then it is referenced by the full path. We would like to reference it by a variable or relative path like "../../Prompts.step" instead. This functionality constitutes the Git integrability and allows for a simultaneous work of more than 1 person while keeping the project in the Git.   We would like to see a following set up – each developer works on own local repository. Inside a repository we have number of Flows. Some Flows in a folder contain Custom Steps.        One developer changes something in such Custom Step and commits the changes. Other developer clones the repository and tries to change the same Custom Step. Dev2 is now unable to save it, because the path of the Custom Step points to dev1’s local repository. It means that even though the Flow is in repo2, the object inside (Custom Step) is from repo1. The path to DEV1's repo is visible if we hover over opened inside object from DEV2's Flow.   It is like this:   We want it to be like this:   Now we have to remove the Custom Step from each Flow and attach the new version, then select every custom option inside. It takes a lot of time, since one Custom Step can be in more than one flow. To solve this we could include objects with relative path (f.e. ../../Prompts/1_Prompts.step) or variable (f.e. ${path}/Prompts/1_Prompts.step) so it works across repositories. We don’t want to keep those Custom Steps outside repository as there is no DI’s check-out option and anyone could change the code of the Custom Step anytime. recording - ref: CS0060147 ... View more

HI, you should be able to export from an EG project file stored processes, including prompts, to a file (a SAS package?), and then reimport it into another project, prompts intact. It seems like a pretty strange oversight that you can't do this. ... View more

The ability to synchronize axis would be a great addition to the dual axis graphs. Having two different axis can be misleading and confusing. Right now it is possible to bypass unsynchronized axis by setting a fixed minumum and maximum. However, fixed axis is not considered ideal as new values can be higher or lower than the fixed values (e.g. when reporting on a new month). Therefore, a dynamic solution such as synchronizing axis would be ideal.  ... View more