Known Limitations
This page lists specific language and regional support limitations in Altus custom components, along with workarounds where available.
Note
These are not bugs — they represent areas where language and regional support has not yet been implemented. They are tracked on our development roadmap.
Date and Calendar Display
| Limitation | Impact | Workaround |
|---|---|---|
| Date picker controls display English month and day names | Calendar popups show "January", "Monday", etc. regardless of user language | None currently. Dates are stored correctly regardless of the display language. |
| Timesheet displays dates in a fixed English format | The Timesheet header shows dates as "Mon, Jan 15 2024" rather than a locale-specific format | None. The underlying date values are correct; this is cosmetic only. |
| Dashboard date display uses British English formatting | The Dashboard shows dates in a fixed format with English ordinal suffixes (e.g. "15th January") | None. Cosmetic only. |
Data Import and Processing
| Limitation | Impact | Workaround |
|---|---|---|
| Schedule import may interpret dates based on server locale | When importing MPP files, date parsing uses the server's regional settings rather than the user's personal settings | Use ISO 8601 date formats (YYYY-MM-DD) in source files where possible. |
| Numeric data parsing may be affected by server locale | Bulk data imports may interpret decimal separators (. vs ,) based on the server configuration | Ensure source data uses period (.) as the decimal separator. |
User Interface Text
| Limitation | Impact | Workaround |
|---|---|---|
| Custom component labels are in English only | All button labels, column headers, tooltips, and messages within Altus custom components appear in English | None currently. Translation infrastructure is in place; additional languages will be added progressively. |
| Error messages are in English only | Technical error messages and notifications are displayed in English | None. Error messages are primarily for support purposes and include technical details that aid troubleshooting. |
Layout and Script Support
| Limitation | Impact | Workaround |
|---|---|---|
| Right-to-left (RTL) layout is not supported | Languages such as Arabic and Hebrew require right-to-left text flow, which Altus custom components do not currently support | None. RTL support is on our development roadmap. |
Found Something Not Listed Here?
If you encounter a language or regional issue that is not listed on this page:
- Check your Personalisation Settings in Dynamics 365 to confirm your regional format is configured correctly.
- Check the organisation-level format settings — see Platform Regional Settings.
- If the issue is with a standard Dynamics 365 form or view (not an Altus custom component), it may be a platform configuration issue rather than an Altus limitation.
- If none of the above resolve the issue, please submit an idea on Product Board so we can track demand and prioritise accordingly.