Updating Multiple Rows in Grid with dropdowns - Mass Issue to Mfg

Hello,

So I am stuck about 1/2 way on attempt to default the From Warehouse and From Bin columns in the Material Issues Grid to our “WIP”. (Mass Issue to Msg > Enter Job# > Click Issue Assembly button).

I tried a BPM on BuildMassIssueBrowse, which I found was what setup the grid data. However, only the post process has the actual collection and modifying in post doesn’t update the UI.

So I turned to using events, and found the below post on how to use an iteration to loop through all the rows of the grid:

What was odd though, is it looked like the code would skip the first row of grid, so I added a row-update after the dataview-condition as I knew that would update the first record.

And while the From Bin is updating (screenshots below to example things), the dropdown is not. I am not sure if that’s because of the nature of how events work and changing the underlying binding value won’t update the dropdown in a grid?

I am stuck, so I hope someone can shed some light on this. As I mentioned, below are screens to example the workflow items and also show what the grid columns looked like before and what they look like now. Thank you for your help and time!

Before grid column update:
image

After grid column update:
image

Our first event:

The expression was something I came up with to ensure I capture all rows. For my test case, all rows had an Assembly Seq of 0.

The second event that is for the iterative event, OSS_DefWhseBinToWIP, updates the two columns:

So I’m thinking this approach won’t work… something with the combo. I added a message handler to show me the value beforehand to make sure I am setting it correctly and I am so…

My only other question to everyone, is it possible to use a data rule to default an entire column to another value?

Hi Rob,

First thing I’d look at is the Dataviews with the trace function, if you’re able. The events update the UI, but not necessarily what is on the database, which is where, maybe, the dropdown is defaulting from. One thing I was thinking is you could maybe have an event that saves after the iterations so it saves them all as WIP to the database. I’d also make sure the dropdown has a WIP option (not familiar with where you’re at) and if it doesn’t, making it show as WIP doesn’t mean anything. If it’s a dropdown, usually it has a code and it displays the description instead, so manually hard coding it into WIP looks good on paper, but you’ll run into errors when you try to save from my experience.