On 10.2.600, when Epicor calls a post process on Receipt.GetDtlPORelInfo that contains a show message (either in custom code or widget) the message will show twice and then an error message will pop up saying,
The rest of the process will work as intended.
This occurs in 10.2.200 but there is no error message, just a duplicate of the first message.
Also this only occurs on the first release of a PO, any subsequent releases just display the message once.
Does anyone have a clue why this is?
Originally it was structured with custom code but I removed everthing while debugging until it was just the Start widget connected to a show message widget. The message continued to display twice followed by the above error.
I apologize, the project I am working on is a post process and this is where I first encountered the error. After your suggestion I then tested if I could replicate the error in a pre process (Start widget connected to a show message widget to keep it simple) and I did. To summarize, the error occurs in both pre and post so moving my project between the two isn’t an option. For the time being I have jury rigged a workaround that utilizes the post process without a show message (to avoid the error) and some code on a customization to display the message separately but it’s definitely not a long term solution.
I have verified that the dataview values are correct and that the code works as intended when a Show Message is not present in the BPM. As soon as a show message is placed in the release bpm it causes the message to run twice and then display the error above. Also it should be noted that, according to a trace, the bpm itself is not running twice.
Thank you for the documentation. I just tried this and it worked for the most part, it returned what I wanted it to and displayed the message without error. The only issue is that it doesn’t update when the line is changed, so POs with multiple lines don’t update like it did with the publish and subscribe. This code is for displaying comments from PODetail on receipt entry so having the dataview update on line update is important.