d365fo-mcp 1.16.2 → 1.17.0

package/dist/bridge/bridgeAdapter.js

@@ -1259,6 +1259,10 @@ const BRIDGE_MODIFY_OPS = new Set([
     // No C# op exists for query ranges on entities — served entirely by a
     // direct-XML writer (data-entity is already in BRIDGE_MODIFY_TYPES).
     'add-query-range', 'remove-query-range',
+    // Routed straight to the XML writer by XML_ONLY_MODIFY_PAIRS below, but the
+    // dispatch gate is checked FIRST — an op absent here is refused as unknown
+    // before the pair table is ever consulted.
+    'report-design',
 ]);
 /**
  * Supported object types for bridge-based modification.
@@ -1292,6 +1296,12 @@ const XML_ONLY_MODIFY_PAIRS = {
     'remove-entry-point': new Set(['security-privilege']),
     'remove-diagnostic-suppression': new Set(['ignore-diagnostic-list']),
     'add-diagnostic-suppression': new Set(['ignore-diagnostic-list']),
+    // An AxReport has no bridge write path at all — IMetadataProvider cannot express
+    // a dataset field or a report parameter through a Dictionary<string,string> — and
+    // `report` is deliberately absent from BRIDGE_MODIFY_TYPES for that reason. Without
+    // this pair the caller would get "the bridge could not resolve the object" instead
+    // of the operation actually running.
+    'report-design': new Set(['report']),
 };
 /**
  * Names the properties the bridge could not write, for appending to a success message.

package/dist/knowledge/atlNodes.generated.d.ts

@@ -0,0 +1,55 @@
+/**
+ * GENERATED by scripts/oracles/atlNodes.ts — do not edit.
+ *
+ * The Acceptance Test Library's data tree, read from the AOT on a VM.
+ * 1105 ATL data classes, 38 root modules,
+ * 351 nodes that produce a table or an ATL entity.
+ *
+ * The root class declares ONE accessor of its own; every module below arrives on
+ * an extension class in another package, which is why a missing package reference
+ * fails on `data.invent()` rather than on `AtlDataRootNode`.
+ */
+/** A module hanging off `AtlDataRootNode::construct()`. */
+export interface AtlRootModule {
+    /** Accessor as written in a test: `data.invent()`. */
+    readonly accessor: string;
+    /** The node class it returns. */
+    readonly node: string;
+    /** The package that DEFINES it — the model must reference this one. */
+    readonly package: string;
+}
+/** A node that hands back a record: `data.cust().customers().default()`. */
+export interface AtlTableNode {
+    /** Table or ATL entity the node produces. */
+    readonly produces: string;
+    /** Full accessor path from the root, excluding `data.`. */
+    readonly path: string;
+    readonly node: string;
+    readonly package: string;
+    /**
+     * `default` returns the demo-data record and reuses it; `createDefault` makes a
+     * new one. Master data mostly offers the first, transactions the second.
+     */
+    readonly kind: 'default' | 'createDefault';
+    /**
+     * When `produces` is an AtlEntity wrapper, the buffer `.record()` hands back.
+     * Absent when the node already returns a table.
+     */
+    readonly record?: string;
+}
+export declare const ATL_ROOT_MODULES: readonly AtlRootModule[];
+export declare const ATL_TABLE_NODES: readonly AtlTableNode[];
+/** The packages a model needs in its Descriptor before any of this compiles. */
+export declare const ATL_PACKAGES: readonly string[];
+/**
+ * EVERY node that yields the given buffer, likeliest first. Several usually do,
+ * and they are not interchangeable: `SalesTable` comes from both
+ * `sales().salesOrders()` and `sales().returnOrders()`, and a helper that
+ * silently returned one of them would hand a return order to a test about an
+ * order. Matched on the buffer a test declares, so `CustTable` finds the node
+ * producing an AtlEntityCustomer.
+ */
+export declare function atlNodesForTable(tableName: string): AtlTableNode[];
+/** The arrange line for one node, e.g. `data.cust().customers().default().record()`. */
+export declare function atlArrangeLine(node: AtlTableNode): string;
+//# sourceMappingURL=atlNodes.generated.d.ts.map