JET UI vs Legacy UI Recommendation Rules acting different?
We are currently seeing an issue where we have two recommendation rules trying to set one attribute. One rule is a force set and the other is a soft set. According to my knowledge, the forced set should overrule the soft set (which is what we want). This seems to work fine in out legacy UI, but with JET UI, the first update shows correctly, but then if Update is hit again it will kick out the force set and go to the soft set selection. Does anyone know why this might be or of a