nexo-sharepoint-sync-rules

Automate deterministic archival of ERP documents into SharePoint with routing, metadata, and naming.

1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/buurguees/av-tech-p-gina-de-inicio --skill nexo-sharepoint-sync-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nexo-sharepoint-sync-rules
Source: https://github.com/buurguees/av-tech-p-gina-de-inicio/tree/main/.agents/skills/nexo-sharepoint-sync-rules
Command: npx skills add https://github.com/buurguees/av-tech-p-gina-de-inicio --skill nexo-sharepoint-sync-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This solution defines deterministic rules to archive ERP-generated documents into SharePoint with correct path, naming, and metadata, ensuring reproducibility and auditability.

Core Features & Use Cases

  • Deterministic archival routing: maps documents to fixed SharePoint paths based on document type and year.
  • Metadata mapping by document type: assigns required metadata fields such as TipoDocumento, NumeroDocumento, FechaDocumento, MesFiscal, AnoFiscal, DocumentoERPId, HashPDF, ArchivadoPor, and ArchivadoEn.
  • Naming conventions & validation: enforces consistent file naming and pre-archival validations to prevent misplacement.
  • Auditability & error handling: logs decisions and errors for traceability and rollback if needed.

Quick Start

Configure deterministic archival rules to map ERP documents to their SharePoint destinations.

Frequently Asked Questions about nexo-sharepoint-sync-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate ERP document archival to SharePoint with correct metadata?

Automating ERP document archival to SharePoint requires deterministic routing rules that map document types to fixed paths, enforce mandatory metadata fields like NumeroDocumento, and validate naming conventions before storage to ensure reproducibility and auditability.

What metadata fields are required for deterministic SharePoint document archiving?

Deterministic SharePoint document archiving requires mandatory metadata fields including TipoDocumento, NumeroDocumento, FechaDocumento, MesFiscal, AnoFiscal, DocumentoERPId, HashPDF, ArchivadoPor, and ArchivadoEn to ensure consistent storage and traceability.

How do I route ERP invoices and tickets to different SharePoint sites automatically?

Routing ERP invoices and tickets to different SharePoint sites automatically requires deterministic archival rules that map documents to fixed paths based on document type and year, ensuring consistent placement and preventing misplacement through pre-archival validations.

Can I ensure auditability when archiving accounting documents from an ERP to SharePoint?

Ensuring auditability when archiving accounting documents from an ERP to SharePoint requires logging all routing decisions and errors. This provides traceability for archived documents and supports rollback if needed.

How do I enforce consistent naming conventions for ERP documents stored in SharePoint?

Enforcing consistent naming conventions for ERP documents stored in SharePoint requires pre-archival validations that check file names against deterministic rules before storage, preventing misplacement and ensuring reproducible document retrieval.

What is the best way to prevent misplacement of ERP documents in SharePoint?

Preventing misplacement of ERP documents in SharePoint requires deterministic archival rules that enforce fixed routing paths, mandatory metadata mapping, and pre-archival naming validations to guarantee consistent storage across sites.