datamanager-to-pdk

Data Manager Form → PDK Plugin Conversion

What is a DM Form?

A DM (Data Manager) form is a Mission Control scripting artifact — a binary .fsf file containing:

• ProFusion controls rendered in a legacy form host (hierarchy selectors, checkboxes, grids, buttons)
• VBScript event handlers embedded in each button/control, with inline SQL using ADODB
• Two planogram selectors: a Source hierarchy control and a Target(s) hierarchy control
• Direct SQL run via Application.ProfusionSupport.ADOConnection — no stored procedures

The FSF format is a compound binary (OLE) document. To read logic from it: use the Read tool on the .fsf file. Despite being binary, the VBScript and control names are embedded as wide-character (UTF-16LE) strings that appear as readable text. Look for:

• Control names near their type identifiers (CObjCheckbox, CObjActiveX, CObjEdit, etc.)
• VBScript code — large readable blocks containing Sub, Function, ADODB.Command, Application. calls
• Form title — appears near the top as a readable string

DM vs OpenAccess: Use crisp-tc:datamanager-to-openaccess if the target is an OpenAccess ASCX control. Use this skill when the target is a PDK plugin (WPF/MVVM, single DLL deployed to %AppData%\Cantactix\MissionControl\Plugins).

---

DM → PDK Concept Mapping

DM Form Element	PDK Equivalent
ProFusionHierarchyCtrl_Src (source selector)	A SourcePlanogramDbKey int property on the ViewModel, bound to a ComboBox/TextBox
ProFusionHierarchyCtrl_Trg (target selector)	BatchProvider.GetSpaceFiles() — the planograms selected in MC's batch panel
Button click VBScript (cmd_Xxx)	RunCommand in ViewModel → ProcessAsync in Processor
Application.ProfusionSupport.ADOConnection	CkbProvider.GetCkbDbConnection().ConnectionString → new DB(...) → SQLHelper
Inline SQL built in VBScript	Stored procedures in CKB, called via the DB class
chk_SomeName.check = 1	bool property on ViewModel, bound to WPF CheckBox
grid_TagList.Object.Count / .Selected(i)	BindableCollection<TagItemViewModel>, rendered as ListBox with checkboxes
Application.ShowStatusMsg / ShowWaitCursor	ReportProgress / ReportCompleted / ReportFailed in Processor
Application.MessageBox	Result message shown in View after ProcessAsync completes
Oracle/MSS dual-path SQL	SQL Server (MSS path) only — CKB is always SQL Server

---

One DM Button = One PDK Plugin (Usually)

DM forms often have 3–6 buttons. A PDK plugin typically has one Run button. Rules:

• If the operations share the same source/target selection and users commonly run them together → combine into one plugin with checkboxes selecting which operations to perform.
• If operations are truly independent (different inputs, different purposes) → separate plugins.
• Never expose unrelated operations in a single plugin just because they were on the same DM form.

---

Source Planogram Pattern

DM forms have a dedicated Source hierarchy control. In PDK, BatchProvider.GetSpaceFiles() serves as the target list. For the source, choose one of:

Option	When to use
A — First selected pog is source	Simplest. User adds source first in the MC batch panel; plugin treats index 0 as source, rest as targets. Requires a note in the UI.
B — Dedicated source selector	A ComboBox/TextBox in the View where user types a DBKey or searches by name. Better UX when source ≠ any of the targets.
C — Master/config-driven source	Client has a fixed master planogram per store cluster. Expose as a preset setting.

Most DM form migrations use Option B.

---

Scope Reduction Guidance

The request will specify which DM buttons to include. Common reductions:

DM Button	PDK include?	Reason
Copy Action List	Often yes	Simple single-field copy, high value
Copy Tags	Often yes	Frequently used, maps cleanly to SQL
Copy Textboxes	Sometimes	Involves ix_spc_drawing; adds complexity
Copy Notes	Rarely	Very client-specific

---

Key CKB Tables (Space Planning copy operations)

Table	Relevant Columns	Purpose
ix_spc_planogram	dbkey, pgactionlist	Planogram header; Action List is stored here
ix_spc_performance	dbparentplanogramkey, dbparentproductkey, desc35–desc50	Per-product per-planogram; Tags (desc35–50) live here
ix_spc_drawing	dbparentplanogramkey, type (5=textbox)	Textboxes/annotations

Tag Fields

Tags are desc35 through desc50 on ix_spc_performance (16 fields, 0-indexed: i=0 → desc35, i=15 → desc50).

The DM form's grid_Tag_List shows these tags. In PDK: use a BindableCollection<TagItemViewModel> where each item has a Name and IsSelected bool. Default all to true; user unchecks to exclude.

Primary ID Join Strategy

When copying tags, the join on ix_spc_performance must match products between source and target planograms. The request may specify:

Mode	Join on
ID	pf_s.dbparentproductkey = pf.dbparentproductkey
UPC	Join via ix_spc_planogram_item matching on upcp
BOTH	Try ID first, fall back to UPC

Expose this as a RadioButton group in the View; pass the enum to the Processor.

---

VBScript → Stored Procedure Translation

Move all inline SQL to CKB stored procedures. Pattern:

VBScript variable          → SQL parameter
{SourceKey}                → @sourceDbKey INT
{key_string} (CSV list)    → @targetDbKeys VARCHAR(MAX), parsed with STRING_SPLIT
Oracle BEGIN/COMMIT block  → SQL Server BEGIN/END (no COMMIT needed; auto-commit)
Dynamic "SET col=val,..."  → CASE-based bitmask column selection

Copy Action List — stored proc template

CREATE PROCEDURE [dbo].[usp_CopyActionList]
    @sourceDbKey  INT,
    @targetDbKeys VARCHAR(MAX)   -- comma-separated target dbkeys
AS
BEGIN
    UPDATE pl
    SET pl.pgactionlist = (
        SELECT pl_s.pgactionlist
        FROM ix_spc_planogram pl_s
        WHERE pl_s.dbkey = @sourceDbKey
    )
    FROM ix_spc_planogram pl
    WHERE pl.dbkey IN (SELECT value FROM STRING_SPLIT(@targetDbKeys, ','))
END

Copy Tags — stored proc template (ID-join, bitmask)

CREATE PROCEDURE [dbo].[usp_CopyTags]
    @sourceDbKey  INT,
    @targetDbKeys VARCHAR(MAX),
    @tagMask      BIGINT,   -- bitmask: bit 0=desc35, bit 1=desc36 ... bit 15=desc50
    @clearFirst   BIT
AS
BEGIN
    -- Optional: null out excluded tags on targets first
    IF @clearFirst = 1
    BEGIN
        UPDATE pf SET
            pf.desc35 = CASE WHEN (@tagMask &     1) = 0 THEN NULL ELSE pf.desc35 END,
            pf.desc36 = CASE WHEN (@tagMask &     2) = 0 THEN NULL ELSE pf.desc36 END,
            -- ... desc37–desc49 with appropriate bit shifts ...
            pf.desc50 = CASE WHEN (@tagMask & 32768) = 0 THEN NULL ELSE pf.desc50 END
        FROM ix_spc_performance pf
        WHERE pf.dbparentplanogramkey IN (SELECT value FROM STRING_SPLIT(@targetDbKeys, ','))
    END

    -- Copy selected tags from source → targets (ID join)
    UPDATE pf SET
        pf.desc35 = CASE WHEN (@tagMask &     1) > 0 THEN pf_s.desc35 ELSE pf.desc35 END,
        pf.desc36 = CASE WHEN (@tagMask &     2) > 0 THEN pf_s.desc36 ELSE pf.desc36 END,
        -- ... desc37–desc49 ...
        pf.desc50 = CASE WHEN (@tagMask & 32768) > 0 THEN pf_s.desc50 ELSE pf.desc50 END
    FROM ix_spc_performance pf
    INNER JOIN ix_spc_performance pf_s
        ON  pf_s.dbparentplanogramkey = @sourceDbKey
        AND pf_s.dbparentproductkey   = pf.dbparentproductkey   -- ID join
    WHERE pf.dbparentplanogramkey IN (SELECT value FROM STRING_SPLIT(@targetDbKeys, ','))
END

---

Step-by-Step Conversion Checklist

1. Read the .fsf file — extract VBScript for each button into plain text
2. Identify buttons to include per the feature request
3. Decide source selection pattern (Option A/B/C above)
4. Decide Primary ID join mode (ID / UPC / BOTH) if copying Tags
5. Load pdk-development skill — follow its checklist for scaffolding the solution
6. Load ckb-schema skill — reference table/column names when writing stored procs
7. Use PDK.SegmentBreaks as structural template (C:\Users\bwolf\source\repos\PDK.SegmentBreaks\):
   • Rename namespaces: PDK.SegmentBreaks → [Client].[FeatureName]
   • Remove SegmentBreaks-specific code (ProSpaceProcessor, PlanogramFileRef, flat-file logic)
   • Keep: FeatureFactory wiring, ViewModel/Processor base class structure, DB/SQLHelper layer, TestApp
8. Write stored procedures — one per logical operation (CopyActionList, CopyTags, etc.)
9. Build ViewModel: source selector property, operation checkboxes, tag list collection, IsValid
10. Build View: source input, operation checkboxes, tag ListBox, Run button
11. Build Processor: call stored procs via DB class, report progress per target pog
12. Test in TestApp against a dev CKB database

---

Related Skills

• pdk-development — full PDK project structure, base classes, XAML patterns, deploy target
• ckb-schema — CKB table names, stored proc conventions, SQLHelper usage
• datamanager-to-openaccess — use instead of this skill when target is an OA ASCX control