Picker data is not "translated" from local to UaaS
When working on a UaaS project locally, and then transferring content to UaaS, any pickers (media, content, member) used in a Leblender Editor, will no longer refer to the previously selected nodes.
Further inspecting reveals the pickers are still referring to the same node id's as before, but it looks like node id's are different in local and live environment
This seems to be handled if you use pickers as regular property editors as these now refer to the same node as before even though it does not have the same node id as before.
Probably because it needs a data resolver. There is a pull request for one at https://github.com/Lecoati/LeBlender/pull/30. Also note in one of the comments there is a refactored version attached as a zip. I have not used either.
It's been a while since the PR and the authors of LeBlender have not responded. I'd really like to see one either merged into the LeBlender project or at least added as a separate Nuget package.
Picker data is not "translated" from local to UaaS
When working on a UaaS project locally, and then transferring content to UaaS, any pickers (media, content, member) used in a Leblender Editor, will no longer refer to the previously selected nodes.
http://prntscr.com/chwxis
Further inspecting reveals the pickers are still referring to the same node id's as before, but it looks like node id's are different in local and live environment
http://prntscr.com/chx7n9
This seems to be handled if you use pickers as regular property editors as these now refer to the same node as before even though it does not have the same node id as before.
Probably because it needs a data resolver. There is a pull request for one at https://github.com/Lecoati/LeBlender/pull/30. Also note in one of the comments there is a refactored version attached as a zip. I have not used either.
It's been a while since the PR and the authors of LeBlender have not responded. I'd really like to see one either merged into the LeBlender project or at least added as a separate Nuget package.
Ok thanks, hopefully something will happen soon.
is working on a reply...