Rijk van Zanten

A dropdown there would also allow for "off" to flat out hide those fields, which could be a nice addition in the future

> that way we can control which collection to show. I don't think we'll need that actually! If you only want to show the junction items, you should just use...

@licitdev this smells very similar to https://github.com/directus/directus/issues/14209, could be related?

That should actually be a fairly easy fix then, as the interfaces should never fetch data for primary keys `+` from the app 🙂

The action hooks run asynchronously and doesn't block the saving process. So when saving a single (non nested relational) item, it's fired after the database operation is done. When you...

> @rijkvanzanten My point is about the hook triggered from the related value. From this hook reading the item from the active transaction is not working. The item doesn't exist...

Are you using the current transaction as per my example above? That should allow you to read the previous item already as top level parents are created before any nested...

> EDIT: also here it doesn't look like it is the transaction we pass Ah! That could very well be the underlying source of the problem here then 🙂 I...

> @rijkvanzanten Any chance passing the transaction for the action hook would be something considered as something like a critical bug and pushed in v9.5.0 milestone :) ? Maybe in...

> it is working for me now with the following code. Basically i removed to reuse the same database transaction. i know i needed this in the past for sqlite...