# Alarm notification - calculated roster type **URL:** \ **Category:** Ignition\ **Tags:** ignition79\ **Created:** [December 11, 2018, 6:06pm UTC](https://forum.inductiveautomation.com/t/alarm-notification-calculated-roster-type/21341 "2018-12-11T18:06:28Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![gnguyen](https://avatars.discourse-cdn.com/v4/letter/g/41988e/32.png) [@gnguyen](https://forum.inductiveautomation.com/u/gnguyen)\ **Post date:** [December 11, 2018, 6:06pm UTC](https://forum.inductiveautomation.com/t/alarm-notification-calculated-roster-type/21341/1 "2018-12-11T18:06:28Z")
Hello, I want to use a notification block with calculated roster type. In particular, I would like to add the language so that the voice notification can use the correct language (Spanish). I was thinking something like builder.username(“mary”).email([‘mary@company.com’]).add().language([‘es\_ES’]).add() or user1 = { “username”: “mary”, “email”:[“mary@company.com”], “language”:[‘es\_ES’]} Any idea of a correct syntax? Thank you. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [December 11, 2018, 6:31pm UTC](https://forum.inductiveautomation.com/t/alarm-notification-calculated-roster-type/21341/2 "2018-12-11T18:31:01Z")
Unfortunately, it doesn’t look like this is possible with the current implementation of calculated rosters. I’ve added you to an internal bug ticket tracking that change - if you get in contact with support, they can also set things up so you get an email once a fix goes in. ---
**Author:** ![gnguyen](https://avatars.discourse-cdn.com/v4/letter/g/41988e/32.png) [@gnguyen](https://forum.inductiveautomation.com/u/gnguyen)\ **Post date:** [December 12, 2018, 8:35am UTC](https://forum.inductiveautomation.com/t/alarm-notification-calculated-roster-type/21341/3 "2018-12-12T08:35:19Z")
It’s a pity…Thank you Paul. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [July 12, 2021, 9:19pm UTC](https://forum.inductiveautomation.com/t/alarm-notification-calculated-roster-type/21341/4 "2021-07-12T21:19:43Z")
Better late than never, as of 8.1.8 you’ll be able to pass `language` in the `extraProps` key for the calculated roster, which will allow you to specify a language for voice notification. ---
**Author:** ![gnguyen](https://avatars.discourse-cdn.com/v4/letter/g/41988e/32.png) [@gnguyen](https://forum.inductiveautomation.com/u/gnguyen)\ **Post date:** [July 13, 2021, 7:15am UTC](https://forum.inductiveautomation.com/t/alarm-notification-calculated-roster-type/21341/5 "2021-07-13T07:15:44Z")
> [@paul-griffith](#): > > Better late than never As you say, better late than never 😉 ---
**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\ **Post date:** [July 14, 2021, 1:55pm UTC](https://forum.inductiveautomation.com/t/alarm-notification-calculated-roster-type/21341/6 "2021-07-14T13:55:33Z")
Any chance you could add a per-recipient timezone preference for formatting times? 🙂 Have you seen [my hacked up method](http://forum.inductiveautomation.com/t/alarm-notification-timezones/36447) to make it work as-is? I would love to not need that. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [July 14, 2021, 4:08pm UTC](https://forum.inductiveautomation.com/t/alarm-notification-calculated-roster-type/21341/7 "2021-07-14T16:08:50Z")
Hmm…that’d be a separate feature request, but is possibly doable. Maybe make an ideas post for it? We’d probably want to do it ‘right’ by introducing a Timezone top-level user property, which sounds like a whole kettle of fish. ---
**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\ **Post date:** [July 14, 2021, 4:13pm UTC](https://forum.inductiveautomation.com/t/alarm-notification-calculated-roster-type/21341/8 "2021-07-14T16:13:16Z")
> [@paul-griffith](#): > > which sounds like a whole kettle of fish We're already falling down that hole. Once we created a per-user timezone setting, users expected all the Perspective views to pay attention to it. It's an interesting challenge. We've had to explicitly flag some views as being in UTC, and others we had to pre-format the times to strings to prevent the automated formatter from using the wrong timezone. Ideas post made: > **[Support controllable timezones on alarm notification messages | Ignition...](https://inductiveautomation.canny.io/ignition-features-and-ideas/p/support-controllable-timezones-on-alarm-notification-messages)** > > Currently, all alarm notifications format eventTime using the gateway timezone. I would like to override that with a timezone parameter on the alarm event.