Skip to main content
Question

Question about PXDBLocalizableString override

  • January 23, 2026
  • 5 replies
  • 36 views

I’m using the following version 2025 R2 and Build 25.200.0248. What I have to do is to override the character limit of a PXDBLocalizableString field from another DAC but I keep getting errors. Tried doing it the normal way as a DAC MergeMethod.Merge/Replace but I keep getting a Json de-serialization error. It does work, the DB column is set to the characters limit too but there is an error I’m getting when I try opening the Sales/Purchase Orders which error I think is coming from one of our customizations

5 replies

Forum|alt.badge.img+3

@nikola74 You can share the trace log for more details - it would make it easier to suggest a solution.


  • Author
  • Freshman I
  • January 23, 2026

@nikola74 You can share the trace log for more details - it would make it easier to suggest a solution.

On Save action trigger
When I try opening the Sales and Purchase screens

 


Forum|alt.badge.img+2
  • Jr Varsity III
  • January 24, 2026

@nikola74 ,
                       Can you try like this.
Example:
    [PXDBLocalizableString(50, IsUnicode = true)] // Change from default 40 to 50


Forum|alt.badge.img

@noorula77 ​the issue is while overriding the base DAC not the custome DAC.

@nikola74 can you show the piece of code how the way you are overriding the Field. or Instead of modifying the base DAC field length, you replace it at runtime using CacheAttached.

 


  • Author
  • Freshman I
  • January 24, 2026

@noorula77 ​the issue is while overriding the base DAC not the custome DAC.

@nikola74 can you show the piece of code how the way you are overriding the Field. or Instead of modifying the base DAC field length, you replace it at runtime using CacheAttached.

 

@nikola74 ,
                       Can you try like this.
Example:
    [PXDBLocalizableString(50, IsUnicode = true)] // Change from default 40 to 50

Figured out what the issue was. When the length is more than 255 symbols, its storing the user input into a ValueText column instead of the ValueString. So what I have to do now is replace the string field with a text box but I have to keep the localization functionality