There's no way to fix this without breaking the API, so I'm filing this as a documentation issue.
For 2.x, this needs to be changed to using a compound property, so it's $wrapper->remote->foo->value() rather than $wrapper->foo->value(), and so the clash is avoided.
Comments
Comment #1
das-peter commentedI think that would be a smart move.
I started to prefix the the properties in Clients SuiteCrm.
Comment #3
joachim commentedFixed in 2.x, since it breaks the API.
Comment #4
joachim commented