Skip to main content
Answer

Organization Localization Code cannot be empty error

  • May 10, 2024
  • 8 replies
  • 62 views

Forum|alt.badge.img+3

Hello all,

I have been trying to create a new branch but whenever I try to save it, throws the following error:

 

Trace

How can I resolve this issue?

Best answer by harshitasethia74

Turn on the Canadian Localization in Enable/Disable features screen, then in the company settings set the localization to NONE. This will get fixed.

8 replies

Manikanta Dhulipudi
Captain II
Forum|alt.badge.img+15

Hi @Harshita 

Did you restart the application and verify this issue?

Can you check if any customization in branch screen


Forum|alt.badge.img+3
  • Author
  • Captain II
  • May 10, 2024

Hi @Harshita 

Did you restart the application and verify this issue?

Can you check if any customization in branch screen

Hello @manikantad18 , we dont have any customizations. Also, regarding restarting the application does it mean to restart the IIS? or what?


Manikanta Dhulipudi
Captain II
Forum|alt.badge.img+15

Navigate to APPLY Updates and restart APPLICATIONS.

 

Which version of Acumatica using?


Forum|alt.badge.img+3
  • Author
  • Captain II
  • May 10, 2024

Ok I will follow your suggestion & update you. Below is the current version:
 

 


Forum|alt.badge.img+3
  • Author
  • Captain II
  • May 10, 2024

Navigate to APPLY Updates and restart APPLICATIONS.

 

Which version of Acumatica using?

Hello @manikantad18 , it still throws the same error. The thing is we recently upgraded it from 2022R2 to 2024R1.


Manikanta Dhulipudi
Captain II
Forum|alt.badge.img+15

The table changed in the Upgrade,

Can you help me with the screenshot of Branch what you are creating.


Forum|alt.badge.img+3
  • Author
  • Captain II
  • May 10, 2024

 

There’s only one company & we already have 6 branches created, and now after upgrade only it is triggering this error.


Forum|alt.badge.img

Turn on the Canadian Localization in Enable/Disable features screen, then in the company settings set the localization to NONE. This will get fixed.