cancel
Showing results for 
Search instead for 
Did you mean: 

variant configuration - (auto) force change of values

Former Member
0 Kudos

I'll use a simple car example.

KMAT - CAR

CHAR u2013 SPECS

CHAR - ENGINE

CHAR - HOOD

SPECS

specA

flexA

specB

flexB

none

ENGINE

Option1

Option2

HOOD

Design1

Design2

Currently using screen_dep invisible to hide all characteristics until a spec is chosen. Wanted to hide everything until a spec value was chosen. Works good, acceptance is very positive.

Would like a (better) way where if spec = none and ENGINE = option1 and HOOD = design1 then set spec to A. (no sense in allowing no spec to remain chosen if the selections happens to turn into what is actually specA)

$self.specs = u2018specAu2019

If $root.specs eq u2018noneu2019 and

$root.engine eq u2018option1u2019 and

$root.hood eq u2018design1u2019

Now initially forcing the user to choose a spec before proceeding does not allow the procedure above to push this value. You get a red X, inconsistent values error as expected. Any modeling ideas are welcome as Iu2019d like to see a way to push specA in this scenario while still using screen_dep u2013 invisible, and ultimately avoiding the error.

Another challenge is if user chooses spec = none or specA but also chooses values that are 'flexible' as a specification A...aka SPECS = flexA.

ex. Say engine values option1 and option2 are possible with specA. Config profile procedure sets default engine to option1 when you choose speca. But, if the user changes the default of option1 to option2 ... the spec is now considered a "flexA" and no longer u201CspecAu201D

so on the config profile we would haveu2026

$self.specs = 'flexa'

if $root.specs in('specA','none') and

$root.engine eq 'option2' and

$root.hood eq 'design1'

Is there any way to make a Characteristic automatically select or change values based on several other chosen characteristic values?

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

this works to set value of spec based on more than one characteristic, but still receive an error if a user has chosen a value in SPECS...

must be a way to accomplish this through table inferences?

*if CAR_ENGINE is option1 or option 2

*and CAR_HOOD is design2

*then CAR_SPECS will set to flexB

OBJECTS: (300) CAR

WHERE SPECS = CAR_SPECS;

ENGINE = CAR_ENGINE;

HOOD = CAR_HOOD

CONDITION: ENGINE IN('Option1','Option2')

AND

HOOD IN('Design2')

RESTRICTIONS: SPECS = 'flexB',

SPECS NE 'specA',

SPECS NE 'flexA',

SPECS NE 'specB',

SPECS NE 'none'.