Kinetic Layer causes issue with client customization code

knash · February 21, 2024, 7:52pm

Our issue is we have a few folks using Kinetic screens while others are still not there yet. SelectSerialNumberEntry is called by a few screens.

Do you by chance know what the call would be if you use the classic customization? We have found that adding this code breaks the client custom code. Very odd. But the code is needed for the Kinetic layer to work.

Best way forward

 if(request.id == "Erp.UI.SelectSerialNumbersEntry")
  {
      string layerName = "welldamn";
      
      List<string> layers = request.properties.layers.ToList();
      
      layers.Add(layerName);
      
      request.properties.layers = layers.ToArray();
  }

klincecum · February 22, 2024, 12:07am

I have difficulty working with this screen because we don’t use serialization.
I have to set it up for it to work.

Let me think a second and the answer might come to me.

klincecum · February 22, 2024, 12:10am

First thing I would do if I were you is wrap that in a try catch block and put the message somewhere.

Although I’m having difficulty understanding why this would affect smart client code at all, since that is on Ice.Lib.MetaFX.GetApp, which should be a web client only endpoint.

Are you sure this is where your error lies, or could this just be a red herring?

knash · February 22, 2024, 1:48pm

I agree that the old custom form should still just work, but it doesn’t.

I’ll try and put together a video clip showing the issue. I just enable/disable the BPM and can get the issue to work/break.