02-04-2025
FredrikHansson
Obsidian | Level 7
Member since
02-22-2012
- 31 Posts
- 33 Likes Given
- 0 Solutions
- 16 Likes Received
-
Latest posts by FredrikHansson
Subject Views Posted 535 01-07-2025 04:15 AM 983 07-19-2024 11:17 AM 1145 07-19-2024 02:38 AM 1211 06-24-2024 04:58 AM 846 06-09-2024 11:40 AM 1275 06-09-2024 11:24 AM 1366 06-09-2024 11:05 AM 1368 04-03-2024 07:14 AM 1467 03-27-2024 06:36 AM 1608 03-25-2024 06:40 AM -
Activity Feed for FredrikHansson
- Got a Like for Make it possible to style tabs in Visual Analytics Reports. a week ago
- Got a Like for Re: Fit a report to screen size. 01-31-2025 02:42 AM
- Posted Re: SAS Job Execution - HTML doesn't render sgplot image on SAS Programming. 01-07-2025 04:15 AM
- Got a Like for Re: Fit a report to screen size. 11-12-2024 08:00 AM
- Got a Like for Make it possible to style tabs in Visual Analytics Reports. 10-22-2024 10:01 AM
- Got a Like for Make it possible to style tabs in Visual Analytics Reports. 10-02-2024 04:48 AM
- Got a Like for Make it possible to deactivate mouse wheel zoom in Visual Analytics graphs. 10-01-2024 06:24 AM
- Got a Like for Make it possible to style tabs in Visual Analytics Reports. 09-03-2024 06:38 AM
- Got a Like for Make it possible to deactivate mouse wheel zoom in Visual Analytics graphs. 09-03-2024 06:36 AM
- Got a Like for Make it possible to deactivate mouse wheel zoom in Visual Analytics graphs. 08-05-2024 04:25 AM
- Got a Like for Re: SAS Job Execution HTML cannot find png. 07-21-2024 05:41 PM
- Posted Re: SAS Job Execution HTML cannot find png on SAS Programming. 07-19-2024 11:17 AM
- Posted Re: Allow DDC selectors in reports controls and page controls areas on SAS Product Suggestions. 07-19-2024 02:38 AM
- Liked Re: Allow DDC selectors in reports controls and page controls areas - Status changed to: Suggestion Closed for sashakar. 07-19-2024 02:36 AM
- Posted Re: Make it possible to style tabs in Visual Analytics Reports on SAS Product Suggestions. 06-24-2024 04:58 AM
- Got a Like for Make it possible to style tabs in Visual Analytics Reports. 06-11-2024 05:12 AM
- Got a Like for Allow DDC selectors in reports controls and page controls areas. 06-11-2024 05:12 AM
- Got a Like for Make it possible to deactivate mouse wheel zoom in Visual Analytics graphs. 06-11-2024 05:12 AM
- Got a Like for Make it possible to deactivate mouse wheel zoom in Visual Analytics graphs. 06-10-2024 03:12 AM
- Got a Like for Allow DDC selectors in reports controls and page controls areas. 06-10-2024 03:11 AM
-
Posts I Liked
Subject Likes Author Latest Post 1 1 3 12 2 -
My Liked Posts
Subject Likes Posted 2 03-25-2024 06:40 AM 1 07-19-2024 11:17 AM 5 06-09-2024 11:40 AM 2 06-09-2024 11:24 AM 6 06-09-2024 11:05 AM
01-07-2025
04:15 AM
I'm sorry if I missled you.
"_ODSOPTIONS" is a parameter that must be submitted to the JobExecution job. The parameter will be handled by the %JESBEGIN-macro.
%JESBEGIN macro will generate a ods-statement for you. To avoid confusion I would remove the ods-statement from your code.
The code below works for me. I call the job with the parameter _ADDJESBEGINENDMACROS set to "false" to prevent %JESBEGIN from executing before my own code. Then I call %JESBEGIN from within my code to leverage the functionality within the macro.
Tip: Parameters can be set in job properties.
Tip2: Set the _DEBUG-parameter to true to see what code is generated from %JESBEGIN.
* Job must be called with parameter _ADDJESBEGINENDMACROS set to "false" ;
%let _ODS_DEVICE = png;
%let _ODSOPTIONS = options(BITMAP_MODE='inline');
options mprint;
%JESBEGIN;
options nomprint;
title; footnote;
proc sgplot data=sashelp.class;
scatter x=height y=weight;
run;
%JESEND;
... View more
07-19-2024
11:17 AM
1 Like
Try setting:
_ODSOPTIONS = options(BITMAP_MODE='inline')
This option will convert your binary picture into a BASE64-encoded string that is included into the HTML. The pictures are not stored as separate binary files.
... View more
07-19-2024
02:38 AM
Thank you! I'm looking forward to use DDC as control object in future releases.
... View more
06-24-2024
04:58 AM
Hi @Stu!
That's good news! I can see in your animation that there is a hand on mouse-over. That's great, and making it possible to style the text will be a game changer!
Yes, my screen snippet is from a report package. When we start letting users in to VA later this year, they will be directed to reports using the parameters reportViewOnly=true and reportContextBar=false. So the reports will appear very similar to the report package.
We are currently using Long-Term Support 2024.03. Our plan is to stick with LTS-releases.
Are you willing to guess when we can expect to be able to style tabs in a LTS release?
... View more
06-09-2024
11:40 AM
5 Likes
I know this has been suggested before, but the issue was closed. (https://communities.sas.com/t5/SAS-Visual-Analytics/Mouse-wheel-graph-interaction/td-p/435358) We are about to publish reports for a big number of users with low computer experience. Using VA is a very small part of their daily job. To educate them all on how to avoid unintended zooming in graph objects, is not a feasible task.
A possibility to deactivate mouse wheel zoom would be a great increase in usability for our VA reports, and massively reduce our support burden.
I really hope you can consider implementing this soon. Thanks in advance.
... View more
- Find more ideas tagged with:
- graphs
- visual analytics
- zoom
See more ideas labeled with:
06-09-2024
11:24 AM
2 Likes
Data Driven Content objects are not only used for visualizing data. They are also the key to innovative ways to select/subset what data to display in the report. (For example the TreeSelector). Therefore it would be very useful if DDC objects could be used exactly as Control object, including being put in the reports controls area and the page controls area of the report.
Implementing this would really be a game changer for us.
... View more
- Find more ideas tagged with:
- Data Driven Content
- DDC
- selection
- visual analytics
See more ideas labeled with:
06-09-2024
11:05 AM
6 Likes
Our users are often not very impressed with the reports me and my colleagues make for them. The reason is that they only see the first tab of the report. The tabs are so subtile that the users don't even see them. It's also hard to see which tab is selected.
Please make it possible to style the tabs so that we can make them "pop" more.
Picture to show what I mean:
Picture of "invisible" tabs in a VA report
... View more
- Find more ideas tagged with:
- tabs
- visual analytics
See more ideas labeled with:
04-03-2024
07:14 AM
I also have issues with "Timed Out". In my case we didn't have one huge SQL-query but many few. That made it possible to work around the problem by splitting the job into two. The status "Timed Out" should really be addressed as a bug or at least documented.
... View more
03-27-2024
06:36 AM
That was just a lengthy way of saying "I have no idea what status message 'Timed Out' means".
... View more
03-25-2024
06:40 AM
2 Likes
The only solution that I have come up with that really works, is to first decide what is the smallest possible screen size that is supported, and what is the highest possible zoom-level. Then I design and test the report with that configuration.
(The report will look strange on bigger screens with higher resolution and/or lower zoom-levels, but it will work. All texts and objects will be visible.)
Designing a report for a bigger screen and relying on VA to adjust it for smaller screens is not a good way to go. Instead of rearranging report objects and changing tabs to hamburger menus (which is a common way for responsive web sites to adjust to smaller screens), report objects are resized so that texts are disappearing, making graphs impossible to interpret.
If someone has better ideas on how to build responsive VA reports I would be very interested.
... View more
11-29-2023
03:50 AM
Great article!
We're trying to set up something similar too.
Do you know if there is an updated guide for sas.logon.oath.providers? (sas.logon.oath.providers.external_oauth is deprecated)
Thanks!
... View more
05-10-2023
06:55 AM
This is a very reasonable request. The workaround of using a separate text object will make the graph incomplete when maximizing, exporting to picture or including the graph object in another web application.
... View more
01-20-2023
09:45 AM
The problem has now been reproduced in another environment. So at least I'm not alone. 😉
A support track is opened: 7613725502
... View more
01-20-2023
05:59 AM
New day, new scheduling problems!
We had some difficulties with scheduling in Viya before. The first (Jobs and Flows - How do I schedule a flow?) turned out to be a bug, the other (How do I make my scheduled flow to actually run?) a user mistake.
Let´s what´s the problem this time. 😊
The task
We have three different flows “Personal-data”, “Senioralert 1-8” and “Swedeheart 1-8”. Each of the flows contains a number of SAS Studio flows who are to be run in a certain order.
“Senioralert 1-8” and “Swedeheart 1-8” can run in parallel, but “Personal-data” must run befor them both.
We created the flow “Nattbatchen” ( “The night batch” in swedish 😊) that contains “Personal-data”, “Senioralert 1-8” and “Swedeheart 1-8”.
💡 The flows in the pictures below are built in Environment Manager --> "Jobs and Flows". Not to be confused with the kind of flows that are built in SAS studio.
Here are pictures of all four flows:
(as you can see there is more happening in “Nattbatchen”, but it shouldn’t be relevant to my issue)
My problem
When I trigger the main flow “Nattbatchen” manually (by right-clicking and selecting “Execute” everything executes in the order I expect it to.
But when I schedule “Nattbatchen” the order in the subflows ar not respected. All SAS Studio Flows in the “Personal-data”-flow are triggered at the same time.
I hope these pictures will describe the problem better:
Expected behavior (happens when running “Nattbatchen” manually)
As you can see the pdbatch*-flows run one at a time. Sa2batch*-flows run one at a time, shtbatch*-flows run one at a time (in parallel with sa2batch* which is what I want)
Unexpected behavior (happens when “Nattbatchen” is scheduled to run at a specific time)
All pdbatch-flows are started at the same time. Shtbatch* and sa2batch* waits for pdbatch, but are then started all at the same time.
We are using Viya 2022.09. Is there someone experiencing the same problems?
... View more
01-19-2023
09:18 AM
The error was in my flow. I started the flow with a time-event (wait for 01:00 = the same time the flow was scheduled to run) and that's where it stopped.
Now my biggest problem is that I can't find the embarrassed-emoji...
... View more