So the solution above didn't really solve your your problem then? 😉 Thank you for unmarking it. 🙏   I also have to downgrade. Using the workaround 20 times a day is not possible. How did you manage to downgrade? 🤔 My installation depot contains EG8.31 and I don't want to go that far back. ... View more

@Erdnis Could you please (if possible) unmark this reply as a solution? I guess this workaround is sufficient for some users, but for many (most?) users it's not acceptable. ... View more

Hi @sashakar. Sorry for the late response. We are using a mix of report packages and guest users access to the Visual Analytics web application. A report level setting (or object level setting) would be sufficient. But having a system wide setting for "Disable zoom in graphs", would be great!   Thank you! Fredrik ... View more

  I've got an answer. I haven't read it in detail yet, but it seems like its not the answer I was hoping for...     Hello Fredrik, Thank you for contacting SAS Technical Support and for your inquiry regarding the default file encoding in SAS Enterprise Guide 8.6. Starting with this version, the default encoding for new program files has been updated to UTF-8. We understand that this change may affect workflows where a different encoding was previously used. As a workaround we propose the following, (this example is for Norwegian characters, adapt it as required): 1) From EG 8.6, select File > Open > My Computer, and change the "Open as" to be "Program with encoding", as per following screenshot   2) Browse to the code required, and select, where you get will get a pop up as following:   3) Select "Code with encoding" and set encoding to "Western European (Windows) Code Page 1252)". You will then see the ANSI code working as expected, as per the following screenshot:   An alternative workaround would be to convert the program files to UTF-8. We encourage reviewing encoding settings when working with existing files to ensure alignment with your current environment. Please don’t hesitate to reach out if we can assist with anything. I hope this answers any questions you have, but if you need anything further then please let us know, Regards, ... View more

@sashakar  Hi! What's the status of the review? ... View more

I did. Half an hour ago. 🙂 I will update this thread when I get an answer. ... View more

I have the same problem after upgrading to 8.6. I hope we can get a quick fix for this. ... View more

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

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

Thank you! I'm looking forward to use DDC as control object in future releases. ... View more

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

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