Skip to main content
Answer

unknown column error on project dashboard

  • June 24, 2024
  • 4 replies
  • 78 views

iqraharrison
Captain II
Forum|alt.badge.img+8

Hi!

looking at the project dashboard in the sales demo, I am getting this error when switching between projects.  I have a feeling this is in regards to a table but I am not sure.  Has anyone seen this and been able to resolve?

 

Best answer by iqraharrison

@Chris Hackett hi! i ended up submitting a ticket to acumatica.  we found that MySQL was causing issues.  I worked with our internal IT department to set up the local and cloud hosted instances with the MS SQL and we no longer had any issues!  We also noticed an increase in the instance’s speed!

I provided acumatica with all the details and they escalated it to the development to look into, however, we were able to close the case since our issue was resolved by changing the database type

thanks!

4 replies

nhatnghetinh
Captain II
Forum|alt.badge.img+11

Hi @iqraharrison 

I tried with version 2023.R1 and it works well.

 

 

Best Regards,

NNT


iqraharrison
Captain II
Forum|alt.badge.img+8
  • Author
  • Captain II
  • June 26, 2024

@nhatnghetinh hi! this is happening in 24R1 build 4 and 5 (at least that’s where i’ve tested it) but I just met with acumatica to discuss this and it seems to be working on the version 24.100


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • July 31, 2024

Hi @iqraharrison were you able to find a solution? Thank you!


iqraharrison
Captain II
Forum|alt.badge.img+8
  • Author
  • Captain II
  • Answer
  • August 1, 2024

@Chris Hackett hi! i ended up submitting a ticket to acumatica.  we found that MySQL was causing issues.  I worked with our internal IT department to set up the local and cloud hosted instances with the MS SQL and we no longer had any issues!  We also noticed an increase in the instance’s speed!

I provided acumatica with all the details and they escalated it to the development to look into, however, we were able to close the case since our issue was resolved by changing the database type

thanks!