|
|
 New Property Restriction
| Issue Type: |
Status: |
Priority: |
Date Submitted: |
Votes: |
| Enhancement |
Open |
Medium |
Fri 27th Jul 2012 |
3 votes
 |
| |
| Found in version: |
Last Updated: |
Completed in version: |
Date Completed: |
Track Changes: |
| 5.0.24 |
Thu 17th Dec 2015 |
|
|
Log In |
| |
| ElliotM | | Fri 27th Jul 2012 17:04 |
Right now, you can check the value of a single property as a restriction, but I think it would be useful to also be able to compare the values of two properties, whether they belong to the same entity or different ones.
The only selection restriction I think that would be needed for programming this would be that the two properties must be the same type, ie., object list, state list, selection, etc.
PropertyX of [location/character/object][must/must not] be equal to the value of PropertyY of [location/character/object]
|
| |
| ElliotM | | Tue 15th Dec 2015 03:57 |
| A work around for this might be to dynamically add items to a group by the value of a property you want to compare. If both items are in the group, then it is the same as 'PropertyX of X is equal to PropertyX of Y'. |
| |
| saabie | | Thu 17th Dec 2015 02:08 |
You can also use an Expression Restriction to do this, eg:
JohnSmith.PropertyX = JohnSmith.PropertyY
|
| |
| ElliotM | | Thu 17th Dec 2015 05:18 |
| Even better, that'd work great as a workaround for the time being. |
|
