By using this website, you agree to our Terms of Use (click here)
I want to make a GI that lists inventory items and use the attributes of the items for the parameters at the top where the user could select each attribute they want to narrow down the list of items. Similar to a product configurator or a filter list you would see on a website store of items. Does anyone have a working GI like this? IF so anything you recommend or and advice on getting started to achieve this?
An example of what I am trying to achieve here would be the following:
Attribute - Product Type: (Multi-Select Combo) CSAnswer: GAUGE
Attribute - Dial Size: (Multi-Select Combo) CSAnswer: 2.5"
Attribute - Connection Size: (Multi-Select Combo) CSAnswer: 1/4"NPT
So if a user wants to find available stock for the above, they would just select from the parameters of the GI to narrow down the inventory list.
Hi Dan,
So you want to pull out information from the Attribute field? Is this your goal?
Thanks
Daru
Yes, but the attributes are not text but multi select combo boxes. I don't want these in the columns of the GI, just as parameters at the top of the GI for the user to select.
Ok,
So you have attributes with selector combo and want to use that as a filtering parameter in your GI?
The problem with attributes is they have their own table field that the ID isn't so clear.
Usually, for this case, my team and I did a custom field (add new field) with a new table and used it to filter the GI.
But, let me check with another option. \
Regards,
Daru
OK, Thanks Daru. Any input is appreciated.
I think there are two hurdles to this:
1. Getting a Multi Select Combo attribute parameter to filter things correctly.
2. Having multiple parameters that behave like a product configurator selector.
I'm not sure how to get past hurdle #1.
If I have the following Multi Select Combo attribute:
And an Item that is assigned to one of the options:
And a Generic Inquiry where the Multi Select Combo attribute is a Parameter. Everything works fine if I only select one option:
When I select multiple options, my brain thinks that I'm selecting one or the other, but I'm really selecting both so the Item doesn't appear because it's only assigned to one option, not both:
The SQL that gets generated shows that it's not an either or, it's both:
If I assign the Item to both options:
Then the Item will appear when I select both options in the parameter:
But that's probably not the behavior that you want.
For hurdle #2, the problem is that parameters are independent of each other. When I get to parameter #2, it doesn't know what I selected in parameter #1.
Thanks Tim. My findings are taking me to these same results.