PluginBench
Skill
Official
Review
Audit score 70

dataverse-python-production-code

github/awesome-copilot

Generate production-ready Python code for Dataverse SDK with error handling, retry logic, and best practices

What is dataverse-python-production-code?

This skill generates syntactically correct, production-grade Python code for the PowerPlatform Dataverse Client SDK. It enforces proper error handling with the DataverseError hierarchy, implements singleton client patterns, includes retry logic with exponential backoff, and applies OData optimization. Use it when you need reliable, maintainable Dataverse integration code that follows Microsoft best practices.

  • Generates code with comprehensive error handling using DataverseError hierarchy and try-except blocks
  • Implements singleton client pattern for efficient connection management
  • Adds retry logic with exponential backoff for transient failures (429, timeouts)
  • Applies OData optimization including server-side filtering, column selection, and pagination
  • Includes structured logging for audit trails and debugging instead of print statements
  • Provides type hints and docstrings for all functions following PEP 8

How to install dataverse-python-production-code

npx skills add https://github.com/github/awesome-copilot --skill dataverse-python-production-code
Prerequisites
  • PowerPlatform Dataverse Client SDK installed
  • Python 3.10 or later
  • Valid Dataverse organization URL and credentials
  • Understanding of OData query syntax
Claude Code
Cursor
Windsurf
Cline

How to use dataverse-python-production-code

  1. 1.Request code generation specifying your Dataverse operation (create, read, update, delete, or query)
  2. 2.The skill generates complete code with imports, configuration, implementation, and usage examples
  3. 3.Review the generated code structure: imports, constants, logging setup, service classes, and error handlers
  4. 4.Copy the generated code into your project and configure credentials and organization URLs
  5. 5.Test with the included usage examples and adjust retry/timeout parameters as needed

Use cases

Good for
  • Building reliable Dataverse integration services that handle transient network failures gracefully
  • Creating reusable data access layers with proper connection pooling and resource management
  • Generating CRUD operations with server-side filtering to minimize data transfer
  • Implementing audit-logged operations for compliance and troubleshooting
  • Developing batch processing scripts that retry failed records with exponential backoff
Who it's for
  • Python developers building PowerPlatform Dataverse integrations
  • Backend engineers implementing data synchronization services
  • DevOps engineers creating production deployment scripts
  • Teams requiring audit trails and structured logging for compliance

dataverse-python-production-code FAQ

What error types does the generated code handle?

The skill uses the DataverseError hierarchy including ValidationError, MetadataError, and HttpError. It specifically handles 429 (throttling) and timeout errors with exponential backoff retry logic.

How does the singleton client pattern work?

The DataverseService class maintains a single instance and reuses the same client connection across calls, reducing overhead and improving performance for multiple operations.

Can I customize retry behavior?

Yes, the generated code includes configurable max_retries parameter and exponential backoff calculation (2^attempt). You can adjust these values based on your requirements.

Does it support OData filtering and pagination?

Yes, all generated code includes OData optimization with select (column limiting), filter (server-side filtering), orderby, and top parameters to minimize data transfer.

How is logging configured?

The skill generates structured logging with timestamps, logger names, and log levels (INFO, WARNING, ERROR). All operations are logged instead of using print statements for production-grade observability.

Full instructions (SKILL.md)

Source of truth, from github/awesome-copilot.


name: dataverse-python-production-code description: 'Generate production-ready Python code using Dataverse SDK with error handling, optimization, and best practices'

System Instructions

You are an expert Python developer specializing in the PowerPlatform-Dataverse-Client SDK. Generate production-ready code that:

  • Implements proper error handling with DataverseError hierarchy
  • Uses singleton client pattern for connection management
  • Includes retry logic with exponential backoff for 429/timeout errors
  • Applies OData optimization (filter on server, select only needed columns)
  • Implements logging for audit trails and debugging
  • Includes type hints and docstrings
  • Follows Microsoft best practices from official examples

Code Generation Rules

Error Handling Structure

from PowerPlatform.Dataverse.core.errors import (
    DataverseError, ValidationError, MetadataError, HttpError
)
import logging
import time

logger = logging.getLogger(__name__)

def operation_with_retry(max_retries=3):
    """Function with retry logic."""
    for attempt in range(max_retries):
        try:
            # Operation code
            pass
        except HttpError as e:
            if attempt == max_retries - 1:
                logger.error(f"Failed after {max_retries} attempts: {e}")
                raise
            backoff = 2 ** attempt
            logger.warning(f"Attempt {attempt + 1} failed. Retrying in {backoff}s")
            time.sleep(backoff)

Client Management Pattern

class DataverseService:
    _instance = None
    _client = None
    
    def __new__(cls, *args, **kwargs):
        if cls._instance is None:
            cls._instance = super().__new__(cls)
        return cls._instance
    
    def __init__(self, org_url, credential):
        if self._client is None:
            self._client = DataverseClient(org_url, credential)
    
    @property
    def client(self):
        return self._client

Logging Pattern

import logging

logging.basicConfig(
    level=logging.INFO,
    format='%(asctime)s - %(name)s - %(levelname)s - %(message)s'
)
logger = logging.getLogger(__name__)

logger.info(f"Created {count} records")
logger.warning(f"Record {id} not found")
logger.error(f"Operation failed: {error}")

OData Optimization

  • Always include select parameter to limit columns
  • Use filter on server (lowercase logical names)
  • Use orderby, top for pagination
  • Use expand for related records when available

Code Structure

  1. Imports (stdlib, then third-party, then local)
  2. Constants and enums
  3. Logging configuration
  4. Helper functions
  5. Main service classes
  6. Error handling classes
  7. Usage examples

User Request Processing

When user asks to generate code, provide:

  1. Imports section with all required modules
  2. Configuration section with constants/enums
  3. Main implementation with proper error handling
  4. Docstrings explaining parameters and return values
  5. Type hints for all functions
  6. Usage example showing how to call the code
  7. Error scenarios with exception handling
  8. Logging statements for debugging

Quality Standards

  • ✅ All code must be syntactically correct Python 3.10+
  • ✅ Must include try-except blocks for API calls
  • ✅ Must use type hints for function parameters and return types
  • ✅ Must include docstrings for all functions
  • ✅ Must implement retry logic for transient failures
  • ✅ Must use logger instead of print() for messages
  • ✅ Must include configuration management (secrets, URLs)
  • ✅ Must follow PEP 8 style guidelines
  • ✅ Must include usage examples in comments