Mesh Indexer Network Files

The Mesh Indexer Network Files node allows users to trigger a full indexing operation against a specific data source (such as Autodesk Vault, Autodesk Construction Cloud, or SharePoint). This process is typically used to populate or refresh a Mesh index for use in downstream workflows, search, or analytics.

Overview

This node executes a full reindexing operation using preconfigured settings. It retrieves source data, generates enriched metadata (including optional OCR and embedding information), and updates an index in the Mesh system.

The indexing behavior can be controlled by the Index Name and Mesh Index Type parameters.

---

Inputs

Label	Description	Required	Example
Index Name	The identifier of the Mesh index to target (e.g., minuteview_index_vault)	✅	minuteview_index_sharepoint
Mesh Index Type	The indexing mode to run. Only FullDataReIndex and FullContentReIndex are currently supported by this node.	✅	FullContentReIndex

Supported Mesh Index Type Values

• FullContentReIndex — Re-indexes all content, regenerating embeddings and full text.
• FullDataReIndex — Re-indexes only the metadata without regenerating full content.
• ❗Other types like UpdateFromDate and UpdateDataOnExisting are defined but not currently active in this node implementation.

---

Outputs

Output	Description
Indexing Status	Task status will be marked as Completed or Fail.
Status Message	Returns "Indexing Completed Successfully" on success or a detailed error message on failure.

---

Execution Logic

1. Validation: The task checks that Index Name and Mesh Index Type are supplied.

2. Full Indexing:

   • Selects the data source (Vault, ACC, or SharePoint) based on hardcoded logic (⚠ This may need to be updated to dynamically use the Index Name).
   • Builds indexerSettings, enabling full content, embeddings, and thumbnail generation.
   • Executes the indexer and logs duration.

3. Configuration Management:

   • Updates the last indexed timestamp in a JSON config file located at C:\Indexing\config_{indexName}.json.
   • Supports fallback mechanisms for retrieving or creating config files.

---

Notes

• Currently, only the SharePoint data source (minuteview_index_sharepoint) is active in code. Switching to other sources like ACC or Vault requires manual changes to the datasource variable in the FullIndexer() method.
• The task retrieves connector settings from the backend API at /api/Mesh/GetMeshConnectors, though this value is unused in the current implementation.
• Index progress logging is commented out. To enable real-time progress, uncomment the ItemIndexer and ProcessAllAsync code block.

---

Known Limitations / To Do

• [ ] Update datasource selection logic to map dynamically from Index Name input.
• [ ] Implement RunIndexer() method for additional indexing types (UpdateFromDate, etc.).
• [ ] Consider exposing data source selection to the front-end config if multiple are to be supported by users.

---

Example Use Case

Use this node after configuring document connectors (e.g., SharePoint) to trigger a full reindex of the content and metadata for search and analytics usage. Place it at the start of an automation pipeline or as part of a scheduled workflow refresh.

---