Let’s clarify @hmwillett & @Mikec63
Hannah, did you try InfoMessage.Publish as well?
Mike, have you tested both ?
Nope–didn’t bother as others have stated that it’s no longer the one to use.
Pretty sure the “accepted” solution was to just switch to PublishInfoMessage.
Just to appease you, InfoMessage still does not work.
Yes, neither worked and I have it on the 1st step of parttran basic.
Thx
mc
No, it’s just a bug. It’s supposed to be fixed in 2023.1.6, and in cloud in 2023.1.5.
So I just answered it by typing that lol. You aren’t on cloud with 2023.1.5, so I’ll upgrade
my environment and see what’s up.
then you have something else wrong
What do you mean by this?
Hurry up Matt, you’re killing me.
I’m on public cloud 2023.1.5 and can confirm InfoMessage.Publish() did not work before and now it does.
On the topic of which is better to use I really do find uses for both InfoMessage.Publish() and this.PublishInfoMessage() and hope they both continue to work. 99% of the time I just need to pop a simple message without having to deal with other options like the DisplayMode or text on the box header. InfoMessage.Publish() keeps my code more clean and easily readable for the next person to come along especially since the IDE for Epicor is lacking to say the least.
2 Likes
Sweet, I’m gonna back up my new toys I made, and do the upgrade.
I’m using a method directive on parttran. I’ve tried Base and pre processing. Neither fire and this worked before the upgrade to 2023.1.5
What is Parttran Basic?
These are the methods on part tran.
And you should NEVER use Base (ok not NEVER, but it’s quite rare that this is necessary)
I should have not upgraded, now I stuck in some kind of client update loop.
Matt,
Thanks for the confirmation. My method BPMs worked before the upgrade and now they don’t strange.
I’ll keep plugging away. With experience comes bumps, bruises and hair pulling.
thx
mc
Post your BPM so we can take a look at it.
Guess what…
Just tested it in a UBAQ, still broken in 2023.1.5 in the cloud. Supposed to be fixed
for cloud users in 2023.1.5 
Try it in a BAQ if you don’t mind.
Toooooo late. I’m restoring a backup to that environment to run through our upgrade next month. 
There is a regression in 2023.1.8, and it’s worse than before
1 Like