The problem in this case is that the area where the example is taking the values from is dynamically built and if the ordering units are different, then the values we care about are not in the same fields. One example is document 4500000015 where the ordering units are PC and CAR, respectively - so in the header status tab, the column for unit of measure is missing and only the value is present.
We noticed this when building the examples, but decided to ignore this case because most documents in the training system don't have such a scenario and it would have made the script more complicated to handle these documents. However, if you want to do this properly, then the solution is first checking whether the "delivered" and "invoiced" values are on the screen in the usual fields, i.e. do those fields exist on the screen?
Usually, the values would be in fields with ID ending with ...VALUE02 and ...VALUE04. In the other, rarer cases, they are in ...VALUE01 and ...VALUE03. So, you'd check with session.idExists and if ...VALUE02 is not there then take ...VALUE01 and so on.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.