Skip to main content
On the backlog

Handle translations Case Sensitive

Related products:Software Factory
Robert Jan de Nie
Jeroen van den Belt
Kevin Horst
Robbert van Tongeren
+16
  • Robert Jan de Nie
    Robert Jan de Nie
  • Jeroen van den Belt
    Jeroen van den Belt
  • Kevin Horst
    Kevin Horst
  • Edwin Saan
  • Robbert van Tongeren
    Robbert van Tongeren
  • Michael
    Michael
  • Mark Jongeling
    Mark Jongeling
  • Hugo Nienhuis
    Hugo Nienhuis
  • Dennis Beeren
  • Frank Junger
  • Henno Tillema
  • Theo Neeskens
    Theo Neeskens
  • C. Lousberg
    C. Lousberg
  • PeterKeeris
  • Dick van den Brink
  • Reitze Bok
    Reitze Bok
  • AndreKemmeren
    AndreKemmeren
  • Marius Korff
    Marius Korff
  • Theo Leijen
  • BramG
  • Ionut
    Ionut

C. Lousberg
Captain

The SF/IAM databases are Case insensitve (Latin1_General_CI_AS) by default.

As we sometimes make some mistakes (who doesn't), we'd like to correct the cases in translations.

E.g. cange “Purchase order” to “Purchase Order”.

 

Currently there are 2 workarounds:

  • update the records in transl table
  • or, change to “Purchase Order1”, sync to all IAM's and change to correct “Purchase Order”

 

The idea we'd like to see implemented is that a collate Latin1_General_CS_AS compare takes place and also the update will take place in this collation so the correct cases will be stored.

Did this topic help you find an answer to your question?

3 replies

Mark Jongeling
Administrator
Forum|alt.badge.img+23
Updated idea statusNewOpen

Jeroen van den Belt
Administrator
Forum|alt.badge.img+9
OpenOn the backlog (research phase)

Forum|alt.badge.img+4
  • Warrior
  • 38 replies
  • July 10, 2025

The annoying part is, when you would do a workaround in a development branche and would sync it to a target branche, the merge session will NOT see the conflict and not update the translation in your target branche. 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings