Looks like someone dropped the ball and i have no idea who to point the finger at.
Looking at the object handles available in Work Ticket Entry, the header object has 3 object handle properties that stand out, while on the "Steps" tab, "Lines" and "Steps" have the same handle whereas while on the "Materials" tab, "Lines" and "Parts" have the same handle.
This was taken while on the Steps tab.
I would expect the VI import to function similar to a framework level Bill of Materials import, where importing into BM_BillHeader allows you to also import into BM_BillDetail, BM_BillOptionCategory, BM_BillOptionHeader, and BM_BillOptionDetail where each table has a different record type prefix.
In theory, it is probably possible to hack together some perform logic to handle the Steps through the coBusiness'Steps handle using either the IMP$[x] variables or temp fields to read the values.
Either Scanco or Sage need to step up and specify whether or not we can expect to be able to import work tickets through stock VI.
------------------------------
David Speck II
Tennessee Software Solutions
------------------------------