Run any Skill in Manus with one click

d365fo-form-navigation

Stars4

Forks0

UpdatedMay 28, 2026 at 13:10

Use when user asks about D365FO forms, menu items, workspace tiles, or UI navigation. "where is vendor invoice journal in the menu", "what data sources does PurchTable form have", "which menu item opens VendInvoiceJournal", "find the workspace for accounts payable", "what forms use CustTable as a data source", "which tile links to vendor invoices", "find all menu items under Procurement module", "form metadata for SalesTable"

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

AurelienClere-365

AurelienClere-365/d365fo-cowork-plugin

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	d365fo-form-navigation
description	Use when user asks about D365FO forms, menu items, workspace tiles, or UI navigation. "where is vendor invoice journal in the menu", "what data sources does PurchTable form have", "which menu item opens VendInvoiceJournal", "find the workspace for accounts payable", "what forms use CustTable as a data source", "which tile links to vendor invoices", "find all menu items under Procurement module", "form metadata for SalesTable"
license	MIT
metadata	{"version":"1.0"}

D365FO Form & Navigation Discovery

Explore form definitions, data sources, menu items, workspace tiles, and navigation paths within D365FO — without opening Visual Studio or a live AOS.

When to use

User needs to know the data sources (tables) backing a specific form
User wants to find which menu item or tile navigates to a feature
User is writing a form extension and needs the form's data source structure first
User is documenting navigation paths for a functional design document
User wants to find all forms related to a business area (e.g. "procurement")

Workflow

Identify the target. Extract form names, module names, or business concepts.
Look up the form. Call get_form(formName) — returns data sources, the source file path, and the top-level form type (ListPage, SimpleList, Details, etc.).
If form name is unknown, call search_any(query) with the business concept and filter results to AxForm type.
Look up menu items. Call get_menu_item(menuItemName) — returns the object it points to (form, report, class), the menu item type (Display/Action/Output), and the label.
Look up tiles. Call search_tiles(query) to find workspace tiles by business concept, then follow up with the tile's linked menu item if needed.
Look up workspaces. Call search_workspaces(query) to find the workspace descriptor and its constituent tiles and KPIs.

Output Format

Form data sources

Data source	Table	Join mode	Link type
SalesTable	SalesTable	—	Root
SalesLine	SalesLine	InnerJoin	1:N child
CustTable	CustTable	OuterJoin	N:1 reference

Menu item

Property	Value
Name	VendInvoiceJournalListPage
Type	Display
Object	VendInvoiceJournal (Form)
Label	Vendor invoice journal
Module	Accounts payable

Notes

Form names in D365FO usually match the primary table name (e.g. SalesTable form for the SalesTable table). Start there if the user gives a table name.
Extensions of a form live in *_Extension objects — check find_extensions(formName) if the user asks what customisations exist on the form.
Workspace tiles are the entry point to most functional areas; search tiles first when a user describes a functional feature rather than a technical object name.

More from this repository

same repository

d365fo-batch-runbase

AurelienClere-365/d365fo-cowork-plugin

Use when user asks about D365FO batch jobs, RunBase, or SysOperation framework. "does a batch job already exist for vendor aging", "scaffold a SysOperation for invoice processing", "find batch jobs related to purchase order cleanup", "RunBase vs SysOperation when to use which", "generate a batch class for ledger closing", "what existing batch jobs post vendor invoices", "scaffold a RunBaseBatch for periodic inventory recalculation"

2026-05-284

d365fo-business-events

AurelienClere-365/d365fo-cowork-plugin

Use when user asks about D365FO business events, outbound notifications, or event-driven integrations. "does a business event exist for purchase order confirmation", "what payload does VendorInvoicePosted send", "find business events related to vendor invoices", "scaffold a custom business event for approval workflow", "list all business events in Procurement", "what contract class does PurchaseOrderConfirmed use", "trigger Power Automate on sales order confirmation", "outbound event when invoice is posted"

2026-05-284

d365fo-class-analysis

AurelienClere-365/d365fo-cowork-plugin

Use when user asks about D365FO classes, class hierarchies, CoC extensions, or event handlers. "what classes handle purchase invoice posting", "who extends SalesFormLetter", "CoC extensions on PurchFormLetter_Invoice", "class hierarchy for SalesLineType", "event handlers for SalesTable insert", "which class handles ledger posting", "find all extensions of VendInvoiceInfoTable", "what event subscribers exist for CustTable", "how many customizations are on PurchFormLetter"

2026-05-284

d365fo-data-entity-discovery

AurelienClere-365/d365fo-cowork-plugin

Use when user asks about D365FO data entities for integration, DMF import/export, or OData. "what data entity should I use to import vendor invoices via DMF", "which entity exposes customer invoices for OData", "import customers from Excel", "DMF entity for purchase orders", "OData endpoint for sales orders", "integration entity for inventory on-hand", "which entity should I use to export GL journals", "data entity for vendor master data"

2026-05-284

d365fo-enum-edt

AurelienClere-365/d365fo-cowork-plugin

Use when user asks about D365FO Extended Data Types (EDTs) or enums. "what EDT should I use for a reference number field", "does an enum exist for approval status", "suggest an EDT for a percentage field", "what base type is CustAccount", "find enums related to vendor status", "what values does PurchStatus have", "create an EDT for a new currency amount field", "what is the parent EDT of SalesIdBase"

2026-05-284

d365fo-extension-strategy

AurelienClere-365/d365fo-cowork-plugin

Use when user asks how to extend or customize D365FO without overlayering base code. "how to extend VendTable without overlayering", "best way to add a field to SalesTable", "can I use CoC for PurchFormLetter", "extension point for SalesLine validation", "how to add logic when a customer is saved", "modify behavior of CustPostInvoice class", "extend a form without touching base objects", "what extension strategy should I use", "difference between CoC and event handler"

2026-05-284

name	d365fo-form-navigation
description	Use when user asks about D365FO forms, menu items, workspace tiles, or UI navigation. "where is vendor invoice journal in the menu", "what data sources does PurchTable form have", "which menu item opens VendInvoiceJournal", "find the workspace for accounts payable", "what forms use CustTable as a data source", "which tile links to vendor invoices", "find all menu items under Procurement module", "form metadata for SalesTable"
license	MIT
metadata	{"version":"1.0"}

D365FO Form & Navigation Discovery

Explore form definitions, data sources, menu items, workspace tiles, and navigation paths within D365FO — without opening Visual Studio or a live AOS.

When to use

User needs to know the data sources (tables) backing a specific form
User wants to find which menu item or tile navigates to a feature
User is writing a form extension and needs the form's data source structure first
User is documenting navigation paths for a functional design document
User wants to find all forms related to a business area (e.g. "procurement")

Workflow

Identify the target. Extract form names, module names, or business concepts.
Look up the form. Call get_form(formName) — returns data sources, the source file path, and the top-level form type (ListPage, SimpleList, Details, etc.).
If form name is unknown, call search_any(query) with the business concept and filter results to AxForm type.
Look up menu items. Call get_menu_item(menuItemName) — returns the object it points to (form, report, class), the menu item type (Display/Action/Output), and the label.
Look up tiles. Call search_tiles(query) to find workspace tiles by business concept, then follow up with the tile's linked menu item if needed.
Look up workspaces. Call search_workspaces(query) to find the workspace descriptor and its constituent tiles and KPIs.

Output Format

Form data sources

Data source	Table	Join mode	Link type
SalesTable	SalesTable	—	Root
SalesLine	SalesLine	InnerJoin	1:N child
CustTable	CustTable	OuterJoin	N:1 reference

Menu item

Property	Value
Name	VendInvoiceJournalListPage
Type	Display
Object	VendInvoiceJournal (Form)
Label	Vendor invoice journal
Module	Accounts payable

Notes

Form names in D365FO usually match the primary table name (e.g. SalesTable form for the SalesTable table). Start there if the user gives a table name.
Extensions of a form live in *_Extension objects — check find_extensions(formName) if the user asks what customisations exist on the form.
Workspace tiles are the entry point to most functional areas; search tiles first when a user describes a functional feature rather than a technical object name.