Since using the view name from the Shop Floor Clockings screen resulted in an error, I created the Migration Job using the underlying database table name instead.
The data was successfully inserted using the Excel Add-in. However, no transaction history was created, and the transaction-related fields in Shop Floor Clockings remained blank.
I also tried using the API SHOP_FLOOR_CLOCKINGS_HANDLING_SVC.DO_ADD_LABOR_CLOCKING_DONE, but an error occurred.
My expected result is to create Shop Floor Clockings data through a Migration Job and have the corresponding transaction history generated automatically, in the same way as when records are created from the application.
Is this behavior supported when using a Migration Job, or is another approach required?
Question
I want to use a Migration Job to import the Shop Floor Clockings data.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.