AdemeroHelp

Lookup doesn't fill fields after entering a packet number

Troubleshoot a packet lookup that fills nothing, especially after adding a catalog or document type. Check the template, shared key field, primary document, matching field names, and user permissions, then test one known packet.

Catalog administratorsContent Central 7.815–20 minutesVerified 2026-10-28

Before you begin

  • Administrator access to Packet Templates and the affected document type's fields and permissions
  • The affected catalog and document type, plus one packet number with an existing primary document

Find what is preventing a packet lookup from copying common field values, correct the affected setup, and test it with one known packet.

Use this guide when you enter a packet number during capture or field editing and Lookup leaves the other fields unchanged. It is especially useful when an existing document type works but a new catalog or document type does not. The steps use the Content Central 7.8 interface.

First check where the values come from

A packet lookup copies values from a document already filed in Content Central. The packet template identifies that source as its Primary Document Type, and a shared Key Field connects the documents. Creating a catalog or workflow does not add its new document types to a packet template automatically.

If the values come from an accounting database, spreadsheet, or another external database, use Look up field values from another system. That guide covers the connection, lookup conditions, and fields to populate. A lookup marked Make available for workflow actions only is excluded from manual Lookup operations.

For the checks below, choose one packet number whose primary document already contains the values you expect. Work through the sections in order and repeat the final test after correcting a setting. Stop when the expected values fill.

1. Include the new document type and enable its lookup

This check addresses a new type that has not been added to the packet template, a disabled template, or an unchecked Lookup box.

  1. Open Administration > Packet Templates.

  2. Find the template used by the working documents and click its Edit Template pencil.

  3. Check Enabled if this is the template that should be in use.

  4. Look for the new catalog and document type under Document Types in Packet.

  5. If it is missing, click Add Document Type.

  6. Select the missing type in Available Document Types.

  7. Click Apply in that dialog.

  8. Check Lookup in that document type's row.

  9. Click Apply on the template page to save the settings.

What you should see: the template includes the destination document type, its Lookup box is checked, and the template is enabled. Req'd controls packet completeness; it does not turn lookup on.

If the new document type is absent from Available Document Types, continue with the shared-key check below. Only document types using the template's global key field can be added.

2. Use the same global field for the packet number

Matching labels are not enough. A locally created field called Packet Number is different from a field linked to the global Packet Number selected by the template.

  1. In the packet template, note the selected Key Field.

  2. Open Administration > Catalogs & Document Types.

  3. Select the new catalog and document type, then open Fields.

  4. Click the pencil for its packet-number field.

  5. Check whether Use Global Field is switched on and Global Field selects the same field you noted in the template.

What you should see: the document type uses that existing global field. Its inherited field properties are locked in the editor; a matching Name or Display Name by itself does not prove the link.

For an existing field that has not been used, switch on Use Global Field, select the existing key field, and click Save. When adding a field for the first time, the button is Create. Return to the packet template and add the document type if it was previously unavailable.

If documents already contain values in this field, have your administrator review the change before saving. Do not delete and recreate a populated field to repair its global link. Editing the global definition also affects other document types that use it.

3. Check the primary document and its packet number

Lookup needs a saved source document. It cannot copy values from a document that has not been captured yet, and it does not use the destination type as its own packet-lookup source.

  1. Open the packet template and note Primary Document Type.

  2. Confirm that it identifies the type that supplies the common field values. It must be different from the document type you are trying to populate.

  3. Use document search to find an existing document of that primary type with the packet number you are testing.

  4. Open the source document's properties and check its packet-number value. Use that stored value for the test, including any leading zeros.

  5. Check that the source document contains nonempty values in the fields you expect to copy.

What you should see: an existing document of the designated primary type, with the matching packet number and the required values already filled in. A document of another type in the same packet is not the primary source.

If the source has not been filed, complete its normal capture first. If its values are incorrect or empty, correct that source through your usual field-editing process before repeating Lookup.

If a new, unused template has the wrong primary type, select the intended Primary Document Type and click Apply. For an established template, review the effect on existing packets and approvals before changing it. If the selection is locked because packets are in an approval process, ask your administrator or Support to review it.

4. Match the names of the fields being filled

For packet lookups, the key is connected through a global field, while the other values are copied to fields with matching Name values. Display Name is the label shown to users and can hide a difference.

  1. Open Administration > Catalogs & Document Types and select the primary document's catalog and document type.

  2. Open Fields, then the pencil for a field whose value should copy, and note its Name.

  3. Open the corresponding field in the destination document type.

  4. Compare Name in the two editors, rather than comparing only Display Name on the capture screen.

What you should see: the source and destination have matching field names. For example, a source field named Customer Name will not automatically fill a destination named Client Name, even if both display the label Customer.

For a new, unused local field, correct Name to match the source and click Save. If the name is inherited from a global field, or the field is already used by documents, workflows, or integrations, have your administrator review those dependencies before renaming it. Do not rename the shared global field just to fix one document type.

5. Check the affected user's field-edit permission

Permissions on the working document type do not automatically grant the same rights on the new one. Packet lookup checks field-edit permission for the destination type.

  1. Open Administration > Catalogs & Document Types and select the destination catalog and document type.

  2. Open Membership & Permissions.

  3. Check Group Permissions for the affected user's group, then User Permissions for any direct grant.

  4. If the user should be allowed to edit these fields, open the appropriate row's pencil and enable Allow Field Editing.

  5. Click Save in the permission dialog.

What you should see: the affected user has field-edit permission through an appropriate group or direct grant. Allow Document Editing is a separate permission for document content. Grant only the access the user is meant to have.

See Document type permissions, explained for how group, user, and creator grants combine.

6. Test one known packet

Use the affected user's account and the same source document checked in section 3.

  1. Open Capture New > Electronic.

  2. Set Index Fields to Provide now.

  3. Select the destination catalog and document type.

  4. Enter the source document's packet-number value in the key field.

  5. Click Lookup after the fields finish loading.

What you should see: matching common fields receive the nonempty source values. You do not need to complete a capture to inspect those returned values.

If only some fields fill, revisit their source values and Name settings. If everything was already filled with the same values, an unchanged screen does not mean the lookup failed. If the button is unavailable or no lookup is configured, revisit the template, shared key, and permissions.

If Lookup still fills nothing

Contact Ademero Support with the customer or organization name, destination catalog and document type, and one packet number that should work. Include any message shown when you click Lookup.

Mention if the same document type belongs to several packet templates, or if more than one primary document has the same packet number. Lookup can select a different source than you intended in those cases; changing templates or removing documents without checking the relationships can make the result more confusing.