crm-debug

Diagnose missing CRM object visibility by validating EAV data and pivot views.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/aspectrr/denchclaw-workspace --skill crm-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: crm-debug
Source: https://github.com/aspectrr/denchclaw-workspace/tree/main/skills/crm-debug
Command: npx skills add https://github.com/aspectrr/denchclaw-workspace --skill crm-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging CRM objects not showing entries despite data existing in the database.

Core Features & Use Cases

  • Diagnose missing PIVOT views for EAV-based CRM objects (e.g., v_{object_name}) and identify where data cannot be read.
  • Validate that objects have corresponding entries and that API queries return entries and a non-zero totalCount.
  • Provide actionable steps to recreate or repair missing PIVOT views, then re-run API checks to confirm data visibility.

Quick Start

Verify the CRM object's data in objects and entries, check for a missing v_<object_name> Pivot view, create the view if missing, and re-query the API to confirm entries appear.

Frequently Asked Questions about crm-debug

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

FAQPage Schema
Why are CRM entries not showing in the UI when the data exists in the database?▼

CRM entries may not show because the EAV-based object is missing its required pivot view, commonly named v_{object_name}, which prevents the system from reading the data for display.

How do I diagnose missing pivot views for CRM objects?▼

Diagnose missing pivot views by verifying object data in the database, checking for the absence of the v_<object_name> view, and querying the API to confirm if entries return a non-zero totalCount.

What is the best way to fix CRM data visibility issues caused by missing v_ views?▼

Fix CRM data visibility by recreating the missing pivot view for the specific object and then re-running the API query to confirm that entries successfully appear with a non-zero totalCount.

How does an EAV-based CRM object rely on pivot views for API visibility?▼

EAV-based CRM objects rely on pivot views to flatten entity-attribute-value data into a queryable structure, allowing APIs to retrieve entries and return a non-zero totalCount for UI display.

What steps are needed to verify CRM object entries and confirm API visibility?▼

Verify CRM object entries by checking the database for existing data, creating the missing pivot view if absent, and re-querying the API to validate that entries appear with a non-zero totalCount.

Can I use this approach to debug CRM objects across any platform using EAV architecture?▼

Yes, this debugging approach applies to any EAV-based CRM system that relies on v_ views, guiding engineers to validate database entries, repair missing pivot views, and confirm API visibility.