Invalidate action Component ID uses GUID

Kinetic ERP
1

I assume the GUID that is in the Component ID on the property-set widget under Parameter > Props

image
image724×234 10.2 KB

that sets the invalidated value under
to ‘invalidated’ is likely the GUID for the Grid that is going to be triggered to refresh.

image
image386×295 3.11 KB

It’s for sure not the Id on the grid -
image
image629×439 11.5 KB

I suppose it could be the GUID for the DataView but other than picking through the JSON, not sure how to find it.

I tried using the Debugger and CTRL+ALT+L to show all components but that did not work, nothing happens and Yes, I had debugging turned on and Yes I was focused on an active control.

2

Anyone know where to find this?

1 Like
3

What are you trying to do, I had trouble getting invalidated to work the other day as well.

1 Like
4

Just trying to trigger the invalidate property so the grids reload based on a custom event workflow. I wound up is just building a new app using the app wizard. The generated events are not locked to it’s pretty simple to change the workflow.

Where we are stuck is in the converted dashboards from classic. Those have locked events so to be able to set the invalidated property on any view/grid to automatically refresh is the goal.

If I have 5 different BAQ’s to manage, not knowing what that GUID is for each is a show stopper for using the invalidated property to auto refresh.

2 Likes
5

Are these grids bound to a provider model?

1 Like
6

Would love to know this as well. Ran into it investigating a system app the other day. Found it a dead end and gave up. Thinking maybe search MetaUI app definition for guid. :man_shrugging:

7

I have gotten this to work before by filling in the grid id with my own value and referencing that. I can’t remember where I did it so I don’t have a screenshot at this moment. But I remember it worked.

1 Like
8
2 Likes
9

Ahhh. GridModel.Id not panelcardgrid.id :+1:

1 Like
10

Yes it was a PITA for me to figure it out but works like a charm once I did.

2 Likes
11

Yes they are. I’m pretty sure they have to be in order for the invalidate technique to work.

12

Sorry, didn’t read to the bottom. Sound’s like we can wire up our own invalidate action and just add the grid Id in the Component Id. Let me know if I am misunderstanding your responses.

13

geesh. looks like grid id could be lotsa things. :wink: :man_shrugging:

  getGridId(a) {
      var u, g;
      let y;
      return y = a.panelCardGrid && a.panelCardGrid.multiGrid ? a.providerModel && a.providerModel.id && a.panelCardGrid.model.guid ? a.panelCardGrid.model.guid + "-" + a.providerModel.id : a.panelCardGrid.model.guid && a.defaultViewProvider.id ? a.panelCardGrid.model.guid + "-" + a.defaultViewProvider.id : a.id + "-" + a.defaultViewProvider.id : a.guid ? a.guid : a.panelCardGrid && a.panelCardGrid.model.guid ? a.panelCardGrid.model.guid : a.id,
      null !== (u = a.userData) && void 0 !== u && u.dynamicAttrClassId ? y + "-" + (null === (g = a.userData) || void 0 === g ? void 0 : g.dynamicAttrClassId) : y
  }