Kinetic 2023.1 PublishInfoMessage not working anymore

[shuotonashi (Victor Hugo Garcia Rocha)]

Hi All,

We have recently updated Epicor to Kinetic 2023.1 (We were using Kinetic 2022.1) today I continue debugging some code I left pending before the update and noticed that all PublishInfoMessage are not working anymore.
Here’s my code.

this.PublishInfoMessage(
                "TEST",
                Ice.Common.BusinessObjectMessageType.Information,
                Ice.Bpm.InfoMessageDisplayMode.Individual,
                "",
                ""
            )

This is what i have tried a and hasn’t worked:

• Clearing all the code leaving only the PublishInfoMessage part
• Using grid instead of individual message
• Asked a coworker to show a message from his code
  Also read new article: What’s New in This Release - Controlled Release Version but there is nothing related to this.

Hope someone knows anything about this.

[josecgomez]

The InfoMessage box now has debug only checkbox I wonder if its defaulted On

[shuotonashi (Victor Hugo Garcia Rocha)]

The message widget does have that flag but have you tried setting that flag in c# code instead of the widget?
I thought that maybe this flag would do something but It doesn’t.

[josecgomez]

Worked fine for me 2023.1

            var messageTextBuilder = new System.Text.StringBuilder();
            
            messageTextBuilder.Append("Process: ");
            messageTextBuilder.Append(this.callContextClient.ProcessId);
            messageTextBuilder.Append("\r\nAssembly: ");
            messageTextBuilder.Append(this.callContextClient.AssemblyName);
            
            var messageText = messageTextBuilder.ToString();
        
            this.PublishInfoMessage(messageText, Ice.Common.BusinessObjectMessageType.Information, Ice.Bpm.InfoMessageDisplayMode.Individual, "ABCCode", "Update");

[klincecum (Kevin Lincecum)]

Are you trying to call a messagebox from a function?

Depending on how it is called, it can show up, but many times it won’t be triggered.
The UI has to have a way to catch it.

[shuotonashi (Victor Hugo Garcia Rocha)]

Yes, from a function. I know it worked before the upgrade. I’m placing @josecgomez snippet in different parts of my function to see it works.

[shuotonashi (Victor Hugo Garcia Rocha)]

Okay the PublishInfoMessage works in a method directive. (Payment Entry → Update)

[klincecum (Kevin Lincecum)]

@shuotonashi

different parts of my function

I’d replace the entire function with just a message box.

[klincecum (Kevin Lincecum)]

@shuotonashi

I know it worked before the upgrade

Are you sure? Are you testing it the same exact way?

[shuotonashi (Victor Hugo Garcia Rocha)]

Yes, no code modifications. Just called my function as usual to see where I left it at (Messages will give me information) but nothing showed up.

[klincecum (Kevin Lincecum)]

@shuotonashi

as usual

Which is how?

[shuotonashi (Victor Hugo Garcia Rocha)]

Click a custom button to select data from payment entry table and show it in a message.
I replaced the retireved text for a fixed value “TEST”.
Also replaced the whole code for the snippet Jose provided.
Nothing worked.

[klincecum (Kevin Lincecum)]

@shuotonashi

Click a custom button

Classic or Kinetic?

How do you know the function fired?

[shuotonashi (Victor Hugo Garcia Rocha)]

Kinetic.
I know the function is fired because I can thwo an exception from it.

throw new Ice.Common.BusinessObjectException(
                new Ice.Common.BusinessObjectMessage("TEST")
                    {
                        Type = Ice.Common.BusinessObjectMessageType.Error,
                    });

[klincecum (Kevin Lincecum)]

Let’s isolate it a bit further.

Make a new layer on a completely different screen and call it.

[klincecum (Kevin Lincecum)]

Also, if you open up the dev-tools in the browser, you should be able to find where the function was called in the network tab. Look in the response headers under CallContext.

You should see if data is being returned. If it is in there, something else is wrong.

[klincecum (Kevin Lincecum)]

Calling a Function from Custom code

If you are getting an error in swagger there is something wrong with your function or your input to your function. Messages come back in the response headers (as shown below) [image] [image]

Look at this picture from this post:

[josecgomez]

I’m not sure that Info message was ever supposed to work in a function… Functions are mostly to be invoked via REST I’m not sure how that would translate to a Kinetic Layer… It seems you said it worked before but from a design perspective it doens’t make sense to me.

Epicor functions are independent of the UX

[shuotonashi (Victor Hugo Garcia Rocha)]

We have abrand new instance aht uses kinetic 2022.2 I will try with that version and let you know.

[HLalumiere (Hugo Lalumiere)]

Rule #1 of Functions, and Directives, is put a try…catch block around your code. My guess is some of your other code is throwing and failing silently.