# Alarm status table row styles flashing and static backgrounds based on priorities **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective\ **Created:** [April 5, 2021, 5:48pm UTC](https://forum.inductiveautomation.com/t/alarm-status-table-row-styles-flashing-and-static-backgrounds-based-on-priorities/45273 "2021-04-05T17:48:10Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\ **Post date:** [April 5, 2021, 9:15pm UTC](https://forum.inductiveautomation.com/t/alarm-status-table-row-styles-flashing-and-static-backgrounds-based-on-priorities/45273/6 "2021-04-05T21:15:53Z")
The `backgroundColor` property is part of the “required” schema of the object, and so even though you can delete it in the Designer, the component is still built with all of its required properties each time it loads. Fortunately, there’s a workaround: anywhere you have a backgroundColor property you want to overwrite/remove, replace the value of `backgroundColor` with `null`. This sort of short-circuits the property into being invalid, and so it falls back to the previous valid value, which in your case is your style. You’ll see a warning in the Designer, but you can safely ignore it. ![Screen Shot 2021-04-05 at 2.15.37PM](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/1/516a4501af67b573886d24e8c8e37e906e942ec8.png) --- _[View the full topic](https://forum.inductiveautomation.com/t/alarm-status-table-row-styles-flashing-and-static-backgrounds-based-on-priorities/45273)._