Hello. I want to have the ability to print labels from all the steps in the flow using the Printing Icon in the ribbon menu on top of Material page. I see that I have to set up Smart table “Material PrintableDocumentContext” table for all the steps. I have hundreds/ thousands of steps and not sure if this is the best way to set it up. There are too many steps. I tried using “AreaPrintableDocumentContext” but gives me an error " Value ‘Label’ is invalid for Property Scope. It must be LotTraveler"
I understand that I can use the entity “Printable Document” to print the label at any steps but don’t want to use it if I don’t need to. Is there an easier way to set this up to print labels from Material page using the Printing Icon?
With the standard setup, the print icon on the Material page needs one MaterialPrintableDocumentContext row per Step, and AreaPrintableDocumentContext can’t be used for labels.
So, options:
Recommended: generate the rows and bulk-load them. If the flow structure is not complex, get the Step list from the flow (a query or export), create one Step → PrintableDocument row per Step, and load them through Master Data. Rows are cheap because there are no other keys. If some Product Groups need a different label, add Step + ProductGroup rows only for those.
Customization: change how the list of printable documents is resolved for a Material so it falls back to the full list of labels when no row matches. Please remark that since this is a customization, you’ll carry through every upgrade.
Assumptions to challenge
Do operators really need to print a label at every Step? In practice labels are usually needed only at a handful of Steps (receiving, splits, packing, shipping). If that’s true here, you’d need far fewer rows, and restricting printing to those Steps would also prevent labels being reprinted at the wrong places. Also, consider usability because having all the labels available all the time also means that the operator needs to select the right one among a huge list, which is very error prone.
Blind spot
With the bulk-load approach, every new Step or flow revision needs a new row. If you use this approach, build the row generation into your master data or flow change process so this doesn’t fail silently.
