@simplysf/simply 3.5.0 → 4.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +405 -5
  2. package/package.json +3 -3
package/README.md CHANGED
@@ -20,11 +20,18 @@ This package is part of the [`@simplysf/simply`](https://github.com/SimplySF/sim
20
20
 
21
21
  <!-- commands -->
22
22
 
23
+ - [`sf simply aep at4dx binding create`](#sf-simply-aep-at4dx-binding-create)
23
24
  - [`sf simply aep at4dx binding list`](#sf-simply-aep-at4dx-binding-list)
25
+ - [`sf simply aep at4dx binding update`](#sf-simply-aep-at4dx-binding-update)
26
+ - [`sf simply aep at4dx binding validate`](#sf-simply-aep-at4dx-binding-validate)
24
27
  - [`sf simply aep at4dx domain-process-binding create`](#sf-simply-aep-at4dx-domain-process-binding-create)
25
28
  - [`sf simply aep at4dx domain-process-binding list`](#sf-simply-aep-at4dx-domain-process-binding-list)
26
29
  - [`sf simply aep at4dx domain-process-binding set`](#sf-simply-aep-at4dx-domain-process-binding-set)
27
30
  - [`sf simply aep at4dx domain-process-binding validate`](#sf-simply-aep-at4dx-domain-process-binding-validate)
31
+ - [`sf simply aep at4dx field-set-inclusion create`](#sf-simply-aep-at4dx-field-set-inclusion-create)
32
+ - [`sf simply aep at4dx field-set-inclusion list`](#sf-simply-aep-at4dx-field-set-inclusion-list)
33
+ - [`sf simply aep at4dx field-set-inclusion update`](#sf-simply-aep-at4dx-field-set-inclusion-update)
34
+ - [`sf simply aep at4dx field-set-inclusion validate`](#sf-simply-aep-at4dx-field-set-inclusion-validate)
28
35
  - [`sf simply apex execute`](#sf-simply-apex-execute)
29
36
  - [`sf simply apex logs purge`](#sf-simply-apex-logs-purge)
30
37
  - [`sf simply apex trace setup`](#sf-simply-apex-trace-setup)
@@ -54,6 +61,76 @@ This package is part of the [`@simplysf/simply`](https://github.com/SimplySF/sim
54
61
  - [`sf simply sobject history query`](#sf-simply-sobject-history-query)
55
62
  - [`sf simply sobject history schema`](#sf-simply-sobject-history-schema)
56
63
 
64
+ ## `sf simply aep at4dx binding create`
65
+
66
+ Create a new AT4DX Application Factory binding (Service, Selector, or Domain) in local source and/or a connected org.
67
+
68
+ ```
69
+ USAGE
70
+ $ sf simply aep at4dx binding create -t service|selector|domain -n <value> -c <value> [--json] [--flags-dir <value>] [-d <value>]
71
+ [-o <value>] [--api-version <value>] [--wait <value>] [--label <value>] [--binding-interface <value>] [-s <value>]
72
+ [--sobject-alternate] [--priority <value>] [--force]
73
+
74
+ FLAGS
75
+ -c, --to=<value> (required) The interface/SObject's implementing Apex class (To__c).
76
+ -d, --source-dir=<value> The package directory to create the binding's .md-meta.xml under. Created if the
77
+ customMetadata folder doesn't exist yet.
78
+ -n, --developer-name=<value> (required) The binding's DeveloperName. Must start with a letter, contain only
79
+ letters, numbers, and single underscores, not end with an underscore, and be 40
80
+ characters or fewer.
81
+ -o, --target-org=<value> Deploy the generated binding to this org after writing it.
82
+ -s, --sobject=<value> The SObject API name to bind against (BindingSObject__c, or
83
+ BindingSObjectAlternate__c with --sobject-alternate). Required, and only allowed,
84
+ when --type is selector or domain.
85
+ -t, --type=<option> (required) Which Application Factory binding type to create: service, selector, or
86
+ domain.
87
+ <options: service|selector|domain>
88
+ --api-version=<value> Override the api version used for api requests made by this command
89
+ --binding-interface=<value> BindingInterface__c — the Apex interface this binding maps to. Required, and only
90
+ allowed, when --type is service.
91
+ --force Write (and deploy) even if validation finds an error-severity issue. Validation still
92
+ runs and its issues are still printed and returned.
93
+ --label=<value> The binding's label. Defaults to --developer-name. Must be 40 characters or fewer.
94
+ --priority=<value> Priority__c. Higher numbers are higher priority; omit for least priority. Only
95
+ allowed when --type is service or selector — Domain has no Priority__c field.
96
+ --[no-]sobject-alternate Write --sobject to BindingSObjectAlternate__c instead of BindingSObject__c. Use this
97
+ for a SObject that can't be referenced through an EntityDefinition field at all (for
98
+ example ServiceResource and other Setup objects). Only allowed when --type is
99
+ selector or domain.
100
+ --wait=<value> [default: 33] Deploy poll timeout, in minutes. Only meaningful with --target-org.
101
+
102
+ GLOBAL FLAGS
103
+ --flags-dir=<value> Import flag values from a directory.
104
+ --json Format output as json.
105
+
106
+ DESCRIPTION
107
+ Create a new AT4DX Application Factory binding (Service, Selector, or Domain) in local source and/or a connected org.
108
+
109
+ Generates a `<LocalObjectName>.<DeveloperName>.md-meta.xml` file from the given flags and writes it under
110
+ --source-dir, deploys it to --target-org, or both. Validates the resulting binding — alongside everything else of the
111
+ same --type already in scope — with the same rules `simply aep at4dx binding validate` uses, and refuses to write if
112
+ that introduces an error-severity issue unless --force is passed. At least one of --source-dir/--target-org is
113
+ required; both may be given at once (write to source and deploy it live in the same run). Given --target-org alone,
114
+ the file is written to a temporary directory, deployed, and discarded — no working-tree footprint.
115
+
116
+ `--type service` uses --binding-interface (BindingInterface__c) and rejects --sobject/--sobject-alternate; `--type
117
+ selector`/`domain` use --sobject and write it to BindingSObject__c by default (pass --sobject-alternate to write
118
+ BindingSObjectAlternate__c instead, for a SObject — such as ServiceResource and other Setup objects — that can't be
119
+ referenced through an EntityDefinition field at all). `--priority` is accepted for `--type service`/`selector` only;
120
+ Domain has no such field.
121
+
122
+ EXAMPLES
123
+ $ sf simply aep at4dx binding create --source-dir sfdx-source/core --type service --developer-name My_Service_Binding --binding-interface IMyService --to MyServiceImpl
124
+
125
+ $ sf simply aep at4dx binding create --target-org myOrg --type selector --developer-name Account_Selector --sobject Account --to AccountsSelector --priority 1
126
+
127
+ $ sf simply aep at4dx binding create --source-dir sfdx-source/core --type domain --developer-name Account_Domain --sobject Account --to AccountDomain
128
+
129
+ $ sf simply aep at4dx binding create --source-dir sfdx-source/core --type selector --developer-name ServiceResource_Selector --sobject ServiceResource --sobject-alternate --to ServiceResourceSelector
130
+ ```
131
+
132
+ _See code: [@simplysf/simply-aep](https://github.com/SimplySF/simply-node/blob/@simplysf/simply-aep@0.7.0/packages/simply-aep/lib/commands/simply/aep/at4dx/binding/create.js)_
133
+
57
134
  ## `sf simply aep at4dx binding list`
58
135
 
59
136
  List the AT4DX Application Factory bindings configured in an org or local source, resolved to show which record wins for each binding key.
@@ -108,7 +185,133 @@ FLAG DESCRIPTIONS
108
185
  Comma-separated list of binding types to include. If not specified, all four are included.
109
186
  ```
110
187
 
111
- _See code: [@simplysf/simply-aep](https://github.com/SimplySF/simply-node/blob/@simplysf/simply-aep@0.6.1/packages/simply-aep/lib/commands/simply/aep/at4dx/binding/list.js)_
188
+ _See code: [@simplysf/simply-aep](https://github.com/SimplySF/simply-node/blob/@simplysf/simply-aep@0.7.0/packages/simply-aep/lib/commands/simply/aep/at4dx/binding/list.js)_
189
+
190
+ ## `sf simply aep at4dx binding update`
191
+
192
+ Update an existing AT4DX Application Factory binding (Service, Selector, or Domain) in local source and/or a connected org.
193
+
194
+ ```
195
+ USAGE
196
+ $ sf simply aep at4dx binding update -t service|selector|domain -n <value> [--json] [--flags-dir <value>] [-d <value>...] [-o
197
+ <value>] [--api-version <value>] [--wait <value>] [--label <value>] [-c <value>] [--binding-interface <value>] [-s
198
+ <value>] [--sobject-alternate] [--priority <value>] [--force]
199
+
200
+ FLAGS
201
+ -c, --to=<value> The interface/SObject's implementing Apex class (To__c). If not given, the existing
202
+ value is kept.
203
+ -d, --source-dir=<value>... One or more paths to directories containing Salesforce DX source, searched for the
204
+ binding to update.
205
+ -n, --developer-name=<value> (required) The DeveloperName of the binding to update.
206
+ -o, --target-org=<value> Locate (when --source-dir isn't given) and/or deploy the binding to this org.
207
+ -s, --sobject=<value> The SObject API name to bind against. Only allowed when --type is selector or domain.
208
+ If not given, the existing value is kept.
209
+ -t, --type=<option> (required) Which Application Factory binding type to look in: service, selector, or
210
+ domain.
211
+ <options: service|selector|domain>
212
+ --api-version=<value> Override the api version used for api requests made by this command
213
+ --binding-interface=<value> BindingInterface__c — the Apex interface this binding maps to. Only allowed when
214
+ --type is service. If not given, the existing value is kept.
215
+ --force Write (and deploy) even if validation finds an error-severity issue. Validation still
216
+ runs and its issues are still printed and returned.
217
+ --label=<value> The binding's label. If not given, the existing label is kept.
218
+ --priority=<value> Priority__c. Only allowed when --type is service or selector — Domain has no
219
+ Priority__c field. If not given, the existing value is kept.
220
+ --[no-]sobject-alternate Write --sobject to BindingSObjectAlternate__c instead of BindingSObject__c, for a
221
+ SObject that can't be referenced through an EntityDefinition field at all (for
222
+ example ServiceResource and other Setup objects). Only allowed when --type is
223
+ selector or domain. If not given, the binding keeps whichever field it already uses —
224
+ this flag only needs to be passed to change it.
225
+ --wait=<value> [default: 33] Deploy poll timeout, in minutes. Only meaningful with --target-org.
226
+
227
+ GLOBAL FLAGS
228
+ --flags-dir=<value> Import flag values from a directory.
229
+ --json Format output as json.
230
+
231
+ DESCRIPTION
232
+ Update an existing AT4DX Application Factory binding (Service, Selector, or Domain) in local source and/or a connected
233
+ org.
234
+
235
+ Finds the binding named --developer-name (of the given --type) in local source and/or a connected org, applies only
236
+ the fields given as flags — everything else, including which SObject reference field a Selector/Domain binding uses,
237
+ is preserved from the found record — and rewrites its `.md-meta.xml` file. Validates the resulting binding — alongside
238
+ everything else of the same --type already in scope — with the same rules `simply aep at4dx binding validate` uses,
239
+ and refuses to write if that introduces an error-severity issue unless --force is passed.
240
+
241
+ When --source-dir is given, the binding is located there (searched across every directory given, same as
242
+ `list`/`validate`) and that exact file is rewritten; the found file is also deployed if --target-org is given. When
243
+ only --target-org is given, the binding is located and updated directly in the org via a temporary file, deployed,
244
+ then discarded — no working-tree footprint.
245
+
246
+ --developer-name identifies the binding to update and can't itself be changed by this command. --type identifies which
247
+ Application Factory Custom Metadata Type to look in and can't be changed either — bindings don't move between types.
248
+
249
+ EXAMPLES
250
+ $ sf simply aep at4dx binding update --source-dir sfdx-source/core --source-dir sfdx-source/app --type selector --developer-name Account_Selector --priority 5
251
+
252
+ $ sf simply aep at4dx binding update --target-org myOrg --type domain --developer-name Account_Domain --to AccountDomainV2
253
+ ```
254
+
255
+ _See code: [@simplysf/simply-aep](https://github.com/SimplySF/simply-node/blob/@simplysf/simply-aep@0.7.0/packages/simply-aep/lib/commands/simply/aep/at4dx/binding/update.js)_
256
+
257
+ ## `sf simply aep at4dx binding validate`
258
+
259
+ Validate the AT4DX Application Factory bindings configured in an org or local source, failing when a wiring problem is found.
260
+
261
+ ```
262
+ USAGE
263
+ $ sf simply aep at4dx binding validate [--json] [--flags-dir <value>] [-o <value>] [--api-version <value>] [-d <value>...] [-t
264
+ service|selector|domain|unit-of-work...]
265
+
266
+ FLAGS
267
+ -d, --source-dir=<value>... One or more paths to directories containing Salesforce DX source. Use this for
268
+ local-source discovery.
269
+ -o, --target-org=<value> Username or alias of the org to read bindings from. Use this for live-org discovery.
270
+ -t, --type=<option>... Binding type(s) to include: service, selector, domain, unit-of-work.
271
+ <options: service|selector|domain|unit-of-work>
272
+ --api-version=<value> Override the api version used for api requests made by this command
273
+
274
+ GLOBAL FLAGS
275
+ --flags-dir=<value> Import flag values from a directory.
276
+ --json Format output as json.
277
+
278
+ DESCRIPTION
279
+ Validate the AT4DX Application Factory bindings configured in an org or local source, failing when a wiring problem is
280
+ found.
281
+
282
+ Reads `ApplicationFactory_ServiceBinding__mdt`, `ApplicationFactory_SelectorBinding__mdt`, and
283
+ `ApplicationFactory_DomainBinding__mdt` — either from a live org or from local Salesforce DX source — and checks them
284
+ for problems `simply aep at4dx binding list` doesn't fail on: a binding with no resolvable key, a Selector/Domain
285
+ binding whose SObject reference is ambiguous or names a standard object that can't actually go through an
286
+ EntityDefinition metadata relationship, two records sharing a platform-unique `To__c`, two Domain records resolving to
287
+ the same SObject, and the same DeveloperName defined more than once within one binding type. Exactly one of
288
+ `--target-org` or `--source-dir` must be specified.
289
+
290
+ `ApplicationFactory_UnitOfWorkBinding__mdt` records are scanned when `--type` includes `unit-of-work` (to keep
291
+ `--type`'s meaning consistent with `binding list`) but never contribute an issue — every record contributes to one
292
+ ordered registration list with no possible wiring conflict.
293
+
294
+ Prints a table of every issue found. Exits non-zero when any issue is an error (a warning alone doesn't fail the
295
+ command) — use this in CI to gate on AT4DX Application Factory wiring problems before they reach an org.
296
+
297
+ EXAMPLES
298
+ $ sf simply aep at4dx binding validate --target-org myOrg
299
+
300
+ $ sf simply aep at4dx binding validate --source-dir sfdx-source/core --source-dir sfdx-source/app
301
+
302
+ $ sf simply aep at4dx binding validate --target-org myOrg --type service,selector
303
+
304
+ $ sf simply aep at4dx binding validate --target-org myOrg --json
305
+
306
+ FLAG DESCRIPTIONS
307
+ -t, --type=service|selector|domain|unit-of-work...
308
+
309
+ Binding type(s) to include: service, selector, domain, unit-of-work.
310
+
311
+ Comma-separated list of binding types to include. If not specified, all four are included.
312
+ ```
313
+
314
+ _See code: [@simplysf/simply-aep](https://github.com/SimplySF/simply-node/blob/@simplysf/simply-aep@0.7.0/packages/simply-aep/lib/commands/simply/aep/at4dx/binding/validate.js)_
112
315
 
113
316
  ## `sf simply aep at4dx domain-process-binding create`
114
317
 
@@ -189,7 +392,7 @@ EXAMPLES
189
392
  $ sf simply aep at4dx domain-process-binding create --source-dir sfdx-source/core --developer-name ServiceResource_Before_Update_Sync --sobject ServiceResource --sobject-alternate --process-context TriggerExecution --trigger-operation Before_Update --type Action --class-to-inject ServiceResourceSyncAction --order 10
190
393
  ```
191
394
 
192
- _See code: [@simplysf/simply-aep](https://github.com/SimplySF/simply-node/blob/@simplysf/simply-aep@0.6.1/packages/simply-aep/lib/commands/simply/aep/at4dx/domain-process-binding/create.js)_
395
+ _See code: [@simplysf/simply-aep](https://github.com/SimplySF/simply-node/blob/@simplysf/simply-aep@0.7.0/packages/simply-aep/lib/commands/simply/aep/at4dx/domain-process-binding/create.js)_
193
396
 
194
397
  ## `sf simply aep at4dx domain-process-binding list`
195
398
 
@@ -235,7 +438,7 @@ EXAMPLES
235
438
  $ sf simply aep at4dx domain-process-binding list --target-org myOrg --active-only --json
236
439
  ```
237
440
 
238
- _See code: [@simplysf/simply-aep](https://github.com/SimplySF/simply-node/blob/@simplysf/simply-aep@0.6.1/packages/simply-aep/lib/commands/simply/aep/at4dx/domain-process-binding/list.js)_
441
+ _See code: [@simplysf/simply-aep](https://github.com/SimplySF/simply-node/blob/@simplysf/simply-aep@0.7.0/packages/simply-aep/lib/commands/simply/aep/at4dx/domain-process-binding/list.js)_
239
442
 
240
443
  ## `sf simply aep at4dx domain-process-binding set`
241
444
 
@@ -314,7 +517,7 @@ EXAMPLES
314
517
  $ sf simply aep at4dx domain-process-binding set --target-org myOrg --developer-name Account_Before_Insert_Assign_Owner --class-to-inject AccountAssignOwnerActionV2
315
518
  ```
316
519
 
317
- _See code: [@simplysf/simply-aep](https://github.com/SimplySF/simply-node/blob/@simplysf/simply-aep@0.6.1/packages/simply-aep/lib/commands/simply/aep/at4dx/domain-process-binding/set.js)_
520
+ _See code: [@simplysf/simply-aep](https://github.com/SimplySF/simply-node/blob/@simplysf/simply-aep@0.7.0/packages/simply-aep/lib/commands/simply/aep/at4dx/domain-process-binding/set.js)_
318
521
 
319
522
  ## `sf simply aep at4dx domain-process-binding validate`
320
523
 
@@ -367,7 +570,204 @@ EXAMPLES
367
570
  $ sf simply aep at4dx domain-process-binding validate --target-org myOrg --json
368
571
  ```
369
572
 
370
- _See code: [@simplysf/simply-aep](https://github.com/SimplySF/simply-node/blob/@simplysf/simply-aep@0.6.1/packages/simply-aep/lib/commands/simply/aep/at4dx/domain-process-binding/validate.js)_
573
+ _See code: [@simplysf/simply-aep](https://github.com/SimplySF/simply-node/blob/@simplysf/simply-aep@0.7.0/packages/simply-aep/lib/commands/simply/aep/at4dx/domain-process-binding/validate.js)_
574
+
575
+ ## `sf simply aep at4dx field-set-inclusion create`
576
+
577
+ Create a new AT4DX Selector field set inclusion (SelectorConfig_FieldSetInclusion__mdt) in local source and/or a connected org.
578
+
579
+ ```
580
+ USAGE
581
+ $ sf simply aep at4dx field-set-inclusion create -n <value> -s <value> -f <value> [--json] [--flags-dir <value>] [-d <value>] [-o <value>]
582
+ [--api-version <value>] [--wait <value>] [--label <value>] [--sobject-alternate] [--active] [--force]
583
+
584
+ FLAGS
585
+ -d, --source-dir=<value> The package directory to create the field set inclusion's .md-meta.xml under. Created if
586
+ the customMetadata folder doesn't exist yet.
587
+ -f, --fieldset-name=<value> (required) FieldsetName__c — the field set to add to the selector's queried field list.
588
+ Unique org-wide across every SObject, not per-SObject.
589
+ -n, --developer-name=<value> (required) The record's DeveloperName. Must start with a letter, contain only letters,
590
+ numbers, and single underscores, not end with an underscore, and be 40 characters or
591
+ fewer.
592
+ -o, --target-org=<value> Deploy the generated field set inclusion to this org after writing it.
593
+ -s, --sobject=<value> (required) The SObject API name to bind the field set to (BindingSObject__c, or
594
+ BindingSObjectAlternate__c with --sobject-alternate).
595
+ --[no-]active IsActive__c. Defaults to true, matching the Custom Metadata Type's own default. Pass
596
+ --no-active to create it inactive.
597
+ --api-version=<value> Override the api version used for api requests made by this command
598
+ --force Write (and deploy) even if validation finds an error-severity issue. Validation still
599
+ runs and its issues are still printed and returned.
600
+ --label=<value> The record's label. Defaults to --developer-name. Must be 40 characters or fewer.
601
+ --[no-]sobject-alternate Write --sobject to BindingSObjectAlternate__c instead of BindingSObject__c. Use this for
602
+ a SObject that can't be referenced through an EntityDefinition field at all (for example
603
+ ServiceResource and other Setup objects).
604
+ --wait=<value> [default: 33] Deploy poll timeout, in minutes. Only meaningful with --target-org.
605
+
606
+ GLOBAL FLAGS
607
+ --flags-dir=<value> Import flag values from a directory.
608
+ --json Format output as json.
609
+
610
+ DESCRIPTION
611
+ Create a new AT4DX Selector field set inclusion (SelectorConfig_FieldSetInclusion__mdt) in local source and/or a
612
+ connected org.
613
+
614
+ Generates a `SelectorConfig_FieldSetInclusion.<DeveloperName>.md-meta.xml` file from the given flags and writes it
615
+ under --source-dir, deploys it to --target-org, or both. Validates the resulting record — alongside everything else
616
+ already in scope — with the same rules `simply aep at4dx field-set-inclusion validate` uses, and refuses to write if
617
+ that introduces an error-severity issue unless --force is passed. At least one of --source-dir/--target-org is
618
+ required; both may be given at once (write to source and deploy it live in the same run). Given --target-org alone,
619
+ the file is written to a temporary directory, deployed, and discarded — no working-tree footprint.
620
+
621
+ --sobject writes BindingSObject__c by default (pass --sobject-alternate to write BindingSObjectAlternate__c instead,
622
+ for a SObject — such as ServiceResource and other Setup objects — that can't be referenced through an EntityDefinition
623
+ field at all).
624
+
625
+ EXAMPLES
626
+ $ sf simply aep at4dx field-set-inclusion create --source-dir sfdx-source/core --developer-name Account_Contact_Fields --sobject Account --fieldset-name ContactRelatedFields
627
+
628
+ $ sf simply aep at4dx field-set-inclusion create --target-org myOrg --developer-name ServiceResource_Skills --sobject ServiceResource --sobject-alternate --fieldset-name SkillFields
629
+ ```
630
+
631
+ _See code: [@simplysf/simply-aep](https://github.com/SimplySF/simply-node/blob/@simplysf/simply-aep@0.7.0/packages/simply-aep/lib/commands/simply/aep/at4dx/field-set-inclusion/create.js)_
632
+
633
+ ## `sf simply aep at4dx field-set-inclusion list`
634
+
635
+ List the AT4DX Selector field set inclusions configured in an org or local source.
636
+
637
+ ```
638
+ USAGE
639
+ $ sf simply aep at4dx field-set-inclusion list [--json] [--flags-dir <value>] [-o <value>] [--api-version <value>] [-d
640
+ <value>...]
641
+
642
+ FLAGS
643
+ -d, --source-dir=<value>... One or more paths to directories containing Salesforce DX source. Use this for
644
+ local-source discovery.
645
+ -o, --target-org=<value> Username or alias of the org to read field set inclusions from. Use this for live-org
646
+ discovery.
647
+ --api-version=<value> Override the api version used for api requests made by this command
648
+
649
+ GLOBAL FLAGS
650
+ --flags-dir=<value> Import flag values from a directory.
651
+ --json Format output as json.
652
+
653
+ DESCRIPTION
654
+ List the AT4DX Selector field set inclusions configured in an org or local source.
655
+
656
+ Reads `SelectorConfig_FieldSetInclusion__mdt` — either from a live org or from local Salesforce DX source — and lists
657
+ every record found. Unlike `simply aep at4dx binding list`, there's no priority/winner concept: every `IsActive__c:
658
+ true` record for a selector's SObject contributes its field set simultaneously, so this is a flat table, not a
659
+ resolved one. Exactly one of `--target-org` or `--source-dir` must be specified.
660
+
661
+ EXAMPLES
662
+ $ sf simply aep at4dx field-set-inclusion list --target-org myOrg
663
+
664
+ $ sf simply aep at4dx field-set-inclusion list --source-dir sfdx-source/core --source-dir sfdx-source/app
665
+
666
+ $ sf simply aep at4dx field-set-inclusion list --target-org myOrg --json
667
+ ```
668
+
669
+ _See code: [@simplysf/simply-aep](https://github.com/SimplySF/simply-node/blob/@simplysf/simply-aep@0.7.0/packages/simply-aep/lib/commands/simply/aep/at4dx/field-set-inclusion/list.js)_
670
+
671
+ ## `sf simply aep at4dx field-set-inclusion update`
672
+
673
+ Update an existing AT4DX Selector field set inclusion (SelectorConfig_FieldSetInclusion__mdt) in local source and/or a connected org.
674
+
675
+ ```
676
+ USAGE
677
+ $ sf simply aep at4dx field-set-inclusion update -n <value> [--json] [--flags-dir <value>] [-d <value>...] [-o <value>] [--api-version <value>]
678
+ [--wait <value>] [--label <value>] [-s <value>] [--sobject-alternate] [-f <value>] [--active] [--force]
679
+
680
+ FLAGS
681
+ -d, --source-dir=<value>... One or more paths to directories containing Salesforce DX source, searched for the
682
+ record to update.
683
+ -f, --fieldset-name=<value> FieldsetName__c — the field set to add to the selector's queried field list. Changing it
684
+ changes which field set is included. If not given, the existing value is kept.
685
+ -n, --developer-name=<value> (required) The DeveloperName of the record to update.
686
+ -o, --target-org=<value> Locate (when --source-dir isn't given) and/or deploy the record to this org.
687
+ -s, --sobject=<value> The SObject API name to bind the field set to. If not given, the existing value is kept.
688
+ --[no-]active IsActive__c. If not given, the existing value is kept. Pass --no-active to deactivate.
689
+ --api-version=<value> Override the api version used for api requests made by this command
690
+ --force Write (and deploy) even if validation finds an error-severity issue. Validation still
691
+ runs and its issues are still printed and returned.
692
+ --label=<value> The record's label. If not given, the existing label is kept.
693
+ --[no-]sobject-alternate Write --sobject to BindingSObjectAlternate__c instead of BindingSObject__c, for a
694
+ SObject that can't be referenced through an EntityDefinition field at all (for example
695
+ ServiceResource and other Setup objects). If not given, the record keeps whichever field
696
+ it already uses — this flag only needs to be passed to change it.
697
+ --wait=<value> [default: 33] Deploy poll timeout, in minutes. Only meaningful with --target-org.
698
+
699
+ GLOBAL FLAGS
700
+ --flags-dir=<value> Import flag values from a directory.
701
+ --json Format output as json.
702
+
703
+ DESCRIPTION
704
+ Update an existing AT4DX Selector field set inclusion (SelectorConfig_FieldSetInclusion__mdt) in local source and/or a
705
+ connected org.
706
+
707
+ Finds the field set inclusion named --developer-name in local source and/or a connected org, applies only the fields
708
+ given as flags — everything else, including which SObject reference field it uses, is preserved from the found record
709
+ — and rewrites its `.md-meta.xml` file. Validates the resulting record — alongside everything else already in scope —
710
+ with the same rules `simply aep at4dx field-set-inclusion validate` uses, and refuses to write if that introduces an
711
+ error-severity issue unless --force is passed.
712
+
713
+ When --source-dir is given, the record is located there (searched across every directory given, same as
714
+ `list`/`validate`) and that exact file is rewritten; the found file is also deployed if --target-org is given. When
715
+ only --target-org is given, the record is located and updated directly in the org via a temporary file, deployed, then
716
+ discarded — no working-tree footprint.
717
+
718
+ --developer-name identifies the record to update and can't itself be changed by this command.
719
+
720
+ EXAMPLES
721
+ $ sf simply aep at4dx field-set-inclusion update --source-dir sfdx-source/core --source-dir sfdx-source/app --developer-name Account_Contact_Fields --no-active
722
+
723
+ $ sf simply aep at4dx field-set-inclusion update --target-org myOrg --developer-name Account_Contact_Fields --fieldset-name ContactRelatedFieldsV2
724
+ ```
725
+
726
+ _See code: [@simplysf/simply-aep](https://github.com/SimplySF/simply-node/blob/@simplysf/simply-aep@0.7.0/packages/simply-aep/lib/commands/simply/aep/at4dx/field-set-inclusion/update.js)_
727
+
728
+ ## `sf simply aep at4dx field-set-inclusion validate`
729
+
730
+ Validate the AT4DX Selector field set inclusions configured in an org or local source, failing when a wiring problem is found.
731
+
732
+ ```
733
+ USAGE
734
+ $ sf simply aep at4dx field-set-inclusion validate [--json] [--flags-dir <value>] [-o <value>] [--api-version <value>]
735
+ [-d <value>...]
736
+
737
+ FLAGS
738
+ -d, --source-dir=<value>... One or more paths to directories containing Salesforce DX source. Use this for
739
+ local-source discovery.
740
+ -o, --target-org=<value> Username or alias of the org to read field set inclusions from. Use this for live-org
741
+ discovery.
742
+ --api-version=<value> Override the api version used for api requests made by this command
743
+
744
+ GLOBAL FLAGS
745
+ --flags-dir=<value> Import flag values from a directory.
746
+ --json Format output as json.
747
+
748
+ DESCRIPTION
749
+ Validate the AT4DX Selector field set inclusions configured in an org or local source, failing when a wiring problem
750
+ is found.
751
+
752
+ Reads `SelectorConfig_FieldSetInclusion__mdt` — either from a live org or from local Salesforce DX source — and checks
753
+ them for problems `simply aep at4dx field-set-inclusion list` doesn't fail on: a record with no resolvable SObject, an
754
+ ambiguous SObject reference, a SObject reference naming a standard object that can't actually go through an
755
+ EntityDefinition metadata relationship, two records sharing a FieldsetName__c value (unique org-wide, not
756
+ per-SObject), and the same DeveloperName defined more than once. Exactly one of `--target-org` or `--source-dir` must
757
+ be specified.
758
+
759
+ Prints a table of every issue found. Exits non-zero when any issue is an error (a warning alone doesn't fail the
760
+ command) — use this in CI to gate on AT4DX field set inclusion wiring problems before they reach an org.
761
+
762
+ EXAMPLES
763
+ $ sf simply aep at4dx field-set-inclusion validate --target-org myOrg
764
+
765
+ $ sf simply aep at4dx field-set-inclusion validate --source-dir sfdx-source/core --source-dir sfdx-source/app
766
+
767
+ $ sf simply aep at4dx field-set-inclusion validate --target-org myOrg --json
768
+ ```
769
+
770
+ _See code: [@simplysf/simply-aep](https://github.com/SimplySF/simply-node/blob/@simplysf/simply-aep@0.7.0/packages/simply-aep/lib/commands/simply/aep/at4dx/field-set-inclusion/validate.js)_
371
771
 
372
772
  ## `sf simply apex execute`
373
773
 
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@simplysf/simply",
3
3
  "description": "Salesforce CLI Plugins created by @SimplySF",
4
- "version": "3.5.0",
4
+ "version": "4.1.0",
5
5
  "author": "@ClayChipps",
6
6
  "homepage": "https://github.com/SimplySF/simply-node",
7
7
  "bugs": "https://github.com/SimplySF/simply-node/issues",
@@ -75,7 +75,7 @@
75
75
  },
76
76
  "dependencies": {
77
77
  "@oclif/core": "^4.11.2",
78
- "@simplysf/simply-aep": "^0.7.0",
78
+ "@simplysf/simply-aep": "^0.9.0",
79
79
  "@simplysf/simply-apex": "^1.6.6",
80
80
  "@simplysf/simply-community": "^0.6.2",
81
81
  "@simplysf/simply-data": "^2.4.1",
@@ -184,5 +184,5 @@
184
184
  "output": []
185
185
  }
186
186
  },
187
- "gitHead": "d2a9919f27df257491f324840fcfbbaa3a3a56c0"
187
+ "gitHead": "b1b42d6f0d817ae31c9c9580bc7914182d9e8361"
188
188
  }