Linked (many) entity (from auto/rule) not visible from one 2 many, but visible when many 2 many?

Linked entity (from auto/rule) not visible from one 2 many, but visible when many 2 many?

I am currently implementing card + subcard functionality within fibery’s board view. It works out surprisingly well leveraging parent-card-pid and sub-card-pid +1 (all the same) and based on the parent card’s original pid. while only losing parent-card sorting/priority functionalities etc. as well as being bound to sort card+subcard combos all the way at top or bottom due to requirement for global sort.

  • haven’t thought much if truly the case as I usually am more of “tester/doer” when implementing things over 110% thought and eval. despite much eval:

but if conditional sorting was ever supported akin to conditional coloring the sort could probably be limited for such workaround and sort-based usecase/potential. (while possibly not impeding due to global/top-level sort criteria)

I’m somewhat confused as to why I’m not able to select or “see” the native/default and generated “card” (many) when it comes to rule/automation on linked-entity trigger, from “subcard” (one) perspective. however it perfectly shows up from the “card” (many) perspective. and also while simply using the exactly same native fibery fields and use-case within a many2many setup.

is this a bug? it seems inconsistent at least from someone not normally into DB’s relationships etc. or is it related to missing wip/roadmap polymorphy support or some other technical limiation?

I don’t use any sort of autolinking. the fields i.e. relationships are not setup as “mandatory”.

after switching initially and sensibly unrelated the rules contain “deleted” relation/entity field which makes sense. (as the relationship/field was changed/deleted) but it seems impossible due to one to many context problem.

  • sidenote: is there a roadmap for “ToNumber” Formula function? Thankfully Matt Blaise’s et al’s regex workaround helps but I’m sure many newcomers run into that common requirement.