Running the Document Output Setup migration manually

As of version 28.0, Continia eDocuments are sent through Continia Document Output instead of Continia Document Capture. When a Document Output migration starts, for example when you run the Document Output Setup assisted setup guide, the system creates a job queue entry that runs codeunit 6175405 CDO Setup Migration Mgt. If a delegated administrator starts the migration, the job queue entry can't run, and the migration must therefore be run manually.

This article explains when that happens, what the migration does, and how to run it. The article also explains what to do if you encounter an error that's displayed when an earlier migration hasn't finished.

When you need to run the migration manually

You must run the migration manually when:

• A delegated administrator has started the Document Output migration. This is typically the case when a partner consultant sets up Document Output for a customer.
• Background tasks aren't available.
• The entry failed after three attempts and has the status Error.

Starting the migration creates a job queue entry that runs codeunit 6175405. Business Central only lets licensed users of the company start job queue entries, so an entry created by a delegated administrator stays on hold. In such cases, the assisted setup guide shows the following warning:

• The Document Output setup migration has not started: its job queue entry is on hold, and a delegated administrator cannot start it. Document sending is paused until a licensed user of the company starts the entry from the Job Queue Entries page.

What the migration does

Codeunit 6175405 CDO Setup Migration Mgt. performs the following tasks:

• Fills in the default EMAIL output profile on posted documents that have a blank send code, across 11 posted document tables.

• Updates posted documents and marks some of them (posted sales shipments, invoices, and credit memos dated before the cutoff) as Handled.

  Note

  When the migration starts from the eDocuments setup guide, no documents are marked as Handled, because that guide passes no date.

• Updates the Send code for relevant customers when eDocument sending is migrated from Document Capture to Document Output. It also creates default sender profiles and sets the send code on documents for the customers it changed.

  Note

  The send-code step only runs if the company has an eDocuments license.

• Updates the Document Output Setup, so you can follow the status of the migration.

To run the migration

You run the migration from the Job Queue Entries page. Delegated administrators can run it in the foreground, in their own session. Licensed users of the company can also let the job queue run it in the background.

To run the migration, follow these steps:

1. Search () for and select Job Queue Entries.

2. In the list of entries, select the entry where Object Type to Run is Codeunit and Object ID to Run is 6175405 (CDO Setup Migration Mgt.).

   Note

   Look for an entry that matches these criteria and has the description Document Output setup migration, to be sure to select the right one. Alternatively, go to the notification at the top of the Document Output Setup page and click Open Job Queue Entries, which will take you straight to the right entry.

3. Do one of the following:

   • To run the migration in your own session: In the action bar, click Run once (foreground). You can do this as a delegated administrator. Keep Business Central open until the migration has finished, which can take some time in companies with many posted documents.
   • To let the job queue run the migration in the background: In the action bar, click Set Status to Ready. Only a licensed user of the company with the SUPER permission set can do this.

You've now run the migration job queue manually.

Troubleshooting

You may encounter the following error:

• A Document Output setup migration is already running. Wait for it to finish before starting another.

This error is displayed when an earlier migration hasn't finished. Often, its job queue entry is on hold because a delegated administrator started the setup.

To solve the issue, do one of the following:

• Run the pending migration: Follow the steps in To run the migration above, and then complete the Document Output Setup.
• Clear the migration: On the Document Output Setup page, in the notification at the top about the migration, click Clear migration.

If you choose to clear the migration, migration is abandoned and the job queue entry is deleted. Clearing the migration also leaves old posted documents not marked as Handled, so they can be sent again.

Related information

Sending eDocuments after upgrading to version 28.0
Delegated administrator access to Business Central Online (Microsoft article)