OpFind DAT relative path bug 099|2620
Not sure but seem like the relative path option not working…
instead the relative path to be “container1/geo1”
or “./geo1”
it gives “geo1”
added simple case.
opFindRealtibePathBug.toe (4.28 KB)
OpFind DAT relative path bug 099|2620
Not sure but seem like the relative path option not working…
instead the relative path to be “container1/geo1”
or “./geo1”
it gives “geo1”
added simple case.
opFindRealtibePathBug.toe (4.28 KB)
The relative path in OP Find is the intended behavior. It’s relative to the node in this way:
If op(‘container1’) is the node that’s in your OP Find path,
then op(‘container1’).op(‘geo1’).path
gives correctly:
/project1/container1/geo1
(so you can fetch the relative path from the OP Find table cell)
If you put in a parameter on container1:
me.op(‘geo1’)
you also get:
/project1/container1/geo1
For your example you can use an absolute pah, or use an Evaluate DAT to add in ‘./’.
Thank you.