I’m working on a custom layer for Issue Material that will allow the user to issue material to multiple jobs at once. To do this, I’m creating a grid and having the user enter the number of jobs they want to issue material for into a number box, at which point an iterative event will add rows to the grid until the number or rows in the grid is equal to the number of jobs entered by the user. The user will then paste data into the grid and a function takes it from there to issue material.
This process works fine, however if I enter a number greater than 25 (or somewhere around this number) into the “Number of Jobs” field, the event seems to get hung up, almost as if it’s in an infinite loop. I’m wondering if this has to do with a setting in the grid properties somewhere, but thus far I haven’t found any. I know that when a BAQ executes with thousands of rows of data, there is dynamic loading for the grid and the number of rows initially returned is limited, could this be related somehow? Any ideas?
We are running the current version of Kinetic in the browser. My event is as follows:
• Condition below is (my custom dataview.count < NumofJobs entered by user)
• When this evaluates to true, it calls the AddRowsToGrid event which successfully adds a row to the dataview grid, then reverts back to the original event to continue conditional evaluation.
o Once the condition evaluates to False, it sets the focus to the first row in the grid
• The last screen below is what I get after a few minutes if I allow the event to continue running
