forgex-dynamic-table-troubleshooting

Diagnose FxDynamicTable column rendering and configuration issues across API to frontend layers.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/codernai14-source/Forgex --skill forgex-dynamic-table-troubleshooting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forgex-dynamic-table-troubleshooting
Source: https://github.com/codernai14-source/Forgex/tree/main/.cursor/skills/forgex-dynamic-table-troubleshooting
Command: npx skills add https://github.com/codernai14-source/Forgex --skill forgex-dynamic-table-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Forgex dynamic table troubleshooting helps developers diagnose and fix issues where FxDynamicTable columns do not render, column configurations are saved incorrectly, field linkage is inconsistent, or table-code mappings are mismatched.

Core Features & Use Cases

  • Five-layer link debugging guide to identify where data loss occurs from API response to frontend slot.
  • Structured, repeatable troubleshooting steps for column visibility, configuration merges, and table-code mappings.
  • Use Cases: When a user reports "table not shown" or "columns missing" or "column settings not saved," apply this skill to diagnose.

Quick Start

Begin by running the five-layer diagnostic sequence from API response to frontend slot to identify and fix the root cause of the table not displaying.

Frequently Asked Questions about forgex-dynamic-table-troubleshooting

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

FAQPage Schema
Why are dynamic table columns not rendering in my Forgex application?

Dynamic table columns fail to render when field linkage is inconsistent across API, DTO/VO, service, and frontend configurations. Running an end-to-end diagnostic from API response to frontend slot identifies where data loss occurs.

How do I debug FxDynamicTable column settings that fail to save?

Debug FxDynamicTable column settings by validating configuration merging and table_code mappings. Apply structured troubleshooting steps to verify that visibility controls and field linkage mappings meet expected behavior across all layers.

What is the best way to troubleshoot missing columns in a dynamic table?

The best way to troubleshoot missing columns is applying a five-layer link debugging guide. This process traces data flow from API response through DTO/VO and service layers to the frontend slot to locate the failure point.

How do I fix field linkage mapping inconsistencies between backend and frontend?

Fix field linkage mapping inconsistencies by validating data flow from API response to frontend slot. Ensure configuration merging, visibility controls, and table_code mappings align across API, service, and frontend configurations.

Does troubleshooting Forgex dynamic tables require checking both API and frontend configurations?

Yes, troubleshooting Forgex dynamic tables requires checking both API and frontend configurations. End-to-end validation from API response through DTO/VO and service layers to frontend slots ensures consistent column rendering and configuration.

Dynamic table not showing in Forgex after API update, what should I check?

When a dynamic table is not showing after an API update, check the five-layer diagnostic sequence. Verify API response data, DTO/VO mappings, service configurations, configuration merging, and frontend slot rendering to isolate the issue.