Sierra macros in 6.3

Sierra, Millennium & Encore
,
1

Hi all, someone mentioned during the Sys Admin forum at IUG that when their library upgraded to Sierra 6.3, they lost some of the macro commands/shortcuts (e.g., Ctrl+F1), which are reserved for system use starting with that release. We are upgrading to 6.3 on April 8 and I’d like to make sure our catalogers have their macros saved in keyboard shortcuts that will stay active.

Does anyone who has upgraded to Sierra 6.3 have a list of the macro keyboard shortcuts that are reserved for system use starting with that version? It seems like that information could be obtained in the Admin > Settings > Macro tab. I’d be grateful if anyone on 6.3 could check and report back.

Thank you!

2 Likes
2

@jmgold this sounds familiar. Did you have some code you could share?

3

Hi Daisy,

Our Training instance is on 6.3 and these are the reserved macros per the Admin App:

SDA:

  • F8
  • F10
  • ALT+F4
  • ALT+F6
  • CTRL+F1
  • CTRL+F4

Sierra Web:

  • F1
  • F3
  • F5
  • F6
  • F8
  • F10
  • F11
  • F12
  • ALT+F4
  • ALT+F6
  • CTRL+F1
  • CTRL+F4
  • CTRL+F5
  • SHIFT+F3
  • SHIFT+F5
3 Likes
4

Sierra Macro Assignments.sql (696 Bytes)
Here is a version of some code I shared on the Sierra listserv.  Populate your own <Ctrl+F1> macro with a distinct recognizable string and run this query to find the corresponding desktop_option_id.  Then swap the comments on the WHERE clauses, substituting your <Ctrl+F1> desktop_option_id in place of my 804.

3 Likes
5

I think this is the sql I’d seen from @jmgold that he was using to help identify staff accounts that would be affected by the change:

6

Yes that is the query that worked for us, however as it turns out those iii_user_desktop_option.desktop_option_id values vary between customers. So you have to go hunting for those first.
What I did originally was to take a test user login.
Set all the macros in it to “F1”, “CTRL+F2”, “SHIFT + F3”,etc…
Search iii_user_desktop_option.value for that text, limited to my test user
Then from there grab the id values for those row and stick them into the query Wes just shared.

1 Like
7

@daisypaul, in rereading your post I noticed you referenced macro commands [plural] but <Ctrl+F1> is the only macro affected between releases 6.2 and 6.3.  Victor did at first say there were four macros affected, but he misspoke and has since acknowledged this.  Furthermore, I spent time testing macros before and after our upgrade yesterday and I can verify that only <Ctrl+F1> was affected.

We got pretty lucky here at Stark Library and only a handful of people in Tech Services were actively using that macro slot.  It was helpful to run the before-and-after queries to proactively warn the affected staff members.

This horse was already beaten to death on the Sierra listserv yesterday.

2 Likes