This issue is resolved in neo4j v4.1 update. But my question is related to neomodel v3.3. How do we resolve this issue in neomodel v3.3.
My