When business logic refers to data that has a ref attribute, ArcRAVE needs the ability to go find that referenced dataset elsewhere in the project. (QRAVE already does this.)
In python we do it this way:
https://github.com/Riverscapes/QRAVEPlugin/blob/dev/src/classes/project.py#L304-L361
Update:
I had to create a sample test project and business logic to test this
It's in nardata at the path nardata/Matt/RefProject.zip (80 Mb)
Two things to check:
When business logic refers to data that has a
refattribute, ArcRAVE needs the ability to go find that referenced dataset elsewhere in the project. (QRAVE already does this.)In python we do it this way:
https://github.com/Riverscapes/QRAVEPlugin/blob/dev/src/classes/project.py#L304-L361
Update:
I had to create a sample test project and business logic to test this
It's in
nardataat the pathnardata/Matt/RefProject.zip(80 Mb)Two things to check:
ref=still load normallyref=get the right lookup and appear in the treeref=