Product Configurator not Passing Parameter

Has anyone successfully used a BAQ based Dynamic list in the Product Configurator using a Parameter? It seems like to matter what I do, it acts as if I passed an empty parameter.

This happens whether I use another control as the value or try to pass a static value.

Anyone have any experience with this? I’m thinking about instead moving to a UD Method that calls the BAQ and passes back the values, but I’m not sure if that’s doable either.

Here is a BAQ example:


Here is a UD Method example:

Sorry, I was referring to the Kinetic Product Configurator - sorry, I should have been more specific!

1 Like

It’s the same thing, you cannot pass it parameters, instead you use criterias to filter the BAQ.

1 Like

@JacobLeggatt , in Kinetic it’s buried under Properties → Behaviour → Dynamic Lists → BAQ Criteria.

1 Like

I am able to use those filters without issue, but there’s a second section for Parameters.

It does show the relevant parameters in the dropdown under Param Name, so it is looking at the BAQ, but it looks like it isn’t passing anything.

I can’t use the filters for this because I need to do a MATCHES or LIKE setup, which isn’t available in the BAQ criteria.

I recommend using user defined methods over a BAQ just about all the time. A user defined method gives you complete control over the records you pass back. Filtering can be done any way you like across one or many tables using LINQ. You also can further process the data from the query if you needed to reformat it etc.

Also whether this is still the case but in earlier versions of Epicor a BAQ based dynamic list did the filtering on the CLIENT side. Which means you got the full unfiltered dataset passed down to the client and filtering happened on the client side. again may be history and not the case anymore.

2 Likes

I’ve moved to a Linq based UD method now and it looks to be working fine - thank you all for the advice!

The issue with UD method is that you can only get a value back, not a value AND a description. It’s not always an issue, but sometimes just a value isn’t enough…

You can return a value and description using a UD method. Return a string with

Value1`Description1~Value2`Description2

For use with combo boxes dynamic lists you pass back a delimited string as Jeff posted. But if you are using the UD method for general passing back data you are correct technically you can only pass back ONE value. Kinetic doesn’t allow use of the “out” modifier so you are limited to the return value only. Now that value can be a string array (if they have fixed it) or you could pass back a delimited string and break it up as needed. My understanding the architecture limits the ability to only passing back the return value.