Was asked to add two more Supplier GroupCode drop-down boxes

Hello,

I have a set of employees that need two extra Group drop-down boxes in the Supplier screen.

They need to store different results but use the same drop-down options as the original Group box.

I am assuming I need to create two new UD Fields in the Vendor Table to store the results.

My question is: how do I go about reusing the same drop-down options as the original?

I almost never use group combo boxes so I was making sure I am not going down a road that is the long way, if you know what I mean.

Any and all help is truly appreciated!

My thoughts are that this should be relatively simple:

I agree.

You should be able to just copy/paste the existing combo box (twice) to give yourself two new combo boxes that are set up the exact same way.

You would then just change the epBindings on those boxes so the values are stored in your two new UD columns.

Unless I’m missing something… it should be that straight forward.

2 Likes

You might want to ask them if they can use supplier attributes. Those are already set up where you can pick as many as you want for each supplier.

The problem with adding two more fields for group is, what happens when you want all the suppliers in group x? Now your query has to look for group x in three separate fields. Painful.

1 Like

Hello,

I thought I had this beat but I am getting the same value showing in all three group boxes.

image

The actual values in the 2 new group epicombo boxes is correct (I have them set to different values and checked with BAQ), it is just showing the original group (Group 1) box value on the Supplier screen.

Any idea on which value to change in customization to get it to reflect the actual saved value for each box?

Do you have a dataview called VendorDetail?

The original combo would’ve been bound to Vendor.GroupCode

So, I would’ve assumed your new boxes would just be bound to:
Vendor.GroupCode2_c
Vendor.GroupCode3_3

(for example)

Just not sure what your VendorDetail binding is.

The VendorDetail view is the Epicor created one.

I am not sure how to reuse the Vendor.GroupCode dropdown list on my new boxes. This approach doesn’t seem to be working for me.

Any ideas?

Pretty sure this is your problem.

image

I built this real quick in Kinetic and I don’t have the UD fields set up so I’m just using TransView…

But it holds the value of GroupCode2 and GroupCode3.

image

But since “GroupCodeGroupDesc” is used in all (3) of my combo boxes, it is being overwritten with the last value selected.

In the test below, i set GroupCode3 and then went back and changed GroupCode2:

image

If I change those to GroupCodeGroupDesc2 & GroupCodeGroupDesc3 (respectively) and retest… I now get this:

image

I see them both.

Now, I’m using TransView so it may be auto-generating those and adding them to TransView. You’ll have to test it and see if it will work in your case or not.

I’m with Alisa, this sounds like a perfect use for Supplier Attributes.

I think that may be the last resort.

If they use the attributes, I would have to recreate the Group list in the attributes maintenance and then if they ever create a new group, I would have to remember to update the attributes to reflect that.

It probably won’t happen that often, just trying to minimize the chance of errors later.

1 Like

What is the difference between adding a group and adding an attribute? Not understanding the concern. The list has to be maintained either way.

I’m saying use attributes instead of groups, not in addition. It would be a one time data migration effort to switch.

If also using Attributes, they would have to add the new group in both places (groupCode and attributes).

Just means you would have to manually keep them in sync.

Like I said, probably wouldn’t happen often.

I’m saying to stop using group completely.

What about reports that use groupCode?

Wouldn’t I have to modify each one to use the attributes instead?

Yep But you would have to do that anyway if you add two more UD fields for additional group codes.

2 Likes

I would only have to do that to the reports they tell me they need the extra groups for.

If I move to attributes only, I would have to modify all reports that pull from GroupCode.

It is down to a matter of practicality at this point, IMO.

Since they tell me they only need the extra groups to show on one report, I feel like attributes only would be more work.

If they needed on all reports, I would definitely look into the attributes only option of course.

I appreciate you helping me flesh out the thought process behind this.