In the Classic form, there was a way to copy a dataview and then copy all rules, etc. So , in the form load, we managed to create a duplicate of the JobMtl view and put that in a grid where it wasn’t filtered by assembly. It was extremely useful because people were able to release all materials at the same time instead of going one by one in a big assembly tree to search for the exact line to release
I think that because it’s a tree click that triggers the materials grid filter, there is no event attached that I could technically hack to prevent the filter from happening
However, I’m not sure how I can replicate that in Kinetic. I know that technically, I could do a BAQ but if I do that, all row rules and logic will not be applied. If that’s the only solution, I will but I wonder if someone already went through that process ?
When you say ‘release all materials’, do you mean you were running the Get Request process out of this in Job Entry, or something else I am not familiar with?
I mean putting a ReqDate on all lines, check ‘BuyIt’ on all lines, etc. Filling UD fields too
Updating rows in batch I meant
I found a way. I just created a dataview called JobMtl2 like this:`
Then, I created an event that calls the JobMtlSearchSvc.GetRows (Only by JobNum so no AssemblySeq filter) and return the data in that new view
By doing that, everything works and is linked, except the rules. Which means that I’ll just duplicate the rules that I want to apply on that new view
The normal save from Job Entry works as long as my grid is editable. It works wonderfully and is a way better approach than the old one
2 Likes
Finally, got another problem because of that. If I update a row, it also triggers an update on the JobMtl table which no row is selected (So it takes the first row)
Before update:
After update on 2nd row:
Both rows have changed the partNum which is wrong
If anyone has tips how to fix that, it would be really appreciated
EDIT: Can’t find a solution for that so for now, I created an updateable BAQ and I use that in my JobMtl2 view instead of making reference to JobMtl. It causes too many problems the way that menu is programmed is awful for modifications
