Ideas for Document Central as submitted to our Feature Upvote board. Ideas are ordered by 'new' and the 50 top matches are included. pr_zsni3yh5ixockup 2025-04-04T05:49:51Z sug_tp5ibrm3qbzdrcx 2026-01-13T09:30:31Z 2026-02-19T09:35:43Z Description: Currently, files and images uploaded to Document Central can be very large. When these documents are later sent via email, the size often causes issues such as exceeding attachment limits or slowing down the sending process. Feature Request: Introduce an option to automatically compress files and images during upload to Document Central. -Compression should reduce file size without significantly impacting quality. -Ideally, provide configurable compression levels (e.g., Standard, High, No Compression). -Goal: Ensure documents can be easily attached and sent via email without errors. Business Value: -Prevent email failures due to oversized attachments -Improve sending speed and user experience -Reduce storage consumption in Document Central sug_mcxqtwr2a03z66c 2025-12-18T13:39:29Z 2026-02-19T09:34:53Z Background When moving documents to another contact or entity, the original creation date is overwritten because the system interprets the move as a new upload. Issue Overwriting the original creation date compromises historical accuracy and may lead to compliance issues. Proposed Change Retain the original creation date when moving documents. Update only the “modified” date to reflect the move. sug_tbojpgxookhzlxl 2025-11-03T15:06:10Z 2026-02-19T09:32:34Z Problem - A new feature was recently delivered that enables indexing of metadata at the document entry level. - This enhancement allows for more efficient searching across documents within Document Central. - It also enables filtering based on metadata in the Page-view of Document Central. - However, when filtering in the Page-view, users can only filter by index field name & number rather than the actual names of the indexed metadata fields. - This limitation makes it difficult for end users to apply filters accurately, as they must know the corresponding index field number for each metadata field. Desired Solution - Enable filtering in the Page-view of Document Central using the names of the indexed metadata fields instead of the index field name & number. - Ensure that the filter interface clearly displays the metadata field names to improve usability and reduce confusion, enhancing the user experience by making metadata-based filtering more intuitive and accessible. sug_fuqs2tlzonjsjdz 2025-11-03T14:58:45Z 2026-02-19T09:31:08Z Problem - It is currently not possible to update metadata in bulk for a set of similar documents via Document Central. - This limitation becomes problematic when policies change or when historical metadata needs to be corrected. - Bulk corrections currently appear to be only feasible through direct manipulation of the repository using scripts or tooling. - This approach requires a high level of technical expertise and coordination, often resulting in significant time and cost implications. Desired Solution - Enable the ability to select groups of similar documents based on shared metadata characteristics using filters. - Allow users to apply metadata changes or additions to the entire selected set in one action. - Provide this functionality within the Document Central interface to reduce dependency on technical interventions and lower the cost of metadata management. sug_tgnnuce3amoonwo 2025-11-01T11:49:10Z 2026-02-19T09:28:55Z The "DocumentCentral - Document Search" screen recently added an additional filter option: "Metadata Specification." This allows you to filter by a single metadata item. The ability to enter multiple metadata specifications would be a significant advantage in more targeted document searches. For example, it's currently not possible to filter by both Document Type and Unit Number(s). If this combination were possible, we could easily retrieve all floor plans for a series of units. sug_vosfm2i1dgwnvlk 2025-11-27T07:18:46Z 2026-02-19T09:27:58Z Beim Zuordnen eines Dokuments zu einem Prozess in Document Central soll die Kamera des Tablets direkt als Upload-Option verfügbar sein. Aktuell muss ein Foto zunächst separat aufgenommen, gespeichert und anschließend manuell hochgeladen werden. Die gewünschte Lösung: Direktes Fotografieren und Anhängen innerhalb von Document Central – ohne Zwischenschritte wie Explorer-Suche oder Drag & Drop. Dies würde die Arbeit auf mobilen Endgeräten deutlich vereinfachen und beschleunigen, insbesondere für interne Prozesse. sug_sx858srrhlk0qwe 2026-01-16T13:37:57Z 2026-02-19T09:22:46Z Problem Administrators can configure default or fixed (mandatory) metadata values for documents uploaded via the UI. For documents uploaded via silent drops, only fixed values are supported; default values cannot be configured. This results in inconsistent behavior between UI uploads and silent drops and limits flexibility for automated ingestion. Metadata enrichment for silent drops is therefore either too rigid (fixed values only) or depends on external solutions to ensure required metadata is set. Desired Solution Extend silent-drop metadata configuration to support default values alongside fixed values: - Scenario 1 – Default value, not fixed • No value provided → apply default • Value provided → retain provided value - Scenario 2 – Default value, fixed • No value provided → apply default (fixed) • Value provided → override with default (fixed) sug_unviqrf7szjuham 2025-09-25T08:55:33Z 2025-09-30T06:43:01Z Could we retrieve the list of attached document types and have an alert or a block if certain types are missing? sug_pv4vqews7nzf3px 2025-09-01T14:58:43Z 2025-09-02T06:49:21Z When an incoming document is saved to the DMS, the title is the same as the file name. This file name is sometimes meaningless, making the title meaningless as well. Within our organization, we've emphasized that the title should always be checked for accuracy and clarity, as this title is also the first thing displayed as a document identifier in the customer portal when the document is allowed to be displayed externally. Yet, people often forget to adjust the title. Is it therefore possible to make the title field mandatory, forcing users to think carefully about the title and increasing the likelihood of a correct title? sug_1knsyde1wmhdfkd 2025-08-27T18:41:53Z 2025-09-30T06:47:36Z Currently, when a document is deleted via Document Central (with SharePoint as the storage location), it is permanently removed from SharePoint right away. It does not go to the SharePoint Recycle Bin first. As a result, restoring documents after an accidental deletion is difficult or even impossible. Request: Please add an (optional) setting that ensures deleted documents are always moved to the SharePoint Recycle Bin, instead of being permanently deleted. Benefits: Improved safety: reduces the risk of permanent loss of important documents. User-friendly: aligns with the standard SharePoint behavior that users expect. Less dependency on backups or technical interventions. sug_zxmlrmydjeppxhm 2025-07-28T12:26:43Z 2025-07-31T08:56:40Z We would like to add an additional search filter to "Document Central - document search." The current search options/filters are too limited, resulting in too many documents being returned. We would like to be able to filter by Record Number or linked Cluster or Unit Number. For example, if we want to export the floor plans of specific clusters, this is not possible without using this filter: see the attachment. Then we would receive too many documents. sug_24ungk9ca2jid46 2025-07-24T11:36:21Z 2025-08-05T11:55:03Z Improve the CRM integration in Document Central by showing more relevant metadata (e.g., document type, number, uploader) directly in CRM activities and enabling one-click document previews from the contact card or activity log. By leveraging standard Business Central extensibility (FactBoxes, PageExtensions, preview actions), users gain a faster, more contextual workflow with fewer clicks and better traceability – especially helpful when handling documents in quotes, orders, or communication logs. Why upvote? ✅ Clear, human-readable activity texts ✅ Preview directly in CRM of Document Central Documents ✅ Immediate access to document details from CRM contact ✅ Consistent metadata across modules ✅ Translations and field labels cleaned up ✅ Optional extensibility for partners via events Let’s make the CRM experience in Document Central just as smooth as the rest of BC. sug_y1o8t9wrd4yhjhp 2025-06-11T07:06:15Z 2025-06-16T11:34:35Z In the current implementation of the Document Management System (DMS), users are unable to manage the order of fields within metadata forms. This can hinder the document archiving process, especially when required fields are scattered throughout the form. There is no functionality to define or modify the order of metadata fields in the form. This limits usability, as required fields may appear further down the form. Example Use Case: Place mandatory fields at the top of the metadata form so that users can quickly complete the essential information and archive documents more efficiently. sug_n5qt2vdwlhhachb 2025-05-15T13:40:04Z 2025-09-30T06:51:50Z When a series of documents need to be moved to another Operations card (within the same library), the index data of these documents need to be re-entered per document. For example, when moving many documents from one tenant card to another tenant card, it is a lot of work to re-enter the existing index data. The wish is to be offered the choice when moving many documents whether or not the existing index data should be included in the move. sug_sfhuhbxkzcamiux 2025-05-09T09:53:45Z 2025-06-16T11:46:23Z Problem: - Currently, the publication of the Document Central configuration to SharePoint can only be triggered manually. - It is advisable to perform this action outside of office hours to prevent any performance hindrance for Document Central users. - Since the publication cannot be scheduled, it requires Document Central administrators to consciously initiate the publication outside of office hours. Desired Change: - Implement a scheduling feature that allows the publication of the Document Central configuration to SharePoint to be automated. - This could be achieved through a job queue or a similar mechanism, enabling the publication to be scheduled at a convenient time, such as outside of office hours. sug_qbg6gqp1xznjmbx 2025-05-05T16:40:55Z 2025-06-16T11:49:36Z Passend zu dem neuen Feature "Enhancement of the barcode creation functionality", wäre es vom Vorteil, wenn man die Anordnung oder die Schriftgröße der zusätzlichen Information wie Inhaltstyp und Belegnummer auf dem Barcode-Etikett anpassen könnte. sug_fqfvmaehgnepy8a 2025-05-04T07:33:08Z 2025-09-30T06:56:19Z In the situation where the page view needs to be displayed instead of the data grid view, it is desirable to show the columns "document type" and "description" so that they can be searched for. Without these 2 columns, finding the right document is very difficult for BC cards with many documents sug_zyh0wrkqkuteffd 2025-04-14T18:04:06Z 2025-09-30T06:56:56Z Now, when moving multiple documents at once, the metadata must be filled in again for each document. It is more convenient to use the existing source metadata for the target metadata. Or that there is a choice when moving documents: transfer metadata to the target, or fill it in again. For example, if hundreds of documents have to be moved at once, it is impossible to re-enter the metadata for each document. sug_mdjdfhmuioc0rso 2025-04-04T07:29:36Z 2025-04-23T07:44:58Z **Beschreibung:** Es soll ermöglicht werden, in der Berichtsauswahl den Inhaltstyp aus Document Central flexibel zu definieren. Durch diese Neuerung wäre es möglich, verschiedene Layouts für ein und denselben Bericht zu unterscheiden. **Details:** - Die restlichen Einstellungen, wie beispielsweise der doppelte Druck ("Immer" etc.), sollen weiterhin wie gewohnt aus den Berichtseinstellungen von Document Central übernommen werden. - Die Flexibilität wird erhöht, wodurch statische Einschränkungen in Bezug auf Layouts entfallen. - Unterschiedliche Layout-Vorlagen können basierend auf einheitlichen Berichtsinhalten genutzt werden. **Vorteile:** - Mehr Anpassungsmöglichkeiten für Unternehmensberichte. - Erhöhte Flexibilität, da Berichte nicht mehr an ein starres Layout gebunden sind. - Effiziente Nutzung der bestehenden Berichtsinformationen in Kombination mit variablen Layouts. sug_jlqxenn5zolfms9 2025-03-21T12:55:16Z 2025-03-31T08:49:47Z Problem: - When copying a Business Central production environment to a new sandbox environment, all Simova table data is included, including document entries and their metadata. - These document entries are bound to the repository configured in the production environment, making them inapplicable in the new sandbox environment which has its own repository. - This results in errors when accessing the document entries through the datagrid. - Deleting these document entries is time-consuming, especially in customer environments with a large number of document entries (current examples range from 500,000 to 2,000,000, taking a day or more to delete). Desired Solution: - Exclude document entries and all related data when copying a Business Central production environment to a new sandbox environment. sug_es7ifumrtrtgvo9 2025-03-13T15:27:23Z 2025-09-30T06:57:39Z Problem: - When the number of documents in Document Central exceeds the threshold set in the Module Setup, the Page-view of Document Central opens instead of the Datagrid. - The Page-view is chosen for better performance when opening, but it only presents data from the document entries and lacks metadata bound to each document entry. - This limitation restricts the overview of document-specific data, making it difficult to find the right document in a large set. - Filters can be used to narrow down the set of documents, but filtering on all metadata-values is performance-intensive and the presentation of results still lacks an overview of relevant metadata Desired Solution: - Display a small, configurable number of metadata per document entry while using the Page-view. - Alternatively, allow the use of the Datagrid even with large quantities of documents bound to a specific Business Central record (approximately up to 100K) without mayor losses in performance. sug_ajh4jbvnoqpjf2i 2025-03-12T11:45:47Z 2025-03-31T10:58:24Z The number of content types to choose from on the Zig Operations card is now limited to 10. We would like to see all content types available on the card. This means that it is not necessary to first click on "all files" to be able to create a filter on content type in the data grid. But the filter can already be created on the Operations card itself by first being able to make a choice on content type sug_2k3fgq7iipu7mza 2025-02-24T12:21:42Z 2025-08-05T12:48:51Z We would like to display files with a .heic extension in the viewer (if possible). This is an apple native file extension, so maybe that would be a challenge... sug_lg8whalxdzfmxtq 2025-02-14T08:50:55Z 2025-02-19T13:40:12Z Problem: - Currently, you can view attachments in archived emails, but to process an attachment, you must archive it as a new document with the same metadata and a specific content type. This means you can't directly pick up and process the attachment. Desired Change: - Add a download button to the Email Attachments overview, allowing direct download of attachments. This will eliminate the need to index email attachments separately, avoiding redundant document entries. sug_8243ycqmxpajdeq 2025-02-12T09:58:49Z 2025-02-19T13:44:45Z Bei der Fakturierung von mehreren Aufträgen über die Sammelfaktura (Combine Invoicing) sollte es möglich sein, ein Dokument hinzuzufügen, dass jeder erzeugten Rechnung angehängt wird. So könnte z.B. für bestimmte Kundenkreise (z.B. über Auftragstypenfilter) sehr effizient ein Standard-Schreiben hinzugefügt werden (Aktionsangebote, Preisanpassung, Infoschreiben, Abfuhrkalender, etc.). Idee: Auf der Maske zur Sammelfakturierung (5030450) ein zusätzliches Feld ergänzen, in dem eine Datei ausgewählt werden kann, die dann bei der Ausführung den erzeugten Rechnungsdateien angehängt wird. sug_be4sp7nee6oczbf 2025-02-12T08:58:34Z 2025-02-19T14:24:52Z Sometimes there are different date formats in the date field column e.g. 2024-04-8 or 23/03/2009 plus time. It would be nice if we could set a uniform format for these types of date columns e.g. always the American date format or the European sug_88nhzcvxmw3eefc 2025-02-12T08:53:42Z 2025-02-19T14:29:39Z When filling in a date field when indexing a document, it would be more convenient to use a clickable date calendar for this. For example, in the "Piece date" column, this ensures that the date is recorded in a clear format (e.g. 14-1-2025 of 2025/01/14). These different date notations now ensure, for example, that the sorting does not work properly. sug_tqx2v423omjfpgg 2025-01-29T13:28:43Z 2025-02-19T14:54:20Z It is desirable to set a default content type per library. Now the first available content type based on alphabetical order is selected by default. sug_p5pjpqamlothowf 2025-01-16T11:52:53Z 2025-02-04T14:23:46Z Problem: -Current setup of 'Additional Search' allows documents within a document library to be accessed on other lists/cards in Business Central beyond the initial mapping. -All documents that can be related via the 'Additional Search' rule are included. -There is no option to configure access based on content types available in the source library. -This lack of granularity makes it impossible to intentionally exclude certain documents from the 'Additional Search' functionality. -The inability to exclude specific documents impacts both the visibility of sensitive documents and the overall performance due to the volume of documents accessed. Desired Change: -Introduce the ability to configure 'Additional Search' access based on content types available in the source library. This allows the exclusion of specific documents from the 'Additional Search' functionality, improving control over document visibility and reducing the number of documents accessed, thereby enhancing performance. sug_mhp7kzzogrth1xz 2025-01-02T13:58:58Z 2025-01-08T09:15:04Z Oftmals müssen wichtige Dokumente zu einem späteren Zeitpunkt nochmals betrachtet oder bearbeitet werden. Um den Nutzern dieser Systeme mehr Effizienz und Organisation zu bieten, wird eine Funktion gewünscht, die es ermöglicht, beim Ablegen eines Dokuments direkt eine Wiedervorlage bzw. einen Reminder zu erstellen. Diese neue Funktionalität soll den Nutzern die Möglichkeit bieten, während des Speichervorgangs von Dokumenten automatisch Wiedervorlagen mit spezifischen Erinnerungszeiträumen einzurichten. Integrierte Erinnerungserstellung: Beim Speichern eines Dokuments kann der Nutzer direkt eine Erinnerung an einem gewünschten Datum und einer gewünschten Uhrzeit einstellen. Benutzerdefinierte Erinnerungseinstellung: Der Nutzer kann benutzerdefinierte Erinnerungen einstellen, die aus Wiederholungsintervallen (täglich, wöchentlich, monatlich) und speziellen Benachrichtigungsoptionen bestehen. sug_xpwxgxvnqoypuig 2024-12-16T10:12:41Z 2025-08-05T12:10:21Z You now have to click on "attachments"-button on 2nd screen to see if attachment is available. Please develop a look-a-like as in MS Outlook with a paperclip so that end user immediately can see that attachment is related to selected document. sug_7l0gnvtluuxlyjg 2024-12-16T10:08:05Z 2025-01-08T09:20:52Z Recently you added the feature to see and preview the e-mail attachments. Is it possible to add a button to download the attachments? sug_8tratbfxjeourbb 2024-12-13T12:04:35Z 2025-01-07T15:53:11Z Within the DMS Online management environment it is desirable to enforce specific data formats when entering the meta-data, such as a date. We want to be able to archive documents with a date that is different from the creation date (the date the document is added to the archive). Enforcing a date format is essential. If this is not done, there is a risk that documents will be indexed incorrectly, which can lead to inconsistencies and problems in retrieving information. sug_soubrqlibh6u2iw 2024-12-05T15:29:35Z 2025-01-07T15:20:26Z "Umbuchungs Buch.-Blatt" und "Anlagen FiBu Buch.-Blätter" Those are needed when you posting something in the fixed assets module and want to attach the original invoice to the posting. sug_civfuvzxepnmnf2 2024-12-03T19:33:34Z 2025-02-19T14:44:41Z In our business (housing corporation) a lot of pictures are taken and need to be archived. The current support for working with large sets of pictures is not optimal. Might be nice if this could be improved. Real life examples: - A set of 33 pictures of 4 Mb each can't be uploaded (stays on 'processing' for half an hour, unacceptable user experience). - The workaround to add a bunch of pictures by sending them in an e-mail to yourself, then archiving that is also not viable (total file size can't be mailed). - Even if I manage to add the pictures, they end up cluttering up the list. Primary reason: the titles can't be edited when you upload multiple files at once. This makes them exceptions: where the user usually scans the list of titles, he has to check another meta property here ('Description' in our case). - Preview is not optimal because the images are not properly rotated, they don't seem to consider the rotation that is present in the EXIF data. sug_cld8meihqm3ezys 2024-11-27T10:36:57Z 2024-11-27T14:14:08Z Problem - The factbox-component (dropzone) currently supports a maximum of 10 content types. - It is possible / occurs that on a single Business Central table record such variety of documents are archived, that the number of different content types exceeds 10. - As a result, some documents are only visible under the total view instead of being presented by content type. Desired Change - Remove the limit on the maximum number of content types displayed in the datagrid. - Alternatively, make the limit on the number of content types configurable. sug_mdwsz5bxzl0n2l9 2024-11-19T09:00:10Z 2025-07-01T13:48:22Z Problem: • Users upload videos and audio files to Document Central, similar to how they upload images or documents. • These media files cannot be played directly in the datagrid preview. • Users are required to download these files to view or listen to their content. • This functionality is available in the underlying platforms like SharePoint and Azure Blob Storage. Desired Change: • Enable direct playback of video and audio files from the previewer in Document Central. • Eliminate the need for users to download media files to access their content. sug_a9j7xflpfembqdr 2024-11-19T08:57:48Z 2024-11-26T13:42:08Z Problem: • New customers using Document Central report confusion due to the current naming convention of the datagrid. • The datagrid name currently consists of “Document Central - Datagrid” followed by the name of the list on which the datagrid is opened. • This naming convention is reported as not intuitive or too technical and leads to misunderstandings. Desired change: • Make the “Document Central - Datagrid” portion of the datagrid name customizable, likewise to how the name of the Document Central factbox-component name is customizable sug_tgnkhklok1npahc 2024-11-19T08:56:17Z 2024-11-27T09:48:41Z Problem • The datagrid does not display the number of document records in the (filtered) overview. • Only a total count of a selection is visible in the facts block of the Document Central dropzone. Desired change • It is desirable for the datagrid to show a dynamic total count to always know how many document records are currently visible. sug_idgvb0iiivel7zq 2024-11-19T08:55:47Z 2025-07-01T13:52:10Z Problem • The document preview in the right pane or via ‘Selection’ > ‘View document’ displays the various pages of a document in a small format. • It currently does not show the page numbering for each page as part of the whole document. Desired Change • It would be desirable for this page view to also display the page numbering for each page as part of the entire document. • For example, the numbering should be shown as 1/3, 2/3, 3/3. sug_9xybeyguatbzmuq 2024-11-19T08:54:47Z 2024-11-26T12:49:32Z Problem: • Currently, metadata columns can only be modified in the datagrid for document entries and not for version control. • This limitation hinders the ability to tailor the presentation to the (process) usage of a user (or profile). Desired Change: • Enable the modification of metadata columns in the datagrid for version control as well. • This change would allow the presentation to be adjusted according to the (process) usage of a user (or profile). sug_ynhbnm3elkp7fej 2024-11-13T09:34:13Z 2024-11-25T15:45:06Z Currently you have to press "View Document" to show the document in the bigger document preview. It would be helpful if we could use dubble left-mouseclick to instantly show the preview of the document in the bigger document preview. With this you don't have to press "View Document" every time to navigate to the bigger preview of the document. This improvement saves a few clicks. sug_gohwtosi89qcxyd 2024-11-07T10:43:03Z 2024-11-25T15:33:28Z Problem: - The ‘Edit table’ functionality is highly effective and powerful for editing specific table data. - However, it is not possible to filter specific table records using this functionality. - This limitation requires endless scrolling through very large tables to find the correct record. Desired Change: - Implement a filtering option for the values presented on the ‘Edit table’ page. - This will allow users to quickly locate and edit specific records without extensive scrolling. sug_zgovnjluyhpsnsj 2024-11-05T09:41:58Z 2024-11-18T14:48:14Z Below the Dropzone, there is a limit of 10 content types, which appears to be based on alphabetical order. In the attached example, these content types only represent about 5% of all documents for this entity, which is not practical. Is it possible to set the order by library, so that we only see the content types that are relevant? sug_hgwehghc31ksdjv 2024-11-01T12:18:00Z 2024-11-04T14:55:27Z Problem: - When importing a Document Central configuration via the Wizard, existing setups for metadata-template values, default values, fixed values, silent drop values, and retention labels are overwritten. - Periodic updates of the setup in a Business Central environment using a centrally managed standard configuration result in the loss of custom setups. - Custom setups need to be manually corrected after each update. Desired Change: - Ensure that custom setups for default values, fixed values, silent drop values, and retention labels of metadata-template values can be preserved during the import of a new configuration sug_mty6tnom3ybppkm 2024-10-25T12:03:11Z 2025-09-23T07:00:33Z Problem: - Business Central tables can have multiple primary keys (PKs). - In the current mapping setup, only one PK can be selected to match documents to table records. - This limitation can cause documents from other records to appear incorrectly, as the selected PK matches across multiple records. Desired Change: - Allow other table fields (including additional PKs) to be automatically selected as metadata filters in the datagrid. - This change should enable a more accurate record-specific datagrid presentation. - Required is an option to define table fields as metadata filters within the datagrid. sug_icjnmu76ygporno 2024-10-08T13:05:54Z 2024-10-21T08:15:14Z There is a fundamental problem with file names such as VF+/123 for posted sales documents. It has now only become apparent in the course of the Simova extension (based on the file name). Microsoft would not allow a file name with a special character “/”, because for Microsoft a new folder begins with “/” (in the file directory). The fact that Simova uses the slash in the file name is theoretically correct, as this is the record. However, if the file is stored in a folder, this causes an error. Suggestion Sven Hiller: The filenames can be configured. Just a single statement is needed to removes invalid characters from a filename: Filename := FileManagement.GetSafeFileName(Filename); sug_f3rnpizgxc7rnbf 2024-10-07T12:43:18Z 2025-04-23T07:01:38Z It would be nice to be able to reindex a series of already archived documents in one go. For example, to enable the feature "publication external" on all documents in the OGE library with the document type: drawing/plan sug_3qq0na7z2u6lixj 2024-08-22T16:09:02Z 2024-09-05T11:28:13Z It would be useful if selected document lines from the Document Central datagrid could be exported to Excel sug_khnljkjy64zpezs 2024-08-08T12:28:46Z 2024-09-05T12:47:13Z It often happens that an incoming document has to be saved on different (customer / unit) cards. At present, it is only possible to save the document several times and to index it multiple times. We would like to be able to perform 1 document with 1 indexing action with the result that this document is linked to multiple cards. An example of such a situation is when a contractor sends a letter directly to customers. This letter must then be visible to the Customer Contact Center when a customer calls after this letter: this letter must then be retrievable from all customer (cards) that have received the letter from the contractor.