Skip to main content
Solved

Custom Grid on Added Employee Tab Not Working on 24R1


Forum|alt.badge.img+1

Hello,

I have a custom table that I am showing on the ‘Employees’ screen as a new tab. It has one key ID designated with the [PXDBIdentity(IsKey = true)] attribute in the DAC. It worked in 23R1 but now that I have it published in 24R1 none of my event handlers are firing on the tab and when I attempt to add a value in one column the row effectively resets and I lose all my data.

I should note that I also have a maintenance screen with the exact same logic pointing to the same DAC- just not filtered by the employee- and all the logic works and saves to the DB without any error.

  • Since 24R1 added a bunch of permission defaulting, my first spot was to check there but no luck. I have the rights on the view set to DELETE so it shouldn’t be a permission issue.
  • I also deleted all my event handlers to where the only code I had in my employee graph ext was the view itself and I am still getting the error. 
  • I ran the request profiler and have not been able to get consistent results but a few times I have gotten the following (note that I don’t have a clear indication if these are related as they are not consistently showing up and might have been a one time thing):
    • The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters. (Note: I am not dealing with Base-64 directly anywhere in my code and I do not have a PXImport attribute set as I know that did change in 24R1).
    • Value cannot be null.\r\nParameter name: key (I feel like there is something where the key value of the record isn’t binding appropriately with the screen- this would explain the behavior but I have no clue how to fix it).

Any help would be much appreciated, thanks!

Best answer by rhooper91

Figured it out- it was an Acumatica base code issue. As mentioned before, I got it to work on another instance which was deployed as 24.093.0169 build and it worked. I wanted to see if it was an instance bug or a version bug so I upgraded the issue instance from 24.104.0008 to latest (24.111.0011) build and it works. So I guess moral of the story, be careful working 24.104.0008- without reading through all the dev notes, I couldn’t say when it was broke and when it was fixed other than it was working in 24.093.0169, broke in 24.104.0008, and fixed again in 24.111.0011.

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

3 replies

Forum|alt.badge.img+1
  • Author
  • Varsity III
  • 64 replies
  • August 22, 2024

Update, I installed in a new 24R1 local instance and now no issue.. what could cause the disparity between two instances where one works and another does not? I would like to understand the reason before I publish into a production environment, any insight would greatly be appreciated before I close this out!


Forum|alt.badge.img+1
  • Author
  • Varsity III
  • 64 replies
  • Answer
  • August 26, 2024

Figured it out- it was an Acumatica base code issue. As mentioned before, I got it to work on another instance which was deployed as 24.093.0169 build and it worked. I wanted to see if it was an instance bug or a version bug so I upgraded the issue instance from 24.104.0008 to latest (24.111.0011) build and it works. So I guess moral of the story, be careful working 24.104.0008- without reading through all the dev notes, I couldn’t say when it was broke and when it was fixed other than it was working in 24.093.0169, broke in 24.104.0008, and fixed again in 24.111.0011.


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • 2657 replies
  • August 26, 2024

Thank you for sharing your solution with the community @rhooper91!


Reply


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