Kinetic Application Layer - extendedProp disabled icon appearing on slide out panel

James_OToole · July 11, 2023, 6:35pm

I have created a customer Erp.UI.SalesOrderEntry layer with the following settings, effectively hiding “Attachments”, “Change Log”, “Memos”, and “Call Log” icons from the toolbar.

  {
    "Id": null,
    "Path": "/navigation/extendedProps/disableAttachments",
    "Value": true,
    "Operation": "Add",
    "Index": 0
  },
  {
    "Id": null,
    "Path": "/navigation/extendedProps/disableChangeLog",
    "Value": true,
    "Operation": "Add",
    "Index": 0
  },
  {
    "Id": null,
    "Path": "/navigation/extendedProps/disableMemos",
    "Value": true,
    "Operation": "Add",
    "Index": 0
  },
  {
    "Id": null,
    "Path": "/navigation/extendedProps/disableCallLog",
    "Value": true,
    "Operation": "Replace",
    "Index": 0
  },

When I preview the layer, the icons are not there as expected.

However, when I call the “Details” page on this same layer from an “isLink” on Erp.UI.OrderAllocEntry, the icons are there.

In addition, if I hide something in the overflow menu on Erp.UI.SalesOrderEntry, it’s still visible in the slide out panel on Erp.UI.OrderAllocEntry.

How do I get these settings to persist on the slide out panel?

hmwillett · July 11, 2023, 6:42pm

Those are different forms.
You would need to create a layer for OrderAllocEntry, hide it there, and then have the app call that layer.

James_OToole · July 11, 2023, 6:45pm

I have a custom layer for Erp.UI.OrderAllocEntry from which I am calling a custom layer of Erp.UI.SalesOrderEntry.

Based upon what you are saying, I would need to create a custom slide out panel on the Epr.UI.OrderAllocEntry custom layer that would be called by the isLink?

hmwillett · July 11, 2023, 6:47pm

Don’t get hung up on the slide out panel. It’s launching a new form, but there’s a checkbox to allow you to open it in a slide out panel vs a new tab. Whatever form that slide out panel is will need the custom layer hiding those buttons.

For example, if I’m in Sales Order Entry and I have an event that fires and opens Part Entry in a slide out, if I want to do anything custom to that slide out, I have to do it in Part Entry and have the event on the Sales Order Entry side call that custom layer.

James_OToole · July 11, 2023, 6:54pm

Okay. Good. So that’s what I think I have at the moment. My apologies if I am still missing the point.

I created a custom layer for Erp.UI.SalesOrderEntry (SOCustom).

From the custom layer for Erp.UI.OrderAllocEntry, I call SOCustom.

SOCustom isn’t showing the icons in Preview but is showing them when called in the slide out.

klincecum · July 11, 2023, 6:56pm

what does it say in debug when you call it? Is it requesting your layer?

James_OToole · July 11, 2023, 7:04pm

The custom layer appears to be the layer being called. Note, I shortened the name of the customer layer in my previous post. The actual name of the layer is what appears in the log below.

hmwillett · July 11, 2023, 7:04pm

This may or may not be related, but will absolutely bite you going forward: change the View to be the Menu ID (Example. OMT1000 or whatever).
They are deprecating the use of the program DLL name because it circumvents the menu security.

James_OToole · July 11, 2023, 7:07pm

Thank you for that.

If I use the Menu ID of a tracker will it open as a tracker? I also have a need to open as a tracker but can’t seem to figure out how to do that either…beyond the current issue at hand.

hmwillett · July 11, 2023, 7:09pm

Yes, it should.

Create a menu for Erp.UI.SalesOrderEntry and make sure the “Read Only” checkbox is marked in Menu Maintenance, then call that Menu ID with the app-open widget.