Displaying Calculated Field Data on Engineering Workbench

Kinetic ERP
, , ,
1

When we went from classic screens to kinetic web browser screens earlier in the year, we used that an a opportunity to validate any form customs. Meaning if no one asked, we didn’t recreate it. We have one on the classic screen of engineering workbench and method tracker, that takes the qty/parent and calculates the inverse. It makes more sense to see 16 pieces per material part than 0.0625 qty/parent. In attempting to recreate this form custom a few different ways, came across an event widget “calculation”.

image

Using a field to hold the information

image

However, there does not seem to be any documentation around how to format the event widget. Has anyone used this widget? Other suggestions on how to accomplish the overall request?

2

I think the “Initial Value” will be the QtyPer field… then in operations, you select your operator +,-,*,/ etc. depending on what you’re doing and your operand would be the field you’re doing that operation with.

So… EpBinding: ECOMtl.PiecesPerUOM_c
Initial Value: The Field you’re dividing
Operator: /
Operand: The Field you’re dividing by.

3

If I were going to create a dashboard with this information then I would use this as the calculation:

case ( ECOMtl.QtyPer > 0 then 1/ECOMtl.QtyPer else 0 )

I have the event triggering after update of the QtyPer field. The calcuation is still the 1/QtyPer to get the inverse.

4

I would assume then, your settings would be:

EpBinding: ECOMtl.PiecesPerUOM_c
Initial Value: 1
Operator: /
Operand: ECOMtl.QtyPer

I’m not sure of the format for the column reference. Whether you need {} or not, etc.

That being said, you may also be able to do this (and possibly a better way) via Row Update.

Trigger would be the same.
Add a condition widget to handle your “case” statement… ECOMtl.QtyPer > 0

… IF TRUE - row update.
You just add your column in parameters (ECOMtl.PiecesPerUOM_c) and then the rest of the expression you previously posted.

… IF FALSE - row update setting your column = 0

5

This way ended up being easier to do. The calculate widget did not seem to be very clear or to trigger. Where as, using a row update in this format, allowed for the field to update as expected based on the event trigger.

image

1 Like