When selecting a date in a time zone, which attribute is not influenced by localization?

When dealing with data selection in a time zone within Mendix, the concept of localization is crucial to understanding how different attributes handle data representation. The non-localized attribute is utilized for data that remains consistent regardless of the user's locale or time zone settings. This means that when a date is selected based on a user's local time, the underlying representation of that date does not change according to the user's localization settings.

For example, when storing or working with dates or times, a non-localized attribute will always maintain a fixed reference, ensuring that the underlying data remains the same regardless of how different users might perceive or interact with it based on their geographic location or system settings. This makes non-localized attributes particularly useful in scenarios requiring uniformity and consistency across various contexts.

In contrast, a localized attribute is specifically designed to adapt to a user's locale, reflecting differing formats or values based on cultural or regional settings. A microflow's output can also be influenced by the context in which it is executed, taking into account user-specific settings. Similarly, database field types follow the general rules of localization, whereby date and time data might be stored or represented differently based on locale-specific factors.

Therefore, non-localized attributes stand out as the ones that remain unaffected by localization