Advanced dye reset doesn't work as expected when using job specifications

[iFisser]

This is a problem that comes up only in automation.

In a setup like this, outfits set higher on the list will inherit all advanced dyes from outfits lower on the list where no other advanced dye has been specified for them
I.e. if the base design set for all jobs has a modified material row, dyed to red, and a design (for example) set for only a specific job has no dye specified for that row, the latter one will inherit that modification, regardless of weather "Reset Advanced Dyes" is set in the design details of each design or not. Or more simply put: if my base outfit has red pants, any other job-specific outfit that doesnt have a set dye for pants, will then also have red pants.
I have tested this is various configurations and with multiple designs (some of which i made from scratch to see if i can reproduce the behavior reliably).

[Theo-Asterio]

This isn't a bug, this is not reading what the help told you in the (?) section. Automations are applied from top to bottom, what is happening is expected behavior if you have no advanced dyes in PCT for example but do have advanced dyes in one of the other designs that would be applied meeting the criteria.

Reset Advanced Dyes is resetting it, however you have an automation that applies Advanced Dyes, so it's going to apply it like you told it to.

[iFisser]

I do understand the hierarchy of application.
If the "default" design (set to cover all classes) is listed on top, none of the job specific designs ever get applied (which makes sense).
If i sort it underneath as i did in the picture, it behaves as intended where all specified jobs get their own gear applied and all others are only left with what gets applied last. (as expected)
This however then indeed, as you pointed out as well, still apply the dyes from the default set to any non-modified rows from the job sets because there is no way to indicate to "keep default setting for this row" in the same way that changes get saved as well. i do realize now that in my logic, the way that the application rules are layed out read a bit different from how it is intentioned.
Where as in my head "no dyes" still counted as a "set" part of the design. its clear now to me that that is not the case. Thank you for pointing that out.

Though now i am wondering if maybe this could be set through a checkbox in the design details or something? somethign to the effect of "save empty rows".
So far the only "workaround" that achieves the same result is setting a dye for every single row that deviates just slightly from the default so it still gets saved as a change but keeps at least visually the default. This, however is incredibly tedious to do manually for every gear piece in every design. I know i am not the only one who has run into this same problem. I am aware though that this would then not be the right place to discuss this as it would be more of a full feature.

In any case, thank you for your time! I apologize if some of what I have been tryign to express is a bit unclear as English is not my first language