Currently the expression and table constrain are standalone and do not depend on each other. This leads to constrain conflicts and model contradiction errors.

My idea is for the constrains to be made dynamic and dependant on each other, thus providing the ability to create better and intelligent product configurator models and reduce instances of the constrains fighting with each other and pushing the model in contradiction.

Below is an example of how I envisage this to work.

Table constrain 1 – User defined table
Field 1/Field 2/Field 3 where Field 3 is populated after Fields 1 and 2 are selected.

Table constrain 2 – System defined table
Field 3/Field 4 where Field 4 is populated with the value from the field mapped by the system tables against value in Field 3.

Solution – Provide the ability to make table constrain 2 to be dependent on table constrain 1. This provides the ability for Field 3 to be constrained by two interdependent constrains. This could be done by using constrain numbers (like operation numbers in the route).


Needs Votes
Ideas Administrator

Thanks for your input! If it gets voted, we will consider adding it to our long term roadmap. 


Beatriz Nebot Gracia

Program Manager, Microsoft