Problem/Motivation

The Entity Mesh report at admin/reports/entity-mesh/table provides a CSV export (the "Data export" display attached to the view). In that export, the Entity ID (Source) and Entity ID (Target) columns are written as bare numeric entity IDs.

A raw ID is not portable outside the site: whoever opens the CSV cannot reach the referenced entity without manually reconstructing each URL from the ID and entity type. This makes the export hard to audit, share, or cross-reference against other tools, which is the main reason to export the report in the first place.

While we want to include full absolute URIs in the export, modifying the output of the Entity ID columns causes a mismatch between the column header name and its actual contents (an ID column containing a full URL string).

Steps to reproduce

  1. Enable the Entity Mesh module and populate the mesh so the report has rows.
  2. Go to admin/reports/entity-mesh/table.
  3. Download the CSV export.
  4. Open the file and inspect the columns.

Expected: Dedicated columns providing full URIs pointing to the source and target entities alongside their IDs.

Actual: Only bare numeric IDs (for example 12, 48) are available, with no clean URL reference.

Proposed resolution

Keep the existing Entity ID (Source) and Entity ID (Target) columns intact as raw numeric IDs to match their headers. Instead, introduce two new dedicated columns to the export display: Source URL and Target URL. These new columns will render the full absolute canonical URI of the respective entities on export displays.

User interface changes

None on screen. Only the downloaded CSV changes: it now features two additional columns, Source URL and Target URL, containing full absolute URIs. The HTML report pages are completely unchanged.

API changes

None to public APIs.

Data model changes

None. No schema, storage, or stored configuration data model changes. The only configuration change is the addition of the two new URL field handlers on the view's default display configuration.

CommentFileSizeAuthor
#4 issue_on_csv_name.png5.34 KBeduardo morales alberti
#3 entity_mesh_export_as_uri.png186.9 KBeduardo morales alberti

Issue fork entity_mesh-3608136

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

eduardo morales alberti created an issue. See original summary.

eduardo morales alberti opened merge request !81

eduardo morales alberti’s picture

eduardo morales alberti
Primary language Spanish
Location Spain, 🇪🇺
commented
StatusFileSize
new entity_mesh_export_as_uri.png186.9 KB

Ready, waiting for tests
Entity mesh add source/target url

eduardo morales alberti’s picture

eduardo morales alberti
Primary language Spanish
Location Spain, 🇪🇺
commented
StatusFileSize
new issue_on_csv_name.png5.34 KB

Solve the issue with CSV export date when token module is not available:
Issue CSV name
Use the provided one by the core:

-      filename: 'entity_mesh_report_[date:html_time].csv'
+      filename: 'entity_mesh_report_[date:custom:Y-m-d_H-i-s].csv'

eduardo morales alberti’s picture

eduardo morales alberti
Primary language Spanish
Location Spain, 🇪🇺
commented
Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.