nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

onReplicantDelete (after)

nipper

So I am using a field in 1 replicant to populate a list. My onChange event (field) and onReplicantAdd both call the same function to regen the list.

But know I want to be able to, if a replicant is deleted, remove the entry. Easy I thought, onReplicantDelete call the same function. But No. This runs before the replicant is deleted.

Is there an event I can trap after it is deleted ? I know I can write a different function for delete only (and would need t filter out the yet to be deleted replicant).

Is there a better way ?

Find more posts tagged with

Comments

tejul

No i didn't see any event after a deletion of replicant...
What you mentioned is probably the simpliest way to achieve what you want to do.

kaalraa

So I am using a field in 1 replicant to populate a list. My onChange event (field) and onReplicantAdd both call the same function to regen the list.
But know I want to be able to, if a replicant is deleted, remove the entry. Easy I thought, onReplicantDelete call the same function. But No. This runs before the replicant is deleted.
Is there an event I can trap after it is deleted ? I know I can write a different function for delete only (and would need t filter out the yet to be deleted replicant).
Is there a better way ?

Andy,

I think, someone should ask this as a feature addition like BeforeReplicantAdd, AfterReplicantAdd, BeforeReplicantDelete and AfterReplicantDelete.

As of now, this is not supported. However, i can bet that you know how to make it supported for your application.

ISCBorisB

So I am using a field in 1 replicant to populate a list. My onChange event (field) and onReplicantAdd both call the same function to regen the list.

But know I want to be able to, if a replicant is deleted, remove the entry. Easy I thought, onReplicantDelete call the same function. But No. This runs before the replicant is deleted.

Is there an event I can trap after it is deleted ? I know I can write a different function for delete only (and would need t filter out the yet to be deleted replicant).

Is there a better way ?

If your circumstances allow little hacks you may use Listeners. There, 'onItemRemoved' fires after removal.

If you do, make sure that:
a) You register an event listener only once and
b) Check an event source to filter out *false positives* (you will catch a removal of any replicants, not only desired ones)

parent.IWDCEventRegistry.addListener('onItemRemoved', removeItemHandler);
...
function removeItemHandler(item) {
   // Check if you care...
   var xpath = getXPath(item);
   if (xpath.match('YourCollectionPattern')) {
      ...
   }
}

Aryan

I do not intend to intrude buty the approach suggested by ISCBorisB interests me...never tried it before..... ISCBorisB, would you have the time tio eloborate it a bit further? That would be great... Forgive me if it is an "RTFM" stuff

If your circumstances allow little hacks you may use Listeners. There, 'onItemRemoved' fires after removal.

If you do, make sure that:
a) You register an event listener only once and
b) Check an event source to filter out *false positives* (you will catch a removal of any replicants, not only desired ones)

Code:

[left]parent.IWDCEventRegistry.addListener('onItemRemove d', removeItemHandler);...function removeItemHandler(item) { // Check if you care... var xpath = getXPath(item); if (xpath.match('YourCollectionPattern')) { ... }}[/left]

ISCBorisB

I do not intend to intrude buty the approach suggested by ISCBorisB interests me...never tried it before..... ISCBorisB, would you have the time tio eloborate it a bit further? That would be great... Forgive me if it is an "RTFM" stuff

IWDCEventRegistry is FormAPI's fairly low-level class for manipulating replicant Containers (among other things).

Although there are some indications that IWOV contemplated opening that interface to the users that never happened.
Instead, starting with 6.5 replicant related API has been added to IWEventRegistry, that's what you should normally use.
Couple IWOV KB Articles that illustrated IWDCEventRegistry usage for replicant manipulation in TS 6.1 were either removed
or made "internal" ( At least I can not find them anymore ). There are several Forum's posts on that as well.

This mechanism is still alive and well in TS 6.1/5/7. It is however unsupported and is subject to change without notice.
HTH

enthusiast

Does the following still works?

parent.IWDCEventRegistry.addListener('onItemRemoved', removeItemHandler);

I see that last posting of that item was back in 2007. I tried to use this hack yesterday and it does pass the item to the declared method however the getXPath or getName methods fail to get the path of the item. Any help on that would be greatly appreciated.

dial value show.rptdesign

ISCBorisB

Does the following still works?

parent.IWDCEventRegistry.addListener('onItemRemoved', removeItemHandler);

I see that last posting of that item was back in 2007. I tried to use this hack yesterday and it does pass the item to the declared method however the getXPath or getName methods fail to get the path of the item. Any help on that would be greatly appreciated.

Please remember that all this stuff is an undocumented hack. I do not know what are the Classes of the parameters passed to the Listener handler
(up to three objects are passed: item, sourceItem [,originID]). It is however not "IWItem". Depending on TS Version they may or may not have Class.getName(),
Class.getXPath() or any other FormAPI methods.

Try couple attributes (not methods!) like item.name, item.replicantInstanceNumber etc