Why is destinationSet is not defined?

[Coooz]

Hi,

The error "destinationSet" is not defined pops up in my channel, and I have no idea why. Below I give the full error details; lines 264 to 266 are in a - well, the only - destination filter, and line 265 was dragged from the Reference tab. Can anybody help me out here? I'm using Mirth Connect 3.11.

Error details:

Filter error
ERROR MESSAGE: Error evaluating filter
com.mirth.connect.server.MirthJavascriptTransformerException: 
CHANNEL:	Just passing through
CONNECTOR:	To 'Pass through to here'
SCRIPT SOURCE:	FILTER
SOURCE CODE:	
260: function doScript() {
261: msg = new XML(connectorMessage.getTransformedData());
262: if (msg.namespace('') != undefined) { default xml namespace = msg.namespace(''); } else { default xml namespace = ''; }
263: function filterRule1() {
264: if (msg['PID']['PID.8']['PID.8.1'].toString() == 'M') {
265:     destinationSet.remove([2]);
266: }
267: }function doFilter() { phase[0] = 'filter'; return ((filterRule1() == true)); }
268: function doTransform() { phase[0] = 'transformer'; logger = Packages.org.apache.log4j.Logger.getLogger(phase[0]);
269: 
LINE NUMBER:	265
DETAILS:	ReferenceError: "destinationSet" is not defined.
	at cc614301-aeeb-4b44-a8f0-7a27d0159b7d:265 (filterRule1)
	at cc614301-aeeb-4b44-a8f0-7a27d0159b7d:267 (doFilter)
	at cc614301-aeeb-4b44-a8f0-7a27d0159b7d:292 (doScript)
	at cc614301-aeeb-4b44-a8f0-7a27d0159b7d:294
	at com.mirth.connect.server.transformers.JavaScriptFilterTransformer$FilterTransformerTask.doCall(JavaScriptFilterTransformer.java:154)
	at com.mirth.connect.server.transformers.JavaScriptFilterTransformer$FilterTransformerTask.doCall(JavaScriptFilterTransformer.java:119)
	at com.mirth.connect.server.util.javascript.JavaScriptTask.call(JavaScriptTask.java:113)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

[odoodo]

destinationSet is currently only available in the scope of the source connector. There is however a feature request to make it also available in the destination connectors.

[Coooz]

That explains a lot. Thank you ododo for pointing this out.