On the Aura Explore tab, scene actions, the following scene action doesn’t change relationship properties from right clicking on selected arrows. Any idea why this would not be working? Is it an enterprise only feature?
I have write transaction tickbox enabled.
MATCH ()-[r]-()
WHERE id(r) in $relationships
SET r.Name = COALESCE(r.Name, 'delivers')
RETURN r;
Expected behaviour
The arrow Name property for selected arrows should take on the name delivers.
Is it more of a refresh issue or are they not written in the first place?
Thanks Michael
It’s definitely not a refresh issue. It doesn’t get written. The refresh issue does come up for creating relationships through scene actions but which works. Changing relationship properties doesn’t seem to write.
Just for testing can you see if your selected relationships are empty?
Also you might want to add an arrow tip to the pattern so that the rel is not matched twice.
The selected relationships are empty (they have no properties, just the label)
Refreshing doesn't show the 'delivers' and the .Name property is set to show on Relationships (other arrows with Name properties are showing). Thanks.
from the team:
In order for the changes to execute without having to refresh, he needs to return both nodes and relationships.
Like this:
MATCH p= ()-[r]-()
WHERE id(r) in $relationships
SET r.Name = COALESCE(r.Name, 'delivers')
RETURN p
If this still doesn't work, can you please ask the user to check the console log?
Thanks Michael
This didn’t work unfortunately.
Where can I find the logs? I’m on the Aura web based instance version.
Hi rshah! We were referring to browser console, the one you could open with Developer Tools. Are there any errors there?
Seeing the logs would also be interesting (e.g. query log), but I think you are on Aura Free? It seems it's not possible to check that.
Logs are only available for AuraDB Professional instances. Clone to, or create one of these instances to get logs.
Thanks Gregoriy,
Yes I’m on Aura free at the moment. The google chrome browser developer logs shows an error as attached.
Thank you for the info! I've managed to reproduce this behavior. It seems to be specific to Aura Free, since the very same scene actions works if you connect Workspace to a local database (e.q. one from Neo4j Desktop). It will require us some time to investigate what exactly is happening.
Thanks Grigoriy, please do post a quick reply here when it's fixed to give a heads up on this.
The issue should be fixed in Workspace tomorrow (Jul 17).
