Hi Dojo,
Just a quick follow-up from https://community.dataminer.services/question/alarms-report-dashboard-how-can-severity-colours-be-adjusted-in-the-dashboard/
It seems that the colours in the Alarm Report dashboard can change even after being reset - not sure what operations might be triggering this for the preconfigured package (using 1.0.1-CU4) in this staging environment, but is there an option to always link dashboard severities to what is set in the DMS / maintenance settings?
Or is the order in the Data tab the one that would determine the association with the colour in the themes of the LayOut Tab? For some reason, theme colours start from the warning severity on the right in this GUI/environment - haven't found a way to edit a theme that is already present - running 10.5 CU4 - but unaware of what may have changed the colours for pre-built SL themes
In this last case, I think I didn't edit anything relevant - just switched on/off the "Allow Components to shift" option - and reloaded - with my own custom theme - yet this fixed the colour association: 
Any option to skip this and just rely on default colours of the DataMiner xml file?
Hi Alberto,
It is not possible to link the colors in the dashboard directly to the XML file. Dashboards has no concept of 'severities', only of (conditional) data colors.
The order of the colors in the default themes doesn't affect the colors used in the component in this case, since the components have a custom theme overwriting this. These default themes cannot be edited, these are updated with the software itself and are always subject to change.
The order of the colors in the custom theme of the component are what ultimately defines what severity is associated with what color. These colors are used by the data in the order they are defined. This means that the ordering is based on when data requests a color. The package you are using should always do this in the same order, if this isn't the case, I would suggest contacting tech support (support@dataminer.services) so they can look further into this issue.
I see Wout – indeed I wasn't expecting that a shift would occur – I've been able to reproduce the behaviour in staging, will check what happens when using the package in PROD and if that's still verified, I'll double check with our support squad – many thanks