# Sierra macros in 6.3
**URL:** https://forum.innovativeusers.org/t/sierra-macros-in-6-3/2356
**Category:** Sierra, Millennium & Encore
**Tags:** sierra, upgrades
**Created:** [March 20, 2025, 3:43pm UTC](https://forum.innovativeusers.org/t/sierra-macros-in-6-3/2356 "2025-03-20T15:43:37Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@daisypaul](https://forum.innovativeusers.org/u/daisypaul)
#### Post date: [March 20, 2025, 3:43pm UTC](https://forum.innovativeusers.org/t/sierra-macros-in-6-3/2356/1 "2025-03-20T15:43:37Z")
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!
---
### Author:  [@wesochuck](https://forum.innovativeusers.org/u/wesochuck)
#### Post date: [March 20, 2025, 3:58pm UTC](https://forum.innovativeusers.org/t/sierra-macros-in-6-3/2356/2 "2025-03-20T15:58:29Z")
@jmgold this sounds familiar. Did you have some code you could share?
---
### Author:  [@jmoakler](https://forum.innovativeusers.org/u/jmoakler)
#### Post date: [March 20, 2025, 4:57pm UTC](https://forum.innovativeusers.org/t/sierra-macros-in-6-3/2356/3 "2025-03-20T16:57:14Z")
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
---
### Author:  [@bgaydos](https://forum.innovativeusers.org/u/bgaydos)
#### Post date: [March 20, 2025, 5:55pm UTC](https://forum.innovativeusers.org/t/sierra-macros-in-6-3/2356/4 "2025-03-20T17:55:29Z")
[Sierra Macro Assignments.sql](https://forum.innovativeusers.org/uploads/short-url/xTZQVGfi2VpEcKOyMIiYqzLsoWZ.sql) (696 Bytes)
Here is a version of some code I shared on the Sierra listserv. Populate your own \ 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** \ desktop\_option\_id in place of my **804**.
---
### Author:  [@wesochuck](https://forum.innovativeusers.org/u/wesochuck)
#### Post date: [March 20, 2025, 6:35pm UTC](https://forum.innovativeusers.org/t/sierra-macros-in-6-3/2356/5 "2025-03-20T18:35:44Z")
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:
>
---
### Author:  [@jmgold](https://forum.innovativeusers.org/u/jmgold)
#### Post date: [March 20, 2025, 6:45pm UTC](https://forum.innovativeusers.org/t/sierra-macros-in-6-3/2356/6 "2025-03-20T18:45:47Z")
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.
---
### Author:  [@bgaydos](https://forum.innovativeusers.org/u/bgaydos)
#### Post date: [March 20, 2025, 9:19pm UTC](https://forum.innovativeusers.org/t/sierra-macros-in-6-3/2356/7 "2025-03-20T21:19:56Z")
@daisypaul, in rereading your post I noticed you referenced macro command **s** [plural] but \ 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 \ 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.