Hi @Sliman_Medini -
Sure thing. We have a few model classes that each have two separate N:M polymorphic associations. Sequelize provides the necessary values for the link table for one of those associations when we save a new instance in FA. However, we need to populate the link table with a second set of values for the second association.
As an example, imagine metadata that can be assigned to either a book or a movie. In addition, that metadata can belong to a user or a group (all these are belongsToMany associations in Sequelize). If we’re creating metadata for a book that, in our use-case, is currently checked out to a user, Sequelize provides FA the values to fill in the Metadata <-> Book relationship, but not the Metadata <-> User relationship.
If we had access to the breadcrumbs, we’d be able to see if the book metadata was being created after drilling down through a user or a group and correctly set up that second association.
Hope this helps!