-
Notifications
You must be signed in to change notification settings - Fork 24.9k
Add localization/decimal separator note to Part 5 (Working with SQL) for non-English locales where comma vs. dot causes Price editing issues #33793
Copy link
Copy link
Open
Labels
Source - Docs.msDocs Customer feedback via GitHub IssueDocs Customer feedback via GitHub Issueai-backlog-handling-pre-1-1-26Used for a 2026 project for identifying old backlog issues copilot could handleUsed for a 2026 project for identifying old backlog issues copilot could handleai-triage-action-planAssigned when an AI generated triage and action plan report is created for an issue.Assigned when an AI generated triage and action plan report is created for an issue.doc-bugseQUESTeredIdentifies that an issue has been imported into Quest.Identifies that an issue has been imported into Quest.
Description
Description
Verbatim:
The view shows prices with a comma while the database is a dot. When you edit, you can't put anything behind the dot, it removes it, so 19.99 becomes 1999,00
Page URL
Content source URL
Document ID
a0b5e15c-d747-8710-95fb-a55c09861a1e
Article author
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Source - Docs.msDocs Customer feedback via GitHub IssueDocs Customer feedback via GitHub Issueai-backlog-handling-pre-1-1-26Used for a 2026 project for identifying old backlog issues copilot could handleUsed for a 2026 project for identifying old backlog issues copilot could handleai-triage-action-planAssigned when an AI generated triage and action plan report is created for an issue.Assigned when an AI generated triage and action plan report is created for an issue.doc-bugseQUESTeredIdentifies that an issue has been imported into Quest.Identifies that an issue has been imported into Quest.