| Issue Type: |
Status: |
Priority: |
Date Submitted: |
Votes: |
| Bug |
No Longer Required |
High |
Thu 22nd Aug 2013 |
2 votes
 |
| |
| Found in version: |
Last Updated: |
Completed in version: |
Date Completed: |
Track Changes: |
| 5.0.30.1 |
Thu 7th Aug 2014 |
|
|
Log In |
| |
| ice_wanted | | Thu 22nd Aug 2013 03:50 |
Since version 5.0.30 theses function no longer return any values
%object%.Property8.Name
%object%.HeldByWho.Name
%object%.WornByWho.Name
I had to revert to theses functions instead.
%PropertyValue[%object%, Property8]%
%PropertyValue[%object%, HeldByWho]%
%PropertyValue[%object%, WornByWho]% |
| |
| Campbell | | Thu 31st Jul 2014 22:49 |
| Is this still an issue? - it seems to be ok for me. |
| |
| ice_wanted | | Fri 1st Aug 2014 01:18 |
I've re-tested and it does seems ok as you say. Even tried it in a restriction text where I had the problem initially, all good. (maybe fixed in version 5.0.31?)
So in this light, you can close this item. |
| |
| Campbell | | Fri 1st Aug 2014 09:25 |
| Could you send me a sample TAF that has the problem please? |
| |
| ice_wanted | | Wed 6th Aug 2014 19:56 |
I can't reproduce it, so let's close this issue.
One thing I notice however if you perform a check for : %object%.Property1 in a task description but the object used doesn't have property1 assigned, then you get a nasty error box (instead of returning NULL string). The functions following down the text do not resolve any more. I'll post a simple TAF in the forum so you can check it. |
| |
| ice_wanted | | Thu 7th Aug 2014 14:46 |
| As discussed in the forum, version x.32.1 fixed the nasty popup error. However, the return value should be Null or 0 when querying a unassigned property value. Check the forum for the TAF example. |
%object%.Property8.Name no longer returing any value