When attempting to drop a job or a group of trusses on Transmit in the output processor, you may encounter an error stating “No job rows exported… Job not sent”, and as a result your transmit will fail. This is an issue related to the packaging of a job in preparation for transmitting. It does however have a relatively simple fix.
What you will need to do is simply make a copy of the job which you are attempting to transmit. At this stage it does not matter what you call the job, but do ensure that all elements are copied and none excluded. So, we select the job in iCommand/Homebase, click “Copy”, and ensure that all items are included in the copy.
If you have chosen a job number for the copy that you are satisfied with, or the job number is of no ultimate importance to you, then you should not need to do anything more. You should now be able to transmit the job via the copied version. If, however, you would like to be able to work with the job with the original job number, then there are just a couple more steps to take.
Return to the original job and delete it. As long as you have copied the job in such a way as all elements are included then you need not worry about losing any data. Once the original job is deleted, return again to the copied version of the job. What we will do now is make another copy of the job from the copied version, which we can now name with the original job number. Once this second copy is made, you may similarly delete the first copied job, and proceed as you normally would with the second copy, now called according to the original job number.
You should no longer receive any error when attempting to transmit your job!
Email Support: firstname.lastname@example.org