It would not be straightforward or expected to be able to do this...
... but I may be misunderstanding what you are trying to achieve!
Whenever the 'other' node was subsequently republished, it would have its examine index refreshed and so would not know about the previous change to its index triggered by your original TransformingIndexValues event...and so any updated value would be lost.
But you could in your TransformingIndexValues event for the 'other' node, look at the content on the original node that triggers this corresponding update, and keeps the value in it's index in sync with the original node...
...and so then what you are looking to solve is a different problem - eg how to trigger the 'other' node to be published, whenever the original one is published, which could be handled in a Saving or Publishing Notification.
But hard to know what the values are that you are trying to share across indexed items...
Examine - TransformingIndexValues event, update a custom field on a different indexed node
I'm using the TransformingIndexValues event to add custom information to an Examine index. Easy enough with e.Fields.Add("name",value) in same node.
However, inside my TransformingIndexValues event, I also need to update the index value for different node.
Possible?
Hi neerajsaini999
It would not be straightforward or expected to be able to do this...
... but I may be misunderstanding what you are trying to achieve!
Whenever the 'other' node was subsequently republished, it would have its examine index refreshed and so would not know about the previous change to its index triggered by your original TransformingIndexValues event...and so any updated value would be lost.
But you could in your TransformingIndexValues event for the 'other' node, look at the content on the original node that triggers this corresponding update, and keeps the value in it's index in sync with the original node...
...and so then what you are looking to solve is a different problem - eg how to trigger the 'other' node to be published, whenever the original one is published, which could be handled in a Saving or Publishing Notification.
But hard to know what the values are that you are trying to share across indexed items...
regards
Marc
is working on a reply...