# Configurator - Changes to one combo box changes another?

**URL:** <https://www.epiusers.help/t/configurator-changes-to-one-combo-box-changes-another/71072>\
**Category:** Epicor ERP 10\
**Tags:** e10\
**Created:** [September 18, 2020, 6:41pm UTC](https://www.epiusers.help/t/configurator-changes-to-one-combo-box-changes-another/71072 "2020-09-18T18:41:10Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![jwfoster](https://www.epiusers.help/letter_avatar_proxy/v4/letter/j/e5b9ba/32.png) [@jwfoster](https://www.epiusers.help/u/jwfoster)\
**Post date:** [September 21, 2020, 8:07pm UTC](https://www.epiusers.help/t/configurator-changes-to-one-combo-box-changes-another/71072/21 "2020-09-21T20:07:10Z")

</div>

That makes sense.

I have abstracted away the fields in the page from the rules by using a single field that is populated with a comma delimited list of all the values selected and entered. This means I don’t need to reference fields in my rules, with the exception of the one CSV field.

By doing this, I am free to make whatever changes I want to the UI without having to find references to fields throughout the rules associated with my SuperMOM. I can easy create new Configurators as well. Seeing how this is the first implementation of Epicor for this company, I anticipate there being quite a few changes as we approach role out.

[Previous page](https://www.epiusers.help/t/configurator-changes-to-one-combo-box-changes-another/71072.md?page=1)
