Configurator with a sub assembly that is also a configured item

Hey Guys,

I have been playing around with the configurator and I seem to have hit a hurdle when including a configured item within another configured item.

Both of these items have been linked to separate configurators and I have added configured item B into A as a sub assembly (and also ensured that pull as assembly was checked)

I was under the impression that doing this would present the user with configurator B before passing the item configured in B to configurator A, then showing configurator A to the user.

However this is not the case, to be able to configure the configurable sub assembly ‘B’ in ‘A’ the user has to via quote add the Item A and get details, then after configuring A, they need to find B inside A’s sub tree and right click this then get details again and finally go through B’s configurator.

This doesn’t seem like its the way its intended to work?

The other thing I have noticed is that in A’s configurator entry screen under the Sequence tab even after clicking Actions > Rebuild Configurator Sequence the Sequence tab is empty, though I thought this would be where I could select what configurator is shown first to the user?

We are using Epicor Version 10.1.500.13

Does anyone have any experience with doing what I am attempting here, Am I missing something, or could this be a bug?

Many Thanks in advance!
Lee

Hi Lee,

I seem to be experiencing the same issue as you. Subconfigurator works in the quote entry module using the get details function. But nothing appears in the sequence tab like you describe. Were you able to resolve this issue? Thanks.

Kind Regards,
Adriano

(Edit: Resolved the issue by updating from 10.1.400.9 to 10.1.400.29)

Hi Lee,

Are you still having a issue with this?
I found the approved dates need to be a certain way for the sub-assembly to appear in the sequence list. I set mine to all be the same date.
My parent configurator runs, then the sub-configurators run. At the quote you get details on the top level and my configured sub assemblies pull their details through straight away.
The only thing I found is you sometimes need to use the Rule Functions SetCurrentRevision() and RetainExistingMethods() if you want to set the details to a different part revision or keep the existing details from the part attached

Cheers

Hey,

Thanks for this info- I never did get them working correctly but I shall give the approval dates a test and see what happens :slight_smile:

Thanks again
Lee