Single Piece Property "Send To Location" Issue

Technical Support & Bugs
1

While using 3.2.0 —

When trying to use “Send to Location” to another counter based on properties, I observed erratic results. If I used more than one property as a selection criteria,

BasicName = PurchasePoint && CurrentMap= $CurrentZone$

it would either not work or send to an incorrect counter. I was able to get it to perform the way I wanted by creating a calculated property representative off all the necessary criteria on both the sending and receiving counter and using the calculated property. I tried several permutations and it eventually started sending the unit to random destination counters. I’ve never used the send to another counter before so I don’t know if this issue exists in previous versions.

2

CurrentMap = $CurrentZone$ looks weird…
Do you mean you have Zones in a map with names corresponding to those of other maps?

3

That is correct. When I’m one map, I drag a counter to a zone labeled with the name of another map as that is the location I wish to send the counter when placed in that zone.

4

Thus spake MKerby:

While using 3.2.0 —

When trying to use “Send to Location” to another counter based on
properties, I observed erratic results. If I used more than one
property as a selection criteria,

BasicName = PurchasePoint && CurrentMap= $CurrentZone$

it would either not work or send to an incorrect counter. I was able to
get it to perform the way I wanted by creating a calculated property
representative off all the necessary criteria on both the sending and
receiving counter and using the calculated property. I tried several
permutations and it eventually started sending the unit to random
destination counters. I’ve never used the send to another counter
before so I don’t know if this issue exists in previous versions.

Are you still having a problem with this in 3.2.6? If so, could you
post a minimal test module demonstrating it?

–
J.