Fun fact: if you have an apostrophe in the name/address field of CheckHed, it then becomes impossible to void the check - in the browser. (Does work in classic.)
What happens is that every interactive control on the screen grays out (and the void button, though still blue, becomes unclickable).
I’ll be reporting this now.
Wow… nice catch.
Yeah, because I didn’t want to get anything done today.
Good to know! I know apostrophes play havoc in IDC and ECM, too. So better not to have them in a name at all.
Just my 2 cents 
Unfortunately you can’t control what another company names themselves.
Support says they cannot recreate the issue on 2023.2.19 or 2024.1.5.
I don’t have an environment set up for those releases at the moment.
Anyone feel generous enough to test it? If not that’s fine. I’m ambivalent.
If you do test this, I think the issue is the name on the check itself (CheckHed.Name), not the name on the Vendor table.
I see the same thing on our test instance of 2024.1.4. Everything except the navigation bar on the left of the screen and the address box in the form isn’t interactible. I’m patching up to .5 right now and will check to see if it’s the same.
Thank you - I appreciate it!
Slightly different symptoms on .5. I had to switch to using the client-embedded kinetic screen because I’m having issues logging in with browser, but when I pull up the payment, everything looks OK. The Apply Date and reason code are editable.
But then I click on Reason or Apply Date, the form processes something (marching ants at the top of the screen), then everything is disabled. I can’t even refresh the form or go to the landing page to pull up another payment.
.6 has been posted…in case that matters.
Wild. Thank you so much.
Even on 2023.2.14 I had rather inconsistent results, on the same check but in Production vs. Dev.
Like you say, endgame remains the same - at some point everything is disabled. It’s just when exactly all hope is lost, that will vary.
No offense, but I’d be surprised. Support didn’t say it was fixed per se, just that he could not replicate it on .5.
Invite them to your environment.
No comprende
None taken! It was really for @tsmith who was testing .5…
Give them a login and show them in your environment.
We do it all the time.
And I was looking in the Archives folder on EpicWeb instead of the current release. Thanks for the heads up.
