Question:

The example picture shows that some data should populate for BOM 405.Nothing is showing up in my test runs though.  I’ve triple checked all functions in the OnInitialize function and change WIP numbers to ensure everything was being accurately passed from operation to operation.  Is this common?​​​​​​​

Answer:

When you entered the “405” as the order number in the Inputs function of the OnInitialize operation, you pressed Enter twice, which made 2 line breaks part of the input. You can see it in the screenshot below where I highlighted your input, and you can see where the cursor is.This makes Apriso think that the WipOrderNo is “405\\n\\n”, because “\\n” is a line break in html.

Answer:

With this input, the screen will work fine, but the list will show no data because it does not find the order “405\\n\\n”.

And there is no error, because all configuration is right.

To see the wrong WipOrderNo, when you test run your screen, look into the Test Mode Panel on the right (see the screenshot above).

Expand the Debug Tree to see the TRNdtb.HL.Andon operation, and click the DynamicInputs line.This will highlight it in the tree, and when you look to the Properties box below the Debug Tree, you will see the values this input got in the test run.The value for WipOrderNo is “405\\n\\n”.

When you find the issue, check the Debug Tree again, and you should see the WipOrderNo is “405”.