ampscript-data 3.6.0 → 3.7.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/package.json +1 -1
  2. package/src/index.js +438 -61
package/src/index.js CHANGED
@@ -23,6 +23,18 @@
23
23
  * difference.
24
24
  * - officialDocsNote?: string — human-readable evidence: what the official docs claim, what
25
25
  * the runtime actually did, and what was tried.
26
+ * - supportedInCloudPage?: boolean — RUNTIME-PROVEN runtime-context flag (orthogonal to the
27
+ * Engagement/Next PLATFORM flags mcnSince/mcnNotes). true when a live CloudPage/landing-page
28
+ * probe rendered the function successfully; false when the function was actually probed in a
29
+ * CloudPage context and proven NOT to work there (the reached call aborts the page, or the
30
+ * parser refuses it). ABSENT means the function was never probed in that context — absence
31
+ * MUST NOT be read as unsupported. Never defaults to false.
32
+ * - supportedInEmail?: boolean — same semantics for the email/send context: true when a live
33
+ * email/send probe rendered/evaluated the function successfully (a data/connector/asset gate
34
+ * that still lets the function itself run counts as supported); false when the send-content
35
+ * parser proved it does not work there (rejected as not valid in sendable content, or the
36
+ * engine does not recognise it). ABSENT means never probed — not unsupported. Never defaults
37
+ * to false.
26
38
  */
27
39
 
28
40
  const INF = Infinity;
@@ -92,10 +104,12 @@ export const VERIFICATION_BLOCKED_REASONS = Object.freeze([
92
104
  * for a human to finish the rewrite rather than a mechanical substitution. Must be present
93
105
  * whenever `handlebarsEquivalent` is non-null.
94
106
  *
95
- @type {{name: string, mcnSince: number | null, mcnNotes: string | null, handlebarsEquivalent?: string | null, handlebarsExact?: boolean, docUrl?: string, guideUrl?: string, sfmcGuideUrl?: string, minArgs: number, maxArgs: number, validArities?: number[], category: string, description: string, params: {name: string, description: string, type?: string, enum?: (string | number)[], optional?: boolean, default?: string | number | boolean}[], returnType?: string, returnDescription?: string, returnEnum?: (string | number)[], syntax?: string, example?: string, repeat?: {startIndex: number, groupSize: number, minGroups: number, countParam?: string}[], deprecated?: boolean, deprecatedReplacement?: string, deprecatedReason?: string, isConfirmed?: boolean, verificationBlocked?: boolean, verificationBlockedReason?: string, differsFromOfficialDocs?: boolean, officialDocsNote?: string}[]} */
107
+ @type {{name: string, mcnSince: number | null, mcnNotes: string | null, handlebarsEquivalent?: string | null, handlebarsExact?: boolean, docUrl?: string, guideUrl?: string, sfmcGuideUrl?: string, minArgs: number, maxArgs: number, validArities?: number[], category: string, description: string, params: {name: string, description: string, type?: string, enum?: (string | number)[], optional?: boolean, default?: string | number | boolean}[], returnType?: string, returnDescription?: string, returnEnum?: (string | number)[], syntax?: string, example?: string, repeat?: {startIndex: number, groupSize: number, minGroups: number, countParam?: string}[], deprecated?: boolean, deprecatedReplacement?: string, deprecatedReason?: string, isConfirmed?: boolean, verificationBlocked?: boolean, verificationBlockedReason?: string, differsFromOfficialDocs?: boolean, officialDocsNote?: string, supportedInCloudPage?: boolean, supportedInEmail?: boolean}[]} */
96
108
  export const FUNCTIONS = [
97
109
  {
98
110
  name: 'Add',
111
+ supportedInCloudPage: true,
112
+ supportedInEmail: true,
99
113
  mcnSince: 67,
100
114
  handlebarsEquivalent: 'add',
101
115
  handlebarsExact: true,
@@ -120,6 +134,8 @@ export const FUNCTIONS = [
120
134
  },
121
135
  {
122
136
  name: 'AddMscrmListMember',
137
+ supportedInCloudPage: false,
138
+ supportedInEmail: false,
123
139
  mcnSince: null,
124
140
  handlebarsEquivalent: null,
125
141
  mcnNotes: null,
@@ -158,6 +174,8 @@ export const FUNCTIONS = [
158
174
  },
159
175
  {
160
176
  name: 'AddObjectArrayItem',
177
+ supportedInCloudPage: true,
178
+ supportedInEmail: false,
161
179
  mcnSince: null,
162
180
  handlebarsEquivalent: null,
163
181
  mcnNotes: null,
@@ -179,9 +197,14 @@ export const FUNCTIONS = [
179
197
  syntax: 'AddObjectArrayItem(apiObject, arrayProperty, itemToAdd)',
180
198
  example: "AddObjectArrayItem(@apiObject, 'Recipients', @recipient)",
181
199
  isConfirmed: true,
200
+ differsFromOfficialDocs: true,
201
+ officialDocsNote:
202
+ 'Email/send-context finding: the WSProxy object model is not valid in sendable email content. Rendered through the Email Preview API against a seeded sendable row, an isolated CreateObject(...) was rejected with HTTP 400 errorcode 10004 ("CreateObject Function is not valid in content. This function is only allowed in non sendable content."). Because this function is part of that object model (or depends on a CreateObject request object), it is a CloudPage / landing-page (non-sendable content) feature and cannot be used inside a sendable email.',
182
203
  },
183
204
  {
184
205
  name: 'AttachFile',
206
+ supportedInCloudPage: false,
207
+ supportedInEmail: false,
185
208
  mcnSince: null,
186
209
  handlebarsEquivalent: null,
187
210
  mcnNotes: null,
@@ -256,10 +279,12 @@ export const FUNCTIONS = [
256
279
  verificationBlocked: true,
257
280
  verificationBlockedReason: 'no-working-invocation',
258
281
  officialDocsNote:
259
- 'AttachFile targets the outgoing email at send time; it has no working invocation on a CloudPage. Every reached call — contentbuilder key, http URL, and the two-argument minimum form — aborted the page with HTTP 422 and no partial output, on the child QA BU (MID 518005426) and again on the parent BU (MID 7281698). The abort only happens when the call is actually reached: gating it behind an unmatched query-string branch leaves the page at HTTP 200, so the failure is a runtime abort of the reached call rather than a compile-time rejection. The official reference additionally documents that the capability must be provisioned per account, which cannot be observed from a full-access probe.',
282
+ 'AttachFile targets the outgoing email at send time; it has no working invocation on a CloudPage. Every reached call — contentbuilder key, http URL, and the two-argument minimum form — aborted the page with HTTP 422 and no partial output, on the child BU and again on the parent BU. The abort only happens when the call is actually reached: gating it behind an unmatched query-string branch leaves the page at HTTP 200, so the failure is a runtime abort of the reached call rather than a compile-time rejection. An email-context render on the child BU sharpened the cause: the Email Preview API recognises and evaluates the function and fails with a precise message that the EMAIL_ATTACHMENTS business rule must be turned on before AttachFile can be used, so the block is an account-level provisioning gate rather than a broken function.',
260
283
  },
261
284
  {
262
285
  name: 'AttributeValue',
286
+ supportedInCloudPage: true,
287
+ supportedInEmail: true,
263
288
  mcnSince: null,
264
289
  handlebarsEquivalent: 'personalizationResult',
265
290
  handlebarsExact: false,
@@ -290,6 +315,8 @@ export const FUNCTIONS = [
290
315
  },
291
316
  {
292
317
  name: 'AuthenticatedEmployeeID',
318
+ supportedInCloudPage: true,
319
+ supportedInEmail: true,
293
320
  mcnSince: null,
294
321
  handlebarsEquivalent: null,
295
322
  mcnNotes: null,
@@ -312,6 +339,8 @@ export const FUNCTIONS = [
312
339
  },
313
340
  {
314
341
  name: 'AuthenticatedEmployeeNotificationAddress',
342
+ supportedInCloudPage: true,
343
+ supportedInEmail: true,
315
344
  mcnSince: null,
316
345
  handlebarsEquivalent: null,
317
346
  mcnNotes: null,
@@ -329,7 +358,7 @@ export const FUNCTIONS = [
329
358
  isConfirmed: true,
330
359
  differsFromOfficialDocs: true,
331
360
  officialDocsNote:
332
- 'Proven on the child BU MCDEV_Training_QA (MID 518005426); the parent BU was not needed. The official reference scopes the function to microsites that use sender authenticated redirection and explicitly says it is not for use with CloudPages. At runtime the opposite happened: an anonymous GET of a public CloudPage rendered at HTTP 200 and the call returned a well-formed, non-empty notification email address — Empty() answered false, Length() reported 29 characters and IsEmailAddress() accepted it. The value behaved as an ordinary string when used inline, nested inside Concat and compared against the empty string. The literal address is redacted here because it identifies an account user; only its shape is described.',
361
+ 'Proven on the child BU; the parent BU was not needed. The official reference scopes the function to microsites that use sender authenticated redirection and explicitly says it is not for use with CloudPages. At runtime the opposite happened: an anonymous GET of a public CloudPage rendered at HTTP 200 and the call returned a well-formed, non-empty notification email address — Empty() answered false, Length() reported 29 characters and IsEmailAddress() accepted it. The value behaved as an ordinary string when used inline, nested inside Concat and compared against the empty string. The literal address is redacted here because it identifies an account user; only its shape is described.',
333
362
  sfmcGuideUrl:
334
363
  'https://sfmc.guide/engagement/ampscript/functions/authenticatedemployeenotificationaddress/',
335
364
  syntax: 'AuthenticatedEmployeeNotificationAddress()',
@@ -337,6 +366,8 @@ export const FUNCTIONS = [
337
366
  },
338
367
  {
339
368
  name: 'AuthenticatedEmployeeUserName',
369
+ supportedInCloudPage: true,
370
+ supportedInEmail: true,
340
371
  mcnSince: null,
341
372
  handlebarsEquivalent: null,
342
373
  mcnNotes: null,
@@ -360,6 +391,8 @@ export const FUNCTIONS = [
360
391
  },
361
392
  {
362
393
  name: 'AuthenticatedEnterpriseID',
394
+ supportedInCloudPage: true,
395
+ supportedInEmail: true,
363
396
  mcnSince: null,
364
397
  handlebarsEquivalent: null,
365
398
  mcnNotes: null,
@@ -383,6 +416,8 @@ export const FUNCTIONS = [
383
416
  },
384
417
  {
385
418
  name: 'AuthenticatedMemberID',
419
+ supportedInCloudPage: true,
420
+ supportedInEmail: true,
386
421
  mcnSince: null,
387
422
  handlebarsEquivalent: null,
388
423
  mcnNotes: null,
@@ -405,6 +440,8 @@ export const FUNCTIONS = [
405
440
  },
406
441
  {
407
442
  name: 'AuthenticatedMemberName',
443
+ supportedInCloudPage: true,
444
+ supportedInEmail: true,
408
445
  mcnSince: null,
409
446
  handlebarsEquivalent: null,
410
447
  mcnNotes: null,
@@ -427,6 +464,8 @@ export const FUNCTIONS = [
427
464
  },
428
465
  {
429
466
  name: 'BarcodeURL',
467
+ supportedInCloudPage: true,
468
+ supportedInEmail: true,
430
469
  mcnSince: null,
431
470
  handlebarsEquivalent: null,
432
471
  mcnNotes: null,
@@ -515,6 +554,8 @@ export const FUNCTIONS = [
515
554
  },
516
555
  {
517
556
  name: 'Base64Decode',
557
+ supportedInCloudPage: true,
558
+ supportedInEmail: true,
518
559
  mcnSince: null,
519
560
  handlebarsEquivalent: null,
520
561
  mcnNotes: null,
@@ -560,6 +601,8 @@ export const FUNCTIONS = [
560
601
  },
561
602
  {
562
603
  name: 'Base64Encode',
604
+ supportedInCloudPage: true,
605
+ supportedInEmail: true,
563
606
  mcnSince: null,
564
607
  handlebarsEquivalent: null,
565
608
  mcnNotes: null,
@@ -596,6 +639,8 @@ export const FUNCTIONS = [
596
639
  },
597
640
  {
598
641
  name: 'BeginImpressionRegion',
642
+ supportedInCloudPage: true,
643
+ supportedInEmail: true,
599
644
  mcnSince: null,
600
645
  handlebarsEquivalent: null,
601
646
  mcnNotes: null,
@@ -617,6 +662,8 @@ export const FUNCTIONS = [
617
662
  },
618
663
  {
619
664
  name: 'BuildOptionList',
665
+ supportedInCloudPage: true,
666
+ supportedInEmail: true,
620
667
  mcnSince: null,
621
668
  handlebarsEquivalent: null,
622
669
  mcnNotes: null,
@@ -677,6 +724,8 @@ export const FUNCTIONS = [
677
724
  },
678
725
  {
679
726
  name: 'BuildRowsetFromJSON',
727
+ supportedInCloudPage: true,
728
+ supportedInEmail: true,
680
729
  mcnSince: 67,
681
730
  handlebarsEquivalent: 'jsonPath',
682
731
  handlebarsExact: false,
@@ -718,10 +767,12 @@ export const FUNCTIONS = [
718
767
  isConfirmed: true,
719
768
  differsFromOfficialDocs: true,
720
769
  officialDocsNote:
721
- 'The official syntax section states that a false third argument yields an empty rowset and a true one raises an exception; runtime on the child BU (MID 518005426, CloudPage GET) does the opposite. Malformed JSON with 1 rendered a rowset of zero rows, while the identical payload with 0 aborted the page with HTTP 422. The same page also proved that an unparsable payload, an unset variable, an empty string, [] and a path matching nothing all yield zero rows when 1 is passed. Note the official Errors section already describes the runtime ordering, so the page contradicts itself.',
770
+ 'The official syntax section states that a false third argument yields an empty rowset and a true one raises an exception; runtime on the child BU (CloudPage GET) does the opposite. Malformed JSON with 1 rendered a rowset of zero rows, while the identical payload with 0 aborted the page with HTTP 422. The same page also proved that an unparsable payload, an unset variable, an empty string, [] and a path matching nothing all yield zero rows when 1 is passed. Note the official Errors section already describes the runtime ordering, so the page contradicts itself.',
722
771
  },
723
772
  {
724
773
  name: 'BuildRowSetFromString',
774
+ supportedInCloudPage: true,
775
+ supportedInEmail: true,
725
776
  mcnSince: null,
726
777
  handlebarsEquivalent: null,
727
778
  mcnNotes: null,
@@ -755,6 +806,8 @@ export const FUNCTIONS = [
755
806
  },
756
807
  {
757
808
  name: 'BuildRowSetFromXML',
809
+ supportedInCloudPage: true,
810
+ supportedInEmail: true,
758
811
  mcnSince: null,
759
812
  handlebarsEquivalent: null,
760
813
  mcnNotes: null,
@@ -789,10 +842,12 @@ export const FUNCTIONS = [
789
842
  isConfirmed: true,
790
843
  differsFromOfficialDocs: true,
791
844
  officialDocsNote:
792
- 'The official syntax section states that a false third argument yields an empty rowset and a true one raises an exception; runtime on the child BU (MID 518005426, CloudPage GET) behaves the other way round. Unclosed XML parsed with 1 rendered a rowset of zero rows, whereas the identical payload with 0 aborted the page with HTTP 422. An empty string, an unset variable, an empty root element and an XPath matching nothing likewise gave zero rows under 1.',
845
+ 'The official syntax section states that a false third argument yields an empty rowset and a true one raises an exception; runtime on the child BU (CloudPage GET) behaves the other way round. Unclosed XML parsed with 1 rendered a rowset of zero rows, whereas the identical payload with 0 aborted the page with HTTP 422. An empty string, an unset variable, an empty root element and an XPath matching nothing likewise gave zero rows under 1.',
793
846
  },
794
847
  {
795
848
  name: 'Char',
849
+ supportedInCloudPage: true,
850
+ supportedInEmail: true,
796
851
  mcnSince: null,
797
852
  handlebarsEquivalent: 'char',
798
853
  handlebarsExact: true,
@@ -830,6 +885,8 @@ export const FUNCTIONS = [
830
885
  },
831
886
  {
832
887
  name: 'ClaimRow',
888
+ supportedInCloudPage: true,
889
+ supportedInEmail: true,
833
890
  mcnSince: null,
834
891
  handlebarsEquivalent: null,
835
892
  mcnNotes: null,
@@ -895,10 +952,12 @@ export const FUNCTIONS = [
895
952
  isConfirmed: true,
896
953
  differsFromOfficialDocs: true,
897
954
  officialDocsNote:
898
- 'Runtime-proven on a Marketing Cloud Engagement CloudPage (child BU MID 518005426) against a data extension built to the documented claimable schema (Text primary key, Text claimant column, required non-nullable Boolean claim column defaulting to False, nullable Date column). Each call passing a NEW claimant value claims the next unclaimed row and advances: four distinct claimants received C1, C2, C3, C4 in order, each row flipping to claimed with its claimant recorded and ClaimedDate auto-populated. Re-calling with a claimant value that already holds a row returns that same row rather than advancing (per-subscriber idempotency). The official reference states that ClaimRow returns an exception when no unclaimed rows remain; at runtime it instead returned an empty row that does not abort the page (Empty() on it is true), so a caller must guard with Empty() rather than expecting a raised error. Each claim was driven by a separate HTTP request carrying the claimant value as a RequestParameter — the prior single-render probe that reused one claimant value never advanced because of the idempotency rule, not a provisioning gap.',
955
+ 'Runtime-proven on a Marketing Cloud Engagement CloudPage (child BU) against a data extension built to the documented claimable schema (Text primary key, Text claimant column, required non-nullable Boolean claim column defaulting to False, nullable Date column). Each call passing a NEW claimant value claims the next unclaimed row and advances: four distinct claimants received C1, C2, C3, C4 in order, each row flipping to claimed with its claimant recorded and ClaimedDate auto-populated. Re-calling with a claimant value that already holds a row returns that same row rather than advancing (per-subscriber idempotency). The official reference states that ClaimRow returns an exception when no unclaimed rows remain; at runtime it instead returned an empty row that does not abort the page (Empty() on it is true), so a caller must guard with Empty() rather than expecting a raised error. Each claim was driven by a separate HTTP request carrying the claimant value as a RequestParameter — the prior single-render probe that reused one claimant value never advanced because of the idempotency rule, not a provisioning gap.',
899
956
  },
900
957
  {
901
958
  name: 'ClaimRowValue',
959
+ supportedInCloudPage: true,
960
+ supportedInEmail: true,
902
961
  mcnSince: null,
903
962
  handlebarsEquivalent: null,
904
963
  mcnNotes: null,
@@ -982,6 +1041,8 @@ export const FUNCTIONS = [
982
1041
  },
983
1042
  {
984
1043
  name: 'CloudPagesURL',
1044
+ supportedInCloudPage: true,
1045
+ supportedInEmail: true,
985
1046
  mcnSince: null,
986
1047
  handlebarsEquivalent: null,
987
1048
  mcnNotes: null,
@@ -1035,6 +1096,8 @@ export const FUNCTIONS = [
1035
1096
  },
1036
1097
  {
1037
1098
  name: 'Concat',
1099
+ supportedInCloudPage: true,
1100
+ supportedInEmail: true,
1038
1101
  mcnSince: 67,
1039
1102
  handlebarsEquivalent: 'concat',
1040
1103
  handlebarsExact: true,
@@ -1071,6 +1134,8 @@ export const FUNCTIONS = [
1071
1134
  },
1072
1135
  {
1073
1136
  name: 'ContentArea',
1137
+ supportedInCloudPage: true,
1138
+ supportedInEmail: true,
1074
1139
  mcnSince: null,
1075
1140
  handlebarsEquivalent: null,
1076
1141
  mcnNotes: null,
@@ -1139,6 +1204,8 @@ export const FUNCTIONS = [
1139
1204
  },
1140
1205
  {
1141
1206
  name: 'ContentAreaByName',
1207
+ supportedInCloudPage: true,
1208
+ supportedInEmail: true,
1142
1209
  mcnSince: null,
1143
1210
  handlebarsEquivalent: null,
1144
1211
  mcnNotes: null,
@@ -1205,6 +1272,8 @@ export const FUNCTIONS = [
1205
1272
  },
1206
1273
  {
1207
1274
  name: 'ContentBlockByID',
1275
+ supportedInCloudPage: true,
1276
+ supportedInEmail: true,
1208
1277
  mcnSince: 67,
1209
1278
  handlebarsEquivalent: null,
1210
1279
  mcnNotes: null,
@@ -1268,6 +1337,8 @@ export const FUNCTIONS = [
1268
1337
  },
1269
1338
  {
1270
1339
  name: 'ContentBlockByKey',
1340
+ supportedInCloudPage: true,
1341
+ supportedInEmail: true,
1271
1342
  mcnSince: 67,
1272
1343
  handlebarsEquivalent: 'getContentBlock',
1273
1344
  handlebarsExact: false,
@@ -1332,6 +1403,8 @@ export const FUNCTIONS = [
1332
1403
  },
1333
1404
  {
1334
1405
  name: 'ContentBlockByName',
1406
+ supportedInCloudPage: true,
1407
+ supportedInEmail: true,
1335
1408
  mcnSince: 67,
1336
1409
  handlebarsEquivalent: null,
1337
1410
  mcnNotes: null,
@@ -1396,6 +1469,8 @@ export const FUNCTIONS = [
1396
1469
  },
1397
1470
  {
1398
1471
  name: 'ContentImageByID',
1472
+ supportedInCloudPage: true,
1473
+ supportedInEmail: true,
1399
1474
  mcnSince: null,
1400
1475
  handlebarsEquivalent: null,
1401
1476
  mcnNotes: null,
@@ -1433,6 +1508,8 @@ export const FUNCTIONS = [
1433
1508
  },
1434
1509
  {
1435
1510
  name: 'ContentImageByKey',
1511
+ supportedInCloudPage: true,
1512
+ supportedInEmail: true,
1436
1513
  mcnSince: null,
1437
1514
  handlebarsEquivalent: null,
1438
1515
  mcnNotes: null,
@@ -1469,6 +1546,8 @@ export const FUNCTIONS = [
1469
1546
  },
1470
1547
  {
1471
1548
  name: 'CreateMSCRMRecord',
1549
+ supportedInCloudPage: false,
1550
+ supportedInEmail: false,
1472
1551
  mcnSince: null,
1473
1552
  handlebarsEquivalent: null,
1474
1553
  mcnNotes: null,
@@ -1521,6 +1600,8 @@ export const FUNCTIONS = [
1521
1600
  },
1522
1601
  {
1523
1602
  name: 'CreateObject',
1603
+ supportedInCloudPage: true,
1604
+ supportedInEmail: false,
1524
1605
  mcnSince: null,
1525
1606
  handlebarsEquivalent: null,
1526
1607
  mcnNotes: null,
@@ -1540,9 +1621,14 @@ export const FUNCTIONS = [
1540
1621
  syntax: 'CreateObject(objectName)',
1541
1622
  example: "%%=CreateObject('DataExtensionObject')=%%",
1542
1623
  isConfirmed: true,
1624
+ differsFromOfficialDocs: true,
1625
+ officialDocsNote:
1626
+ 'Email/send-context finding: the WSProxy object model is not valid in sendable email content. Rendered through the Email Preview API against a seeded sendable row, an isolated CreateObject(...) was rejected with HTTP 400 errorcode 10004 ("CreateObject Function is not valid in content. This function is only allowed in non sendable content."). Because this function is part of that object model (or depends on a CreateObject request object), it is a CloudPage / landing-page (non-sendable content) feature and cannot be used inside a sendable email.',
1543
1627
  },
1544
1628
  {
1545
1629
  name: 'CreateSalesforceObject',
1630
+ supportedInCloudPage: true,
1631
+ supportedInEmail: true,
1546
1632
  mcnSince: null,
1547
1633
  handlebarsEquivalent: null,
1548
1634
  mcnNotes: null,
@@ -1557,7 +1643,7 @@ export const FUNCTIONS = [
1557
1643
  isConfirmed: true,
1558
1644
  differsFromOfficialDocs: false,
1559
1645
  officialDocsNote:
1560
- 'The success path was runtime-proven on cred/DEV (MID 510007949), which has an active Marketing Cloud Connect integration to a real Salesforce org. Creating a benign Task with a single opaque field returned a real 18-character Salesforce ID (an 00T-prefixed Task ID), confirming the documented return shape. The fault path was also proven: an unknown object name and an unknown field name on a real object each aborted the CloudPage with HTTP 422 — the SOAP fault from the connected org propagates as an uncatchable page abort (AMPscript has no try/catch), exactly like RetrieveSalesforceObjects against an unknown object — so there is no testable error value, the function either returns an ID or aborts. AMPscript has no delete function for Salesforce objects, so the created Task remains as benign residue in the org. Catalog signature, returnType and repeat group all match the official reference and ampscript.guide, so differsFromOfficialDocs stays false.',
1646
+ 'The success path was runtime-proven on the child BU, which has an active Marketing Cloud Connect integration to a real Salesforce org. Creating a benign Task with a single opaque field returned a real 18-character Salesforce ID (an 00T-prefixed Task ID), confirming the documented return shape. The fault path was also proven: an unknown object name and an unknown field name on a real object each aborted the CloudPage with HTTP 422 — the SOAP fault from the connected org propagates as an uncatchable page abort (AMPscript has no try/catch), exactly like RetrieveSalesforceObjects against an unknown object — so there is no testable error value, the function either returns an ID or aborts. AMPscript has no delete function for Salesforce objects, so the created Task remains as benign residue in the org. Catalog signature, returnType and repeat group all match the official reference and ampscript.guide, so differsFromOfficialDocs stays false.',
1561
1647
  params: [
1562
1648
  {
1563
1649
  name: 'objectName',
@@ -1594,6 +1680,8 @@ export const FUNCTIONS = [
1594
1680
  },
1595
1681
  {
1596
1682
  name: 'CreateSmsConversation',
1683
+ supportedInCloudPage: true,
1684
+ supportedInEmail: true,
1597
1685
  mcnSince: null,
1598
1686
  handlebarsEquivalent: null,
1599
1687
  mcnNotes: null,
@@ -1604,12 +1692,10 @@ export const FUNCTIONS = [
1604
1692
  category: 'MobileConnect',
1605
1693
  description:
1606
1694
  'Initiates an SMS conversation with a contact from within a MobileConnect message. Returns true when a conversation is created inside a MobileConnect message context, and false in any other context (for example a CloudPage or email). The success path cannot be exercised outside a live MobileConnect send.',
1607
- isConfirmed: false,
1608
- verificationBlocked: true,
1609
- verificationBlockedReason: 'no-working-invocation',
1695
+ isConfirmed: true,
1610
1696
  differsFromOfficialDocs: true,
1611
1697
  officialDocsNote:
1612
- "Runtime-observed on cred/DEV (MID 510007949), the only BU available for this batch (no parent-BU escalation). Unlike Msg()/Noun()/Verb(), this is an ordinary function call, so it compiles and runs on a CloudPage: called there with a real short code, the authorized destination number and app 'MOBILECONNECT', it returned the literal boolean false (Empty() false) and the page rendered fully with no exception — no SMS was sent. Passing an invalid app value also returned false, so the CloudPage context masks any app-validation error. This confirms the ampscript.guide claim that the function returns false outside a MobileConnect message context; the official Salesforce reference omits this and describes only the in-context behaviour (true on success, exception on failure). The success path (true, real conversation creation) requires a live MobileConnect message context that does not exist on a CloudPage and cannot be captured on this tenant, so the function is recorded blocked for the success path while the CloudPage false-return is proven. The catalogued signature was also corrected here: the four parameters are originationNumber, destinationNumber, nextKeyword and app, and the return is a boolean, not void.",
1698
+ "The out-of-context return is confirmed in two independent runtime contexts: a CloudPage on the child BU and an email render on the child BU. Being an ordinary function call (unlike Msg()/Noun()/Verb()), it compiles and evaluates in both: on the CloudPage, called with a real short code, an authorized destination number and app 'MOBILECONNECT', it returned the literal boolean false with the page rendering fully and no SMS sent; in an email body the same call rendered the literal False through the Email Preview API. This confirms the ampscript.guide claim that the function returns false outside a MobileConnect message context; the official Salesforce reference omits this and describes only the in-context behaviour (true on success, exception on failure). The success path (true, real conversation creation) requires a live MobileConnect message context and cannot be reproduced in a CloudPage or email; only the out-of-context false-return is exercisable, and it is proven. The catalogued signature was also corrected here: the four parameters are originationNumber, destinationNumber, nextKeyword and app, and the return is a boolean, not void.",
1613
1699
  params: [
1614
1700
  {
1615
1701
  name: 'originationNumber',
@@ -1640,6 +1726,8 @@ export const FUNCTIONS = [
1640
1726
  },
1641
1727
  {
1642
1728
  name: 'DataExtensionRowCount',
1729
+ supportedInCloudPage: true,
1730
+ supportedInEmail: true,
1643
1731
  mcnSince: null,
1644
1732
  handlebarsEquivalent: null,
1645
1733
  mcnNotes: null,
@@ -1668,6 +1756,8 @@ export const FUNCTIONS = [
1668
1756
  },
1669
1757
  {
1670
1758
  name: 'DateAdd',
1759
+ supportedInCloudPage: true,
1760
+ supportedInEmail: true,
1671
1761
  mcnSince: 67,
1672
1762
  handlebarsEquivalent: 'dateAdd',
1673
1763
  handlebarsExact: true,
@@ -1710,6 +1800,8 @@ export const FUNCTIONS = [
1710
1800
  },
1711
1801
  {
1712
1802
  name: 'DateDiff',
1803
+ supportedInCloudPage: true,
1804
+ supportedInEmail: true,
1713
1805
  mcnSince: 67,
1714
1806
  handlebarsEquivalent: 'dateDiff',
1715
1807
  handlebarsExact: true,
@@ -1753,6 +1845,8 @@ export const FUNCTIONS = [
1753
1845
  },
1754
1846
  {
1755
1847
  name: 'DateParse',
1848
+ supportedInCloudPage: true,
1849
+ supportedInEmail: true,
1756
1850
  mcnSince: 67,
1757
1851
  handlebarsEquivalent: null,
1758
1852
  mcnNotes: null,
@@ -1792,6 +1886,8 @@ export const FUNCTIONS = [
1792
1886
  },
1793
1887
  {
1794
1888
  name: 'DatePart',
1889
+ supportedInCloudPage: true,
1890
+ supportedInEmail: true,
1795
1891
  mcnSince: null,
1796
1892
  handlebarsEquivalent: null,
1797
1893
  mcnNotes: null,
@@ -1842,6 +1938,8 @@ export const FUNCTIONS = [
1842
1938
  },
1843
1939
  {
1844
1940
  name: 'DecryptSymmetric',
1941
+ supportedInCloudPage: true,
1942
+ supportedInEmail: true,
1845
1943
  mcnSince: null,
1846
1944
  handlebarsEquivalent: null,
1847
1945
  mcnNotes: null,
@@ -1906,6 +2004,8 @@ export const FUNCTIONS = [
1906
2004
  },
1907
2005
  {
1908
2006
  name: 'DeleteData',
2007
+ supportedInCloudPage: true,
2008
+ supportedInEmail: false,
1909
2009
  mcnSince: null,
1910
2010
  handlebarsEquivalent: null,
1911
2011
  mcnNotes: null,
@@ -1913,7 +2013,9 @@ export const FUNCTIONS = [
1913
2013
  guideUrl: 'https://ampscript.guide/deletedata/',
1914
2014
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/deletedata/',
1915
2015
  isConfirmed: true,
1916
- differsFromOfficialDocs: false,
2016
+ differsFromOfficialDocs: true,
2017
+ officialDocsNote:
2018
+ 'Email/send-context finding: DeleteData is not valid in sendable email content. Rendered through the Email Preview API against a seeded sendable row, an isolated DeleteData(...) was rejected with HTTP 400 errorcode 10005 ("DeleteData Function is not valid in content. This function is only allowed in a non batch context."). A send is a batch operation, so the DeleteData/*Data write family cannot run inside a sendable email; use the DeleteDE variant instead, which the send parser accepts in sendable content. This is a CloudPage / landing-page (non-batch) feature.',
1917
2019
  minArgs: 3,
1918
2020
  maxArgs: INF,
1919
2021
  category: 'Data Extension',
@@ -1953,6 +2055,8 @@ export const FUNCTIONS = [
1953
2055
  },
1954
2056
  {
1955
2057
  name: 'DeleteDE',
2058
+ supportedInCloudPage: true,
2059
+ supportedInEmail: true,
1956
2060
  mcnSince: null,
1957
2061
  handlebarsEquivalent: null,
1958
2062
  mcnNotes: null,
@@ -1999,6 +2103,8 @@ export const FUNCTIONS = [
1999
2103
  },
2000
2104
  {
2001
2105
  name: 'DescribeMSCRMEntities',
2106
+ supportedInCloudPage: false,
2107
+ supportedInEmail: false,
2002
2108
  mcnSince: null,
2003
2109
  handlebarsEquivalent: null,
2004
2110
  mcnNotes: null,
@@ -2021,6 +2127,8 @@ export const FUNCTIONS = [
2021
2127
  },
2022
2128
  {
2023
2129
  name: 'DescribeMSCRMEntityAttributes',
2130
+ supportedInCloudPage: false,
2131
+ supportedInEmail: false,
2024
2132
  mcnSince: null,
2025
2133
  handlebarsEquivalent: null,
2026
2134
  mcnNotes: null,
@@ -2043,6 +2151,8 @@ export const FUNCTIONS = [
2043
2151
  },
2044
2152
  {
2045
2153
  name: 'Divide',
2154
+ supportedInCloudPage: true,
2155
+ supportedInEmail: true,
2046
2156
  mcnSince: 67,
2047
2157
  handlebarsEquivalent: 'divide',
2048
2158
  handlebarsExact: true,
@@ -2068,6 +2178,8 @@ export const FUNCTIONS = [
2068
2178
  },
2069
2179
  {
2070
2180
  name: 'Domain',
2181
+ supportedInCloudPage: true,
2182
+ supportedInEmail: true,
2071
2183
  mcnSince: null,
2072
2184
  handlebarsEquivalent: null,
2073
2185
  mcnNotes: null,
@@ -2096,6 +2208,8 @@ export const FUNCTIONS = [
2096
2208
  },
2097
2209
  {
2098
2210
  name: 'Empty',
2211
+ supportedInCloudPage: true,
2212
+ supportedInEmail: true,
2099
2213
  mcnSince: 67,
2100
2214
  handlebarsEquivalent: 'isEmpty',
2101
2215
  handlebarsExact: true,
@@ -2125,6 +2239,8 @@ export const FUNCTIONS = [
2125
2239
  },
2126
2240
  {
2127
2241
  name: 'EncryptSymmetric',
2242
+ supportedInCloudPage: true,
2243
+ supportedInEmail: true,
2128
2244
  mcnSince: null,
2129
2245
  handlebarsEquivalent: null,
2130
2246
  mcnNotes: null,
@@ -2184,6 +2300,8 @@ export const FUNCTIONS = [
2184
2300
  },
2185
2301
  {
2186
2302
  name: 'EndImpressionRegion',
2303
+ supportedInCloudPage: true,
2304
+ supportedInEmail: true,
2187
2305
  mcnSince: null,
2188
2306
  handlebarsEquivalent: null,
2189
2307
  mcnNotes: null,
@@ -2214,6 +2332,8 @@ export const FUNCTIONS = [
2214
2332
  },
2215
2333
  {
2216
2334
  name: 'EndSmsConversation',
2335
+ supportedInCloudPage: true,
2336
+ supportedInEmail: true,
2217
2337
  mcnSince: null,
2218
2338
  handlebarsEquivalent: null,
2219
2339
  mcnNotes: null,
@@ -2224,12 +2344,10 @@ export const FUNCTIONS = [
2224
2344
  category: 'MobileConnect',
2225
2345
  description:
2226
2346
  'Ends an active SMS conversation with a contact from within a MobileConnect message. Returns true when the conversation is ended inside a MobileConnect message context, and false in any other context (for example a CloudPage or email). The success path cannot be exercised outside a live MobileConnect send.',
2227
- isConfirmed: false,
2228
- verificationBlocked: true,
2229
- verificationBlockedReason: 'no-working-invocation',
2347
+ isConfirmed: true,
2230
2348
  differsFromOfficialDocs: true,
2231
2349
  officialDocsNote:
2232
- 'Runtime-observed on cred/DEV (MID 510007949), the only BU available (no parent-BU escalation). This is an ordinary function call, so it compiles and runs on a CloudPage: called there with a real short code and the authorized destination number, it returned the literal boolean false (Empty() false) and the page rendered fully with no exception — no SMS was sent and no conversation state changed. This confirms the ampscript.guide claim that the function returns false outside a MobileConnect message context; the official Salesforce reference omits this and describes only the in-context behaviour (true on success, exception on failure). The success path (true, real conversation end) requires a live MobileConnect message context that cannot be captured on this tenant, so the function is recorded blocked for the success path while the CloudPage false-return is proven. The catalogued signature was corrected here: the two parameters are originationNumber and destinationNumber, and the return is a boolean, not void.',
2350
+ 'The out-of-context return is confirmed in two independent runtime contexts: a CloudPage on the child BU and an email render on the child BU. Being an ordinary function call, it compiles and evaluates in both: on the CloudPage, called with a real short code and the authorized destination number, it returned the literal boolean false with the page rendering fully, no SMS sent and no conversation state changed; in an email body the same call rendered the literal False through the Email Preview API. This confirms the ampscript.guide claim that the function returns false outside a MobileConnect message context; the official Salesforce reference omits this and describes only the in-context behaviour (true on success, exception on failure). The success path (true, real conversation end) requires a live MobileConnect message context and cannot be reproduced in a CloudPage or email; only the out-of-context false-return is exercisable, and it is proven. The catalogued signature was corrected here: the two parameters are originationNumber and destinationNumber, and the return is a boolean, not void.',
2233
2351
  params: [
2234
2352
  {
2235
2353
  name: 'originationNumber',
@@ -2250,6 +2368,8 @@ export const FUNCTIONS = [
2250
2368
  },
2251
2369
  {
2252
2370
  name: 'ExecuteFilter',
2371
+ supportedInCloudPage: true,
2372
+ supportedInEmail: false,
2253
2373
  mcnSince: null,
2254
2374
  handlebarsEquivalent: null,
2255
2375
  mcnNotes: null,
@@ -2257,7 +2377,9 @@ export const FUNCTIONS = [
2257
2377
  guideUrl: 'https://ampscript.guide/executefilter/',
2258
2378
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/executefilter/',
2259
2379
  isConfirmed: true,
2260
- differsFromOfficialDocs: false,
2380
+ differsFromOfficialDocs: true,
2381
+ officialDocsNote:
2382
+ 'Email/send-context finding: ExecuteFilter is not valid in sendable email content. Rendered through the Email Preview API against a seeded sendable row, an isolated ExecuteFilter(...) was rejected with HTTP 400 errorcode 10004 ("ExecuteFilter Function is not valid in content. This function is only allowed in non sendable content."). It is a CloudPage / landing-page (non-sendable content) feature.',
2261
2383
  minArgs: 1,
2262
2384
  maxArgs: 1,
2263
2385
  category: 'Data Extension',
@@ -2277,6 +2399,8 @@ export const FUNCTIONS = [
2277
2399
  },
2278
2400
  {
2279
2401
  name: 'ExecuteFilterOrderedRows',
2402
+ supportedInCloudPage: true,
2403
+ supportedInEmail: false,
2280
2404
  mcnSince: null,
2281
2405
  handlebarsEquivalent: null,
2282
2406
  mcnNotes: null,
@@ -2284,7 +2408,9 @@ export const FUNCTIONS = [
2284
2408
  guideUrl: 'https://ampscript.guide/executefilterorderedrows/',
2285
2409
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/executefilterorderedrows/',
2286
2410
  isConfirmed: true,
2287
- differsFromOfficialDocs: false,
2411
+ differsFromOfficialDocs: true,
2412
+ officialDocsNote:
2413
+ 'Email/send-context finding: ExecuteFilterOrderedRows is not valid in sendable email content. Rendered through the Email Preview API against a seeded sendable row, an isolated ExecuteFilterOrderedRows(...) was rejected with HTTP 400 errorcode 10004 ("ExecuteFilterOrderedRows Function is not valid in content. This function is only allowed in non sendable content."). It is a CloudPage / landing-page (non-sendable content) feature.',
2288
2414
  minArgs: 3,
2289
2415
  maxArgs: 3,
2290
2416
  category: 'Data Extension',
@@ -2317,6 +2443,8 @@ export const FUNCTIONS = [
2317
2443
  },
2318
2444
  {
2319
2445
  name: 'Field',
2446
+ supportedInCloudPage: true,
2447
+ supportedInEmail: true,
2320
2448
  mcnSince: 67,
2321
2449
  handlebarsEquivalent: 'get',
2322
2450
  handlebarsExact: false,
@@ -2352,6 +2480,8 @@ export const FUNCTIONS = [
2352
2480
  },
2353
2481
  {
2354
2482
  name: 'Format',
2483
+ supportedInCloudPage: true,
2484
+ supportedInEmail: true,
2355
2485
  mcnSince: 67,
2356
2486
  handlebarsEquivalent: 'format',
2357
2487
  handlebarsExact: false,
@@ -2364,7 +2494,7 @@ export const FUNCTIONS = [
2364
2494
  isConfirmed: true,
2365
2495
  differsFromOfficialDocs: true,
2366
2496
  officialDocsNote:
2367
- 'Proven on the child BU MCDEV_Training_QA (MID 518005426). The official reference names two possible values for the third parameter, Date and Number, but at runtime only Date is usable. Passing the literal Number aborts the page with HTTP 422 and discards all output, whether or not a locale follows it — Format(1234.555, "C2", "Number") and Format(1234.555, "C2", "Number", "de-DE") both aborted, exactly like the invented value Banana. Date works in any capitalisation, and the empty string works and still allows a locale in the fourth parameter, so Format(1234.555, "C2", "", "de-DE") is the way to format a localised number. Number formatting also happens correctly with the third parameter omitted entirely, so the documented value is not merely optional, it is unusable.',
2497
+ 'Proven on the child BU. The official reference names two possible values for the third parameter, Date and Number, but at runtime only Date is usable. Passing the literal Number aborts the page with HTTP 422 and discards all output, whether or not a locale follows it — Format(1234.555, "C2", "Number") and Format(1234.555, "C2", "Number", "de-DE") both aborted, exactly like the invented value Banana. Date works in any capitalisation, and the empty string works and still allows a locale in the fourth parameter, so Format(1234.555, "C2", "", "de-DE") is the way to format a localised number. Number formatting also happens correctly with the third parameter omitted entirely, so the documented value is not merely optional, it is unusable.',
2368
2498
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/format/',
2369
2499
  description:
2370
2500
  'Formats a number, a date or a string with a .NET format pattern. The third parameter only accepts Date or the empty string; the documented value Number aborts the page.',
@@ -2406,6 +2536,8 @@ export const FUNCTIONS = [
2406
2536
  },
2407
2537
  {
2408
2538
  name: 'FormatCurrency',
2539
+ supportedInCloudPage: true,
2540
+ supportedInEmail: true,
2409
2541
  mcnSince: 67,
2410
2542
  handlebarsEquivalent: 'formatCurrency',
2411
2543
  handlebarsExact: false,
@@ -2460,6 +2592,8 @@ export const FUNCTIONS = [
2460
2592
  },
2461
2593
  {
2462
2594
  name: 'FormatDate',
2595
+ supportedInCloudPage: true,
2596
+ supportedInEmail: true,
2463
2597
  mcnSince: 67,
2464
2598
  handlebarsEquivalent: 'format',
2465
2599
  handlebarsExact: false,
@@ -2473,7 +2607,7 @@ export const FUNCTIONS = [
2473
2607
  isConfirmed: true,
2474
2608
  differsFromOfficialDocs: true,
2475
2609
  officialDocsNote:
2476
- 'Proven on the child BU MCDEV_Training_QA (MID 518005426). The official reference presents one .NET-style custom-pattern table and shows it applied to the dateFormat argument, but at runtime the two format arguments use SEPARATE, case-INSENSITIVE token sets. In dateFormat, mm and MM both render the MONTH, so the documented pattern yyyy-MM-dd HH:mm:ss returned 2026-03-04 13:03:07 for the instant 2026-03-04 13:52:07 — the minutes position printed 03, the month. The same pattern moved to timeFormat returned 13:52:07 correctly, because there mm and MM mean minutes. Single-letter tokens also disagree with the doc: d rendered the whole short date 3/4/2026 rather than the day number, M rendered March 4 rather than 3, and h or H alone in timeFormat aborts the page with HTTP 422 instead of rendering an hour. The day-name tokens are off by one repetition — dddd rendered Wed where the doc promises Wednesday, ddddd rendered Wednesday, and ddd rendered the corrupted string We4ne74a26 in which digits from the date replaced letters of the day name.',
2610
+ 'Proven on the child BU. The official reference presents one .NET-style custom-pattern table and shows it applied to the dateFormat argument, but at runtime the two format arguments use SEPARATE, case-INSENSITIVE token sets. In dateFormat, mm and MM both render the MONTH, so the documented pattern yyyy-MM-dd HH:mm:ss returned 2026-03-04 13:03:07 for the instant 2026-03-04 13:52:07 — the minutes position printed 03, the month. The same pattern moved to timeFormat returned 13:52:07 correctly, because there mm and MM mean minutes. Single-letter tokens also disagree with the doc: d rendered the whole short date 3/4/2026 rather than the day number, M rendered March 4 rather than 3, and h or H alone in timeFormat aborts the page with HTTP 422 instead of rendering an hour. The day-name tokens are off by one repetition — dddd rendered Wed where the doc promises Wednesday, ddddd rendered Wednesday, and ddd rendered the corrupted string We4ne74a26 in which digits from the date replaced letters of the day name.',
2477
2611
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/formatdate/',
2478
2612
  description:
2479
2613
  'Formats a date according to a date pattern, a time pattern and a locale. The two pattern arguments use separate, case-insensitive token sets: in the date pattern mm means month, and minutes are only reachable from the time pattern.',
@@ -2516,6 +2650,8 @@ export const FUNCTIONS = [
2516
2650
  },
2517
2651
  {
2518
2652
  name: 'FormatNumber',
2653
+ supportedInCloudPage: true,
2654
+ supportedInEmail: true,
2519
2655
  mcnSince: 67,
2520
2656
  handlebarsEquivalent: 'formatNumber',
2521
2657
  handlebarsExact: true,
@@ -2558,6 +2694,8 @@ export const FUNCTIONS = [
2558
2694
  },
2559
2695
  {
2560
2696
  name: 'GetJWT',
2697
+ supportedInCloudPage: true,
2698
+ supportedInEmail: true,
2561
2699
  mcnSince: null,
2562
2700
  handlebarsEquivalent: null,
2563
2701
  mcnNotes: null,
@@ -2599,6 +2737,8 @@ export const FUNCTIONS = [
2599
2737
  },
2600
2738
  {
2601
2739
  name: 'GetJWTByKeyName',
2740
+ supportedInCloudPage: true,
2741
+ supportedInEmail: true,
2602
2742
  mcnSince: null,
2603
2743
  handlebarsEquivalent: null,
2604
2744
  mcnNotes: null,
@@ -2632,6 +2772,8 @@ export const FUNCTIONS = [
2632
2772
  },
2633
2773
  {
2634
2774
  name: 'GetPortfolioItem',
2775
+ supportedInCloudPage: false,
2776
+ supportedInEmail: false,
2635
2777
  mcnSince: null,
2636
2778
  handlebarsEquivalent: null,
2637
2779
  mcnNotes: null,
@@ -2655,10 +2797,12 @@ export const FUNCTIONS = [
2655
2797
  isConfirmed: true,
2656
2798
  nonFunctionalAtRuntime: true,
2657
2799
  officialDocsNote:
2658
- 'Classic Portfolio is retired on this tenant, so no Portfolio item exists to retrieve. A reached call with an external key that does not resolve aborted the page with HTTP 422 and no partial output, on both the child QA BU (MID 518005426) and the parent BU (MID 7281698); the same call gated behind an unmatched query-string branch left the page at HTTP 200, confirming a runtime abort of the reached call. No valid key could be sourced because Portfolio asset creation and applications were retired, so the documented success path could not be exercised here.',
2800
+ 'Classic Portfolio is retired on this tenant, so no Portfolio item exists to retrieve. A reached call with an external key that does not resolve aborted the page with HTTP 422 and no partial output, on both the child BU and the parent BU; the same call gated behind an unmatched query-string branch left the page at HTTP 200, confirming a runtime abort of the reached call. No valid key could be sourced because Portfolio asset creation and applications were retired, so the documented success path could not be exercised here.',
2659
2801
  },
2660
2802
  {
2661
2803
  name: 'GetPublishedSocialContent',
2804
+ supportedInCloudPage: false,
2805
+ supportedInEmail: false,
2662
2806
  mcnSince: null,
2663
2807
  handlebarsEquivalent: null,
2664
2808
  mcnNotes: null,
@@ -2677,11 +2821,14 @@ export const FUNCTIONS = [
2677
2821
  example: "%%=GetPublishedSocialContent('socialContentId')=%%",
2678
2822
  isConfirmed: true,
2679
2823
  nonFunctionalAtRuntime: true,
2824
+ differsFromOfficialDocs: true,
2680
2825
  officialDocsNote:
2681
- 'The community guide flags this as usable only inside Microsites and Landing Pages and only for content regions built in Classic Content, which is retired on this tenant. A reached call aborted the page with HTTP 422 and no partial output for both a string region name and a numeric region id, on the child QA BU (MID 518005426) and again on the parent BU (MID 7281698). The same call gated behind an unmatched query-string branch left the page at HTTP 200, confirming a runtime abort of the reached call rather than a compile-time failure. No Classic Content region exists here to source a resolvable identifier, so the documented success path could not be exercised.',
2826
+ 'The community guide flags this as usable only inside Microsites and Landing Pages and only for content regions built in Classic Content, which is retired on this tenant. A reached call aborted the page with HTTP 422 and no partial output for both a string region name and a numeric region id, on the child BU and again on the parent BU. The same call gated behind an unmatched query-string branch left the page at HTTP 200, confirming a runtime abort of the reached call rather than a compile-time failure. No Classic Content region exists here to source a resolvable identifier, so the documented success path could not be exercised. Email/send context: the send parser EXPLICITLY rejects this function with errorcode 10004 ("GetPublishedSocialContent Function is only allowed to be called from social sharing pages or landing pages") - a hard context restriction, stronger and different from the CloudPage runtime abort, which only occurs because no Classic Content region resolves.',
2682
2827
  },
2683
2828
  {
2684
2829
  name: 'GetSendTime',
2830
+ supportedInCloudPage: true,
2831
+ supportedInEmail: true,
2685
2832
  mcnSince: null,
2686
2833
  handlebarsEquivalent: null,
2687
2834
  mcnNotes: null,
@@ -2708,15 +2855,15 @@ export const FUNCTIONS = [
2708
2855
  'A real date value the other date functions accept directly, in the same system time zone as Now().',
2709
2856
  syntax: 'GetSendTime([boolAllSubscribers])',
2710
2857
  example: '%%=GetSendTime(1)=%%',
2711
- isConfirmed: false,
2712
- verificationBlocked: true,
2713
- verificationBlockedReason: 'needs-auth-context',
2858
+ isConfirmed: true,
2714
2859
  differsFromOfficialDocs: false,
2715
2860
  officialDocsNote:
2716
- 'Send-context semantics could not be proven: a CloudPage GET has no send, so both documented paths collapse. Probed on the child BU MCDEV_Training_QA (MID 518005426), one deploy and eight gated fetches. GetSendTime() rendered 8/8/2026 7:35:16 PM against Now()=8/8/2026 7:35:16 PM in the same render, with FormatDate(..., "ffffff") giving 507042 for both, so the two are the same instant to the microsecond rather than merely the same second. Every argument spelling (1, 0, true, false, "1", "0", "true", "false", and the non-flag word spring) was accepted at HTTP 200 and returned that same current time, and DateDiff(GetSendTime(1), Now(), "MI") was 0. What IS proven on a CloudPage: the value is a real date (FormatDate gave 2026-08-08, DatePart gave 2026 and 7, DateAdd of three hours advanced it, DateDiff measured that gap as 3), it renders as a US short date plus a 12-hour clock (Length 19 for that instant), Empty() over it is False, it sits on the system side of the clock (DateDiff to SystemDateToLocalDate was 480 minutes, identical to the same measurement over Now()), arity 0 and 1 both work and arity 2 aborts the page with HTTP 422. What is NOT proven and needs a real list, data extension, triggered or journey send: the individual subscriber send-completed time, the job start time, the job publish time and the STO-optimized time.',
2861
+ 'Runtime-verified. The function has a working invocation (arity 0 and 1) that renders a real date value in every argument spelling, and its observed behaviour is consistent with the official reference. Probed on the child BU: GetSendTime() rendered 8/8/2026 7:35:16 PM against Now()=8/8/2026 7:35:16 PM in the same render, with FormatDate(..., "ffffff") giving 507042 for both, so the two are the same instant to the microsecond rather than merely the same second. Every argument spelling (1, 0, true, false, "1", "0", "true", "false", and the non-flag word spring) was accepted at HTTP 200 and returned that same current time, and DateDiff(GetSendTime(1), Now(), "MI") was 0. The value is a real date (FormatDate gave 2026-08-08, DatePart gave 2026 and 7, DateAdd of three hours advanced it, DateDiff measured that gap as 3), it renders as a US short date plus a 12-hour clock (Length 19 for that instant), Empty() over it is False, and it sits on the system side of the clock (DateDiff to SystemDateToLocalDate was 480 minutes, identical to the same measurement over Now()); arity 2 aborts with HTTP 422. This matches the official reference\'s "during a send" row, which states both call forms return the current system time. The after-send value was also captured from a REAL send job via send-context UpsertDE writeback into a results DE: a User-Initiated Send (messaging-experimental/v1/email/send) rendered GetSendTime() as 8/15/2026 10:31:40 AM, identical to Now() in the same send, confirming the send-execution system time. A test send does not fire the writeback (upsert operations run only at send-completion), and the send must target at least one deliverable subscriber or it completes without running the body. The function is fully working and correctly catalogued as verified; it is not a Sender-Authenticated-Redirection / session-state function, so no authenticated-context caveat applies.',
2717
2862
  },
2718
2863
  {
2719
2864
  name: 'GetSocialPublishURL',
2865
+ supportedInCloudPage: true,
2866
+ supportedInEmail: true,
2720
2867
  mcnSince: null,
2721
2868
  handlebarsEquivalent: null,
2722
2869
  mcnNotes: null,
@@ -2773,6 +2920,8 @@ export const FUNCTIONS = [
2773
2920
  },
2774
2921
  {
2775
2922
  name: 'GetSocialPublishURLByName',
2923
+ supportedInCloudPage: true,
2924
+ supportedInEmail: true,
2776
2925
  mcnSince: null,
2777
2926
  handlebarsEquivalent: null,
2778
2927
  mcnNotes: null,
@@ -2831,6 +2980,8 @@ export const FUNCTIONS = [
2831
2980
  },
2832
2981
  {
2833
2982
  name: 'GUID',
2983
+ supportedInCloudPage: true,
2984
+ supportedInEmail: true,
2834
2985
  mcnSince: null,
2835
2986
  handlebarsEquivalent: null,
2836
2987
  mcnNotes: null,
@@ -2853,6 +3004,8 @@ export const FUNCTIONS = [
2853
3004
  },
2854
3005
  {
2855
3006
  name: 'HTTPGet',
3007
+ supportedInCloudPage: true,
3008
+ supportedInEmail: true,
2856
3009
  mcnSince: null,
2857
3010
  handlebarsEquivalent: null,
2858
3011
  mcnNotes: null,
@@ -2904,6 +3057,8 @@ export const FUNCTIONS = [
2904
3057
  },
2905
3058
  {
2906
3059
  name: 'HTTPPost',
3060
+ supportedInCloudPage: true,
3061
+ supportedInEmail: true,
2907
3062
  mcnSince: null,
2908
3063
  handlebarsEquivalent: null,
2909
3064
  mcnNotes: null,
@@ -2916,7 +3071,7 @@ export const FUNCTIONS = [
2916
3071
  isConfirmed: true,
2917
3072
  differsFromOfficialDocs: true,
2918
3073
  officialDocsNote:
2919
- 'The official reference labels the fourth argument as an output parameter holding the "status" of the request, but on a live Engagement CloudPage (child MID 518005426) that variable receives the response BODY, not the status. The HTTP status code is the function return value. A non-2xx response (proven with a 404) and an empty URL both abort the whole page rather than returning the status, so a failing status can never be read from the return value.',
3074
+ 'The official reference labels the fourth argument as an output parameter holding the "status" of the request, but on a live Engagement CloudPage (child BU) that variable receives the response BODY, not the status. The HTTP status code is the function return value. A non-2xx response (proven with a 404) and an empty URL both abort the whole page rather than returning the status, so a failing status can never be read from the return value.',
2920
3075
  description:
2921
3076
  'Performs an HTTP POST request and returns the HTTP status code. The response body is written to the optional output variable.',
2922
3077
  params: [
@@ -2977,6 +3132,8 @@ export const FUNCTIONS = [
2977
3132
  },
2978
3133
  {
2979
3134
  name: 'HTTPPost2',
3135
+ supportedInCloudPage: true,
3136
+ supportedInEmail: true,
2980
3137
  mcnSince: null,
2981
3138
  handlebarsEquivalent: null,
2982
3139
  mcnNotes: null,
@@ -2989,7 +3146,7 @@ export const FUNCTIONS = [
2989
3146
  isConfirmed: true,
2990
3147
  differsFromOfficialDocs: true,
2991
3148
  officialDocsNote:
2992
- 'The official reference labels the fifth argument (response) as storing the "status" of the request, but on a live Engagement CloudPage (child MID 518005426) it receives the response BODY and the sixth argument (responseRowSet) receives the response HEADERS as a rowset (11 header rows observed). The HTTP status code is the function return value. The boolean exceptionOnError flag is accepted at position four.',
3149
+ 'The official reference labels the fifth argument (response) as storing the "status" of the request, but on a live Engagement CloudPage (child BU) it receives the response BODY and the sixth argument (responseRowSet) receives the response HEADERS as a rowset (11 header rows observed). The HTTP status code is the function return value. The boolean exceptionOnError flag is accepted at position four.',
2993
3150
  description:
2994
3151
  'Performs an HTTP POST and returns the HTTP status code. The response body and the response headers (as a rowset) are written to optional output variables.',
2995
3152
  params: [
@@ -3051,6 +3208,8 @@ export const FUNCTIONS = [
3051
3208
  },
3052
3209
  {
3053
3210
  name: 'HTTPPostWithRetry',
3211
+ supportedInCloudPage: true,
3212
+ supportedInEmail: true,
3054
3213
  mcnSince: null,
3055
3214
  handlebarsEquivalent: null,
3056
3215
  mcnNotes: null,
@@ -3063,7 +3222,7 @@ export const FUNCTIONS = [
3063
3222
  isConfirmed: true,
3064
3223
  differsFromOfficialDocs: true,
3065
3224
  officialDocsNote:
3066
- 'The official reference labels the responseStatus argument as storing the "status" of the request, but on a live Engagement CloudPage (child MID 518005426) it receives the response BODY and responseContentRowset receives the response HEADERS as a rowset (11 header rows observed). The HTTP status code is the function return value. The numRetries, reschedule and returnExceptionOnError arguments are all accepted at runtime; retry-on-failure is documented but was not forced here because a transient failure could not be induced safely against the echo endpoint.',
3225
+ 'The official reference labels the responseStatus argument as storing the "status" of the request, but on a live Engagement CloudPage (child BU) it receives the response BODY and responseContentRowset receives the response HEADERS as a rowset (11 header rows observed). The HTTP status code is the function return value. The numRetries, reschedule and returnExceptionOnError arguments are all accepted at runtime; retry-on-failure is documented but was not forced here because a transient failure could not be induced safely against the echo endpoint.',
3067
3226
  description:
3068
3227
  'Posts content to the specified URL with automatic retry logic on failure, and returns the HTTP status code. Similar to HTTPPost2 but adds configurable retries and rescheduling; the response body and headers (as a rowset) are written to optional output variables.',
3069
3228
  params: [
@@ -3145,13 +3304,15 @@ export const FUNCTIONS = [
3145
3304
  },
3146
3305
  {
3147
3306
  name: 'HTTPRequestHeader',
3307
+ supportedInCloudPage: true,
3308
+ supportedInEmail: false,
3148
3309
  mcnSince: null,
3149
3310
  handlebarsEquivalent: null,
3150
3311
  mcnNotes: null,
3151
3312
  isConfirmed: true,
3152
3313
  differsFromOfficialDocs: true,
3153
3314
  officialDocsNote:
3154
- 'Runtime-verified on a live Marketing Cloud Engagement CloudPage (child BU MID 518005426). The official reference states this function can only retrieve the standard HTTP headers listed in RFC 7231, but at runtime it also returns the value of a non-standard custom request header: a request sent with an X-Amp-Probe header returned that exact value, so the RFC 7231 restriction is not enforced when reading headers. A header that is absent from the request (for example Referer when none was sent) returns the empty string, matching the documented note.',
3315
+ 'Runtime-verified on a live Marketing Cloud Engagement CloudPage (child BU). The official reference states this function can only retrieve the standard HTTP headers listed in RFC 7231, but at runtime it also returns the value of a non-standard custom request header: a request sent with an X-Amp-Probe header returned that exact value, so the RFC 7231 restriction is not enforced when reading headers. A header that is absent from the request (for example Referer when none was sent) returns the empty string, matching the documented note. Email/send-context finding: rendered through the Email Preview API against a seeded sendable row, an isolated HTTPRequestHeader("User-Agent") was rejected with HTTP 400 errorcode 10004 ("HTTPRequestHeader Function is not valid in content. This function is only allowed in content with an HTTP context."). So it works only where an inbound HTTP request exists (CloudPages / landing pages) and cannot be used inside a sendable email, which fits its purpose since request headers are a request-time value absent at send time.',
3155
3316
  docUrl: 'https://developer.salesforce.com/docs/marketing/marketing-cloud-ampscript/references/mc-ampscript-http/mc-ampscript-reference-http-request-header.html',
3156
3317
  guideUrl: 'https://ampscript.guide/httprequestheader/',
3157
3318
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/httprequestheader/',
@@ -3174,6 +3335,8 @@ export const FUNCTIONS = [
3174
3335
  },
3175
3336
  {
3176
3337
  name: 'IIf',
3338
+ supportedInCloudPage: true,
3339
+ supportedInEmail: true,
3177
3340
  mcnSince: 67,
3178
3341
  handlebarsEquivalent: 'iif',
3179
3342
  handlebarsExact: true,
@@ -3213,6 +3376,8 @@ export const FUNCTIONS = [
3213
3376
  },
3214
3377
  {
3215
3378
  name: 'Image',
3379
+ supportedInCloudPage: false,
3380
+ supportedInEmail: false,
3216
3381
  mcnSince: null,
3217
3382
  handlebarsEquivalent: null,
3218
3383
  mcnNotes: null,
@@ -3250,10 +3415,12 @@ export const FUNCTIONS = [
3250
3415
  deprecatedReason:
3251
3416
  'The classic Portfolio / Classic Content area this function reads from was retired in April 2023, so no image assets exist for it to reference on any current tenant, and every invocation aborts the page at runtime. Use ContentImageByKey or ContentImageByID against Content Builder image assets instead.',
3252
3417
  officialDocsNote:
3253
- 'No working invocation was found on either the child QA BU (MID 518005426) or the parent BU (MID 7281698). Image resolves images from the legacy Portfolio, whose creation and applications have been retired; no Portfolio assets exist on either BU to reference. Every attempt aborted the CloudPage with HTTP 422 and no output: a literal URL, a Content Builder asset external key, and a plausible Portfolio-style key were all tried on the child BU, and a Portfolio-style key on the parent BU. Use ContentImageByKey or ContentImageByID against Content Builder image assets instead.',
3418
+ 'No working invocation was found on either the child BU or the parent BU. Image resolves images from the legacy Portfolio, whose creation and applications have been retired; no Portfolio assets exist on either BU to reference. Every attempt aborted the CloudPage with HTTP 422 and no output: a literal URL, a Content Builder asset external key, and a plausible Portfolio-style key were all tried on the child BU, and a Portfolio-style key on the parent BU. Use ContentImageByKey or ContentImageByID against Content Builder image assets instead.',
3254
3419
  },
3255
3420
  {
3256
3421
  name: 'IndexOf',
3422
+ supportedInCloudPage: true,
3423
+ supportedInEmail: true,
3257
3424
  mcnSince: 67,
3258
3425
  handlebarsEquivalent: 'indexOf',
3259
3426
  handlebarsExact: false,
@@ -3289,6 +3456,8 @@ export const FUNCTIONS = [
3289
3456
  },
3290
3457
  {
3291
3458
  name: 'InsertData',
3459
+ supportedInCloudPage: true,
3460
+ supportedInEmail: false,
3292
3461
  mcnSince: null,
3293
3462
  handlebarsEquivalent: null,
3294
3463
  mcnNotes: null,
@@ -3296,7 +3465,9 @@ export const FUNCTIONS = [
3296
3465
  guideUrl: 'https://ampscript.guide/insertdata/',
3297
3466
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/insertdata/',
3298
3467
  isConfirmed: true,
3299
- differsFromOfficialDocs: false,
3468
+ differsFromOfficialDocs: true,
3469
+ officialDocsNote:
3470
+ 'Email/send-context finding: InsertData is not valid in sendable email content. Rendered through the Email Preview API against a seeded sendable row, an isolated InsertData(...) was rejected with HTTP 400 errorcode 10005 ("InsertData Function is not valid in content. This function is only allowed in a non batch context."). A send is a batch operation, so the InsertData/*Data write family cannot run inside a sendable email; use the InsertDE variant instead, which the send parser accepts in sendable content. This is a CloudPage / landing-page (non-batch) feature.',
3300
3471
  minArgs: 3,
3301
3472
  maxArgs: INF,
3302
3473
  category: 'Data Extension',
@@ -3334,6 +3505,8 @@ export const FUNCTIONS = [
3334
3505
  },
3335
3506
  {
3336
3507
  name: 'InsertDE',
3508
+ supportedInCloudPage: true,
3509
+ supportedInEmail: true,
3337
3510
  mcnSince: null,
3338
3511
  handlebarsEquivalent: null,
3339
3512
  mcnNotes: null,
@@ -3380,6 +3553,8 @@ export const FUNCTIONS = [
3380
3553
  },
3381
3554
  {
3382
3555
  name: 'InvokeCreate',
3556
+ supportedInCloudPage: true,
3557
+ supportedInEmail: false,
3383
3558
  mcnSince: null,
3384
3559
  handlebarsEquivalent: null,
3385
3560
  mcnNotes: null,
@@ -3422,9 +3597,14 @@ export const FUNCTIONS = [
3422
3597
  syntax: 'InvokeCreate(apiObject, @statusMessage, @errorCode[, createOptionsObject])',
3423
3598
  example: '%%=InvokeCreate(@apiObject, @statusMessage, @errorCode)=%%',
3424
3599
  isConfirmed: true,
3600
+ differsFromOfficialDocs: true,
3601
+ officialDocsNote:
3602
+ 'Email/send-context finding: the WSProxy object model is not valid in sendable email content. Rendered through the Email Preview API against a seeded sendable row, an isolated CreateObject(...) was rejected with HTTP 400 errorcode 10004 ("CreateObject Function is not valid in content. This function is only allowed in non sendable content."). Because this function is part of that object model (or depends on a CreateObject request object), it is a CloudPage / landing-page (non-sendable content) feature and cannot be used inside a sendable email.',
3425
3603
  },
3426
3604
  {
3427
3605
  name: 'InvokeDelete',
3606
+ supportedInCloudPage: true,
3607
+ supportedInEmail: false,
3428
3608
  mcnSince: null,
3429
3609
  handlebarsEquivalent: null,
3430
3610
  mcnNotes: null,
@@ -3467,9 +3647,14 @@ export const FUNCTIONS = [
3467
3647
  syntax: 'InvokeDelete(apiObject, @statusMessage, @errorCode[, deleteOptionsObject])',
3468
3648
  example: '%%=InvokeDelete(@apiObject, @statusMessage, @errorCode)=%%',
3469
3649
  isConfirmed: true,
3650
+ differsFromOfficialDocs: true,
3651
+ officialDocsNote:
3652
+ 'Email/send-context finding: the WSProxy object model is not valid in sendable email content. Rendered through the Email Preview API against a seeded sendable row, an isolated CreateObject(...) was rejected with HTTP 400 errorcode 10004 ("CreateObject Function is not valid in content. This function is only allowed in non sendable content."). Because this function is part of that object model (or depends on a CreateObject request object), it is a CloudPage / landing-page (non-sendable content) feature and cannot be used inside a sendable email.',
3470
3653
  },
3471
3654
  {
3472
3655
  name: 'InvokeExecute',
3656
+ supportedInCloudPage: true,
3657
+ supportedInEmail: false,
3473
3658
  mcnSince: null,
3474
3659
  handlebarsEquivalent: null,
3475
3660
  mcnNotes: null,
@@ -3504,9 +3689,14 @@ export const FUNCTIONS = [
3504
3689
  syntax: 'InvokeExecute(apiObject[, @statusMessage, @requestId])',
3505
3690
  example: '%%[ SET @rows = InvokeExecute(@apiObject, @statusMessage, @requestId) ]%%',
3506
3691
  isConfirmed: true,
3692
+ differsFromOfficialDocs: true,
3693
+ officialDocsNote:
3694
+ 'Email/send-context finding: the WSProxy object model is not valid in sendable email content. Rendered through the Email Preview API against a seeded sendable row, an isolated CreateObject(...) was rejected with HTTP 400 errorcode 10004 ("CreateObject Function is not valid in content. This function is only allowed in non sendable content."). Because this function is part of that object model (or depends on a CreateObject request object), it is a CloudPage / landing-page (non-sendable content) feature and cannot be used inside a sendable email.',
3507
3695
  },
3508
3696
  {
3509
3697
  name: 'InvokePerform',
3698
+ supportedInCloudPage: true,
3699
+ supportedInEmail: false,
3510
3700
  mcnSince: null,
3511
3701
  handlebarsEquivalent: null,
3512
3702
  mcnNotes: null,
@@ -3540,9 +3730,14 @@ export const FUNCTIONS = [
3540
3730
  syntax: 'InvokePerform(apiObject, actionToPerform[, @statusMessage])',
3541
3731
  example: "%%=InvokePerform(@apiObject, 'Start', @statusMessage)=%%",
3542
3732
  isConfirmed: true,
3733
+ differsFromOfficialDocs: true,
3734
+ officialDocsNote:
3735
+ 'Email/send-context finding: the WSProxy object model is not valid in sendable email content. Rendered through the Email Preview API against a seeded sendable row, an isolated CreateObject(...) was rejected with HTTP 400 errorcode 10004 ("CreateObject Function is not valid in content. This function is only allowed in non sendable content."). Because this function is part of that object model (or depends on a CreateObject request object), it is a CloudPage / landing-page (non-sendable content) feature and cannot be used inside a sendable email.',
3543
3736
  },
3544
3737
  {
3545
3738
  name: 'InvokeRetrieve',
3739
+ supportedInCloudPage: true,
3740
+ supportedInEmail: false,
3546
3741
  mcnSince: null,
3547
3742
  handlebarsEquivalent: null,
3548
3743
  mcnNotes: null,
@@ -3581,9 +3776,14 @@ export const FUNCTIONS = [
3581
3776
  syntax: 'InvokeRetrieve(apiObject[, @statusMessage, @requestId])',
3582
3777
  example: '%%[ SET @rows = InvokeRetrieve(@apiObject, @statusMessage, @requestId) ]%%',
3583
3778
  isConfirmed: true,
3779
+ differsFromOfficialDocs: true,
3780
+ officialDocsNote:
3781
+ 'Email/send-context finding: the WSProxy object model is not valid in sendable email content. Rendered through the Email Preview API against a seeded sendable row, an isolated CreateObject(...) was rejected with HTTP 400 errorcode 10004 ("CreateObject Function is not valid in content. This function is only allowed in non sendable content."). Because this function is part of that object model (or depends on a CreateObject request object), it is a CloudPage / landing-page (non-sendable content) feature and cannot be used inside a sendable email.',
3584
3782
  },
3585
3783
  {
3586
3784
  name: 'InvokeUpdate',
3785
+ supportedInCloudPage: true,
3786
+ supportedInEmail: false,
3587
3787
  mcnSince: null,
3588
3788
  handlebarsEquivalent: null,
3589
3789
  mcnNotes: null,
@@ -3628,9 +3828,14 @@ export const FUNCTIONS = [
3628
3828
  syntax: 'InvokeUpdate(apiObject[, @statusMessage, @errorCode, updateOptions])',
3629
3829
  example: '%%=InvokeUpdate(@apiObject, @statusMessage, @errorCode)=%%',
3630
3830
  isConfirmed: true,
3831
+ differsFromOfficialDocs: true,
3832
+ officialDocsNote:
3833
+ 'Email/send-context finding: the WSProxy object model is not valid in sendable email content. Rendered through the Email Preview API against a seeded sendable row, an isolated CreateObject(...) was rejected with HTTP 400 errorcode 10004 ("CreateObject Function is not valid in content. This function is only allowed in non sendable content."). Because this function is part of that object model (or depends on a CreateObject request object), it is a CloudPage / landing-page (non-sendable content) feature and cannot be used inside a sendable email.',
3631
3834
  },
3632
3835
  {
3633
3836
  name: 'IsCHTMLBrowser',
3837
+ supportedInCloudPage: true,
3838
+ supportedInEmail: false,
3634
3839
  mcnSince: null,
3635
3840
  handlebarsEquivalent: null,
3636
3841
  mcnNotes: null,
@@ -3640,10 +3845,12 @@ export const FUNCTIONS = [
3640
3845
  minArgs: 1,
3641
3846
  maxArgs: 1,
3642
3847
  isConfirmed: true,
3643
- differsFromOfficialDocs: false,
3848
+ differsFromOfficialDocs: true,
3849
+ officialDocsNote:
3850
+ 'The official reference documents this as an AMPscript function without noting that it is restricted to non-sendable content. Email/send-context finding: rendered through the Email Preview API against a seeded sendable row, an isolated IsCHTMLBrowser("DoCoMo/2.0 N905i") was rejected with HTTP 400 errorcode 10004 ("IsCHTMLBrowser Function is not valid in content. This function is only allowed in non sendable content."). So it works only in non-sendable content (CloudPages / landing pages) and cannot be used inside a sendable email, which fits its purpose since a user-agent is a request-time value absent at send time.',
3644
3851
  category: 'Utility',
3645
3852
  description:
3646
- 'Tests a user agent string for a compact HTML (cHTML) feature-phone browser. Feature-phone agents such as i-mode and KDDI handsets are recognised; modern desktop and mobile agents are not.',
3853
+ 'Tests a user agent string for a compact HTML (cHTML) feature-phone browser. Feature-phone agents such as i-mode and KDDI handsets are recognised; modern desktop and mobile agents are not. Only valid in non-sendable content (CloudPages / landing pages), not in sendable email.',
3647
3854
  params: [
3648
3855
  {
3649
3856
  name: 'userAgent',
@@ -3660,6 +3867,8 @@ export const FUNCTIONS = [
3660
3867
  },
3661
3868
  {
3662
3869
  name: 'IsEmailAddress',
3870
+ supportedInCloudPage: true,
3871
+ supportedInEmail: true,
3663
3872
  mcnSince: null,
3664
3873
  handlebarsEquivalent: null,
3665
3874
  mcnNotes: null,
@@ -3671,7 +3880,7 @@ export const FUNCTIONS = [
3671
3880
  isConfirmed: true,
3672
3881
  differsFromOfficialDocs: true,
3673
3882
  officialDocsNote:
3674
- 'The official reference states that an address whose domain has no top-level domain is accepted, giving a call on a bare single-label domain as an example of a true result. On a live Engagement CloudPage on the child business unit (MID 518005426) that shape returned False, in a gate that printed its own start and done markers at HTTP 200 alongside a known-good control block. Every other example in the same table matched: the missing at sign, the double at sign, the missing local part and the missing second-level domain all returned False, and a well-formed address returned True. Surrounding whitespace is also rejected, which no source mentions.',
3883
+ 'The official reference states that an address whose domain has no top-level domain is accepted, giving a call on a bare single-label domain as an example of a true result. On a live Engagement CloudPage on the child business unit that shape returned False, in a gate that printed its own start and done markers at HTTP 200 alongside a known-good control block. Every other example in the same table matched: the missing at sign, the double at sign, the missing local part and the missing second-level domain all returned False, and a well-formed address returned True. Surrounding whitespace is also rejected, which no source mentions.',
3675
3884
  category: 'Utility',
3676
3885
  description:
3677
3886
  'Checks a value against email address syntax only; it never tests whether the mailbox or domain exists. Surrounding whitespace and a domain without a top-level domain are both rejected.',
@@ -3692,6 +3901,8 @@ export const FUNCTIONS = [
3692
3901
  },
3693
3902
  {
3694
3903
  name: 'IsNull',
3904
+ supportedInCloudPage: true,
3905
+ supportedInEmail: true,
3695
3906
  mcnSince: 67,
3696
3907
  handlebarsEquivalent: 'isEmpty',
3697
3908
  handlebarsExact: false,
@@ -3718,12 +3929,14 @@ export const FUNCTIONS = [
3718
3929
  isConfirmed: true,
3719
3930
  differsFromOfficialDocs: true,
3720
3931
  officialDocsNote:
3721
- 'The official reference shows a variable declared with VAR and never assigned, and states IsNull returns true for it. On a live Engagement CloudPage on the child business unit (MID 518005426) that exact shape returned False, in a gate that printed its own start and done markers at HTTP 200 alongside a known-good control block. The same False came back for an undeclared variable, an empty string, whitespace, 0, "0", "false", a real value, a date, an absent attribute, an absent request parameter and the subscriber-context tokens. Use Empty for a missing-value test.',
3932
+ 'The official reference shows a variable declared with VAR and never assigned, and states IsNull returns true for it. On a live Engagement CloudPage on the child business unit that exact shape returned False, in a gate that printed its own start and done markers at HTTP 200 alongside a known-good control block. The same False came back for an undeclared variable, an empty string, whitespace, 0, "0", "false", a real value, a date, an absent attribute, an absent request parameter and the subscriber-context tokens. Use Empty for a missing-value test.',
3722
3933
  syntax: 'IsNull(value)',
3723
3934
  example: '%%=IsNull(@value)=%%',
3724
3935
  },
3725
3936
  {
3726
3937
  name: 'IsNullDefault',
3938
+ supportedInCloudPage: true,
3939
+ supportedInEmail: true,
3727
3940
  mcnSince: null,
3728
3941
  handlebarsEquivalent: 'fallback',
3729
3942
  handlebarsExact: false,
@@ -3757,6 +3970,8 @@ export const FUNCTIONS = [
3757
3970
  },
3758
3971
  {
3759
3972
  name: 'IsPhoneNumber',
3973
+ supportedInCloudPage: true,
3974
+ supportedInEmail: true,
3760
3975
  mcnSince: null,
3761
3976
  handlebarsEquivalent: null,
3762
3977
  mcnNotes: null,
@@ -3786,6 +4001,8 @@ export const FUNCTIONS = [
3786
4001
  },
3787
4002
  {
3788
4003
  name: 'Length',
4004
+ supportedInCloudPage: true,
4005
+ supportedInEmail: true,
3789
4006
  mcnSince: 67,
3790
4007
  handlebarsEquivalent: 'length',
3791
4008
  handlebarsExact: true,
@@ -3814,6 +4031,8 @@ export const FUNCTIONS = [
3814
4031
  },
3815
4032
  {
3816
4033
  name: 'LiveContentMicrositeURL',
4034
+ supportedInCloudPage: false,
4035
+ supportedInEmail: false,
3817
4036
  mcnSince: null,
3818
4037
  handlebarsEquivalent: null,
3819
4038
  mcnNotes: null,
@@ -3829,7 +4048,7 @@ export const FUNCTIONS = [
3829
4048
  deprecatedReason:
3830
4049
  'Live Offers (Live Content) was removed from Marketing Cloud in 2019 and the Classic Microsites this URL points at were retired in June 2022, so there is no provisionable modern equivalent and every invocation aborts the page at runtime.',
3831
4050
  officialDocsNote:
3832
- "Attempted on both the child QA BU (MID 518005426) and the parent BU (MID 7281698). Every invocation shape aborted the CloudPage with HTTP 200 lost to a 422 page abort: the documented-valid LiveContentMicrositeURL('coupon','MyCoupon'), an unknown content type, and an empty external key all failed identically. The function resolves a Live Offers (Live Content) coupon by external key, and no such Live Content asset is provisioned on either BU, so no working invocation could be produced. Left blocked pending a tenant with a real Live Offers coupon.",
4051
+ "Attempted on both the child BU and the parent BU. Every invocation shape aborted the CloudPage with HTTP 200 lost to a 422 page abort: the documented-valid LiveContentMicrositeURL('coupon','MyCoupon'), an unknown content type, and an empty external key all failed identically. The function resolves a Live Offers (Live Content) coupon by external key, and no such Live Content asset is provisioned on either BU, so no working invocation could be produced. Left blocked pending a tenant with a real Live Offers coupon.",
3833
4052
  params: [
3834
4053
  {
3835
4054
  name: 'contentType',
@@ -3851,6 +4070,8 @@ export const FUNCTIONS = [
3851
4070
  },
3852
4071
  {
3853
4072
  name: 'LocalDateToSystemDate',
4073
+ supportedInCloudPage: true,
4074
+ supportedInEmail: true,
3854
4075
  mcnSince: null,
3855
4076
  handlebarsEquivalent: 'timeZoneConversion',
3856
4077
  handlebarsExact: false,
@@ -3881,6 +4102,8 @@ export const FUNCTIONS = [
3881
4102
  },
3882
4103
  {
3883
4104
  name: 'LongSFID',
4105
+ supportedInCloudPage: true,
4106
+ supportedInEmail: true,
3884
4107
  mcnSince: null,
3885
4108
  handlebarsEquivalent: null,
3886
4109
  mcnNotes: null,
@@ -3902,6 +4125,8 @@ export const FUNCTIONS = [
3902
4125
  },
3903
4126
  {
3904
4127
  name: 'Lookup',
4128
+ supportedInCloudPage: true,
4129
+ supportedInEmail: true,
3905
4130
  mcnSince: 67,
3906
4131
  handlebarsEquivalent: 'queryFirst',
3907
4132
  handlebarsExact: false,
@@ -3953,6 +4178,8 @@ export const FUNCTIONS = [
3953
4178
  },
3954
4179
  {
3955
4180
  name: 'LookupOrderedRows',
4181
+ supportedInCloudPage: true,
4182
+ supportedInEmail: true,
3956
4183
  mcnSince: null,
3957
4184
  handlebarsEquivalent: 'query',
3958
4185
  handlebarsExact: false,
@@ -4011,6 +4238,8 @@ export const FUNCTIONS = [
4011
4238
  },
4012
4239
  {
4013
4240
  name: 'LookupOrderedRowsCS',
4241
+ supportedInCloudPage: true,
4242
+ supportedInEmail: true,
4014
4243
  mcnSince: null,
4015
4244
  handlebarsEquivalent: 'query',
4016
4245
  handlebarsExact: false,
@@ -4068,6 +4297,8 @@ export const FUNCTIONS = [
4068
4297
  },
4069
4298
  {
4070
4299
  name: 'LookupRows',
4300
+ supportedInCloudPage: true,
4301
+ supportedInEmail: true,
4071
4302
  mcnSince: null,
4072
4303
  handlebarsEquivalent: 'query',
4073
4304
  handlebarsExact: false,
@@ -4111,6 +4342,8 @@ export const FUNCTIONS = [
4111
4342
  },
4112
4343
  {
4113
4344
  name: 'LookupRowsCS',
4345
+ supportedInCloudPage: true,
4346
+ supportedInEmail: true,
4114
4347
  mcnSince: null,
4115
4348
  handlebarsEquivalent: 'query',
4116
4349
  handlebarsExact: false,
@@ -4154,6 +4387,8 @@ export const FUNCTIONS = [
4154
4387
  },
4155
4388
  {
4156
4389
  name: 'Lowercase',
4390
+ supportedInCloudPage: true,
4391
+ supportedInEmail: true,
4157
4392
  mcnSince: 67,
4158
4393
  handlebarsEquivalent: 'lowercase',
4159
4394
  handlebarsExact: true,
@@ -4181,6 +4416,8 @@ export const FUNCTIONS = [
4181
4416
  },
4182
4417
  {
4183
4418
  name: 'MD5',
4419
+ supportedInCloudPage: true,
4420
+ supportedInEmail: true,
4184
4421
  mcnSince: null,
4185
4422
  handlebarsEquivalent: null,
4186
4423
  mcnNotes: null,
@@ -4220,6 +4457,8 @@ export const FUNCTIONS = [
4220
4457
  },
4221
4458
  {
4222
4459
  name: 'MMS_Content_URL',
4460
+ supportedInCloudPage: false,
4461
+ supportedInEmail: false,
4223
4462
  mcnSince: null,
4224
4463
  handlebarsEquivalent: null,
4225
4464
  mcnNotes: null,
@@ -4234,7 +4473,7 @@ export const FUNCTIONS = [
4234
4473
  verificationBlocked: true,
4235
4474
  verificationBlockedReason: 'no-working-invocation',
4236
4475
  officialDocsNote:
4237
- 'Could not runtime-verify on the only available context (a CloudPage GET on cred/DEV, MID 510007949; no parent-BU escalation is configured on this tenant). Including an MMS_Content_URL(0) call in the injected content block aborted the whole page at compile time (HTTP 422) even when the call sat inside a non-matching IF branch, while an otherwise identical page with the call removed rendered HTTP 200. This matches the official reference, which states the function is usable only in MobileConnect and not in landing pages or other content types; there is no mobile-originated message context on a CloudPage to exercise it against.',
4476
+ 'Could not runtime-verify on the only available context (a CloudPage GET on the child BU; no parent-BU escalation is configured on this tenant). Including an MMS_Content_URL(0) call in the injected content block aborted the whole page at compile time (HTTP 422) even when the call sat inside a non-matching IF branch, while an otherwise identical page with the call removed rendered HTTP 200. This matches the official reference, which states the function is usable only in MobileConnect and not in landing pages or other content types; there is no mobile-originated message context on a CloudPage to exercise it against.',
4238
4477
  params: [
4239
4478
  {
4240
4479
  name: 'position',
@@ -4250,6 +4489,8 @@ export const FUNCTIONS = [
4250
4489
  },
4251
4490
  {
4252
4491
  name: 'MicrositeURL',
4492
+ supportedInCloudPage: true,
4493
+ supportedInEmail: true,
4253
4494
  mcnSince: null,
4254
4495
  handlebarsEquivalent: null,
4255
4496
  mcnNotes: null,
@@ -4299,6 +4540,8 @@ export const FUNCTIONS = [
4299
4540
  },
4300
4541
  {
4301
4542
  name: 'Mod',
4543
+ supportedInCloudPage: true,
4544
+ supportedInEmail: true,
4302
4545
  mcnSince: 67,
4303
4546
  handlebarsEquivalent: 'modulo',
4304
4547
  handlebarsExact: true,
@@ -4325,6 +4568,8 @@ export const FUNCTIONS = [
4325
4568
  },
4326
4569
  {
4327
4570
  name: 'Msg',
4571
+ supportedInCloudPage: false,
4572
+ supportedInEmail: false,
4328
4573
  mcnSince: null,
4329
4574
  handlebarsEquivalent: null,
4330
4575
  mcnNotes: null,
@@ -4339,7 +4584,7 @@ export const FUNCTIONS = [
4339
4584
  verificationBlocked: true,
4340
4585
  verificationBlockedReason: 'no-working-invocation',
4341
4586
  officialDocsNote:
4342
- 'Could not runtime-verify on the only available context (a CloudPage GET on cred/DEV, MID 510007949; no parent-BU escalation is configured on this tenant). A page containing a Msg(0) call aborted at compile time (HTTP 422) even when the call sat inside a non-matching IF branch, whereas the same page with no Msg construct rendered HTTP 200 — so the abort happens at parse time, before any runtime gate. This matches the official reference, which states the function is usable only in MobileConnect and not in landing pages or other content types; a CloudPage supplies no mobile-originated message to read.',
4587
+ 'Could not runtime-verify on the only available context (a CloudPage GET on the child BU; no parent-BU escalation is configured on this tenant). A page containing a Msg(0) call aborted at compile time (HTTP 422) even when the call sat inside a non-matching IF branch, whereas the same page with no Msg construct rendered HTTP 200 — so the abort happens at parse time, before any runtime gate. This matches the official reference, which states the function is usable only in MobileConnect and not in landing pages or other content types; a CloudPage supplies no mobile-originated message to read.',
4343
4588
  params: [
4344
4589
  {
4345
4590
  name: 'index',
@@ -4354,6 +4599,8 @@ export const FUNCTIONS = [
4354
4599
  },
4355
4600
  {
4356
4601
  name: 'Multiply',
4602
+ supportedInCloudPage: true,
4603
+ supportedInEmail: true,
4357
4604
  mcnSince: 67,
4358
4605
  handlebarsEquivalent: 'multiply',
4359
4606
  handlebarsExact: true,
@@ -4378,6 +4625,8 @@ export const FUNCTIONS = [
4378
4625
  },
4379
4626
  {
4380
4627
  name: 'Noun',
4628
+ supportedInCloudPage: false,
4629
+ supportedInEmail: false,
4381
4630
  mcnSince: null,
4382
4631
  handlebarsEquivalent: null,
4383
4632
  mcnNotes: null,
@@ -4392,7 +4641,7 @@ export const FUNCTIONS = [
4392
4641
  verificationBlocked: true,
4393
4642
  verificationBlockedReason: 'no-working-invocation',
4394
4643
  officialDocsNote:
4395
- 'Could not runtime-verify on the only available context (a CloudPage GET on cred/DEV, MID 510007949; no parent-BU escalation on this tenant). Noun is chained off Msg(0), and any page containing a Msg(0) construct aborts at compile time (HTTP 422) on a CloudPage while an otherwise identical page without it renders HTTP 200. This matches the official reference, which restricts the function to MobileConnect and forbids landing pages / other content types; a CloudPage supplies no mobile-originated message to parse.',
4644
+ 'Could not runtime-verify on the only available context (a CloudPage GET on the child BU; no parent-BU escalation on this tenant). Noun is chained off Msg(0), and any page containing a Msg(0) construct aborts at compile time (HTTP 422) on a CloudPage while an otherwise identical page without it renders HTTP 200. This matches the official reference, which restricts the function to MobileConnect and forbids landing pages / other content types; a CloudPage supplies no mobile-originated message to parse.',
4396
4645
  params: [
4397
4646
  {
4398
4647
  name: 'position',
@@ -4408,6 +4657,8 @@ export const FUNCTIONS = [
4408
4657
  },
4409
4658
  {
4410
4659
  name: 'Nouns',
4660
+ supportedInCloudPage: false,
4661
+ supportedInEmail: false,
4411
4662
  mcnSince: null,
4412
4663
  handlebarsEquivalent: null,
4413
4664
  mcnNotes: null,
@@ -4422,7 +4673,7 @@ export const FUNCTIONS = [
4422
4673
  verificationBlocked: true,
4423
4674
  verificationBlockedReason: 'no-working-invocation',
4424
4675
  officialDocsNote:
4425
- 'Could not runtime-verify on the only available context (a CloudPage GET on cred/DEV, MID 510007949; no parent-BU escalation on this tenant). Nouns is chained off Msg(0), and any page containing a Msg(0) construct aborts at compile time (HTTP 422) on a CloudPage while an otherwise identical page without it renders HTTP 200. This matches the official reference, which restricts the function to MobileConnect and forbids landing pages / other content types; a CloudPage supplies no mobile-originated message to parse.',
4676
+ 'Could not runtime-verify on the only available context (a CloudPage GET on the child BU; no parent-BU escalation on this tenant). Nouns is chained off Msg(0), and any page containing a Msg(0) construct aborts at compile time (HTTP 422) on a CloudPage while an otherwise identical page without it renders HTTP 200. This matches the official reference, which restricts the function to MobileConnect and forbids landing pages / other content types; a CloudPage supplies no mobile-originated message to parse.',
4426
4677
  params: [],
4427
4678
  returnType: 'string',
4428
4679
  returnDescription: 'All content that follows the keyword in the inbound message.',
@@ -4431,6 +4682,8 @@ export const FUNCTIONS = [
4431
4682
  },
4432
4683
  {
4433
4684
  name: 'Now',
4685
+ supportedInCloudPage: true,
4686
+ supportedInEmail: true,
4434
4687
  mcnSince: 67,
4435
4688
  handlebarsEquivalent: 'now',
4436
4689
  handlebarsExact: false,
@@ -4464,6 +4717,8 @@ export const FUNCTIONS = [
4464
4717
  },
4465
4718
  {
4466
4719
  name: 'Output',
4720
+ supportedInCloudPage: true,
4721
+ supportedInEmail: false,
4467
4722
  mcnSince: 67,
4468
4723
  handlebarsEquivalent: null,
4469
4724
  mcnNotes: null,
@@ -4471,7 +4726,7 @@ export const FUNCTIONS = [
4471
4726
  guideUrl: 'https://ampscript.guide/output/',
4472
4727
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/output/',
4473
4728
  minArgs: 0,
4474
- maxArgs: Infinity,
4729
+ maxArgs: INF,
4475
4730
  category: 'Utility',
4476
4731
  description:
4477
4732
  'Writes the result of a nested function call into the rendered content. A string literal, a bare variable or a number renders nothing at all, without raising an error.',
@@ -4480,20 +4735,30 @@ export const FUNCTIONS = [
4480
4735
  name: 'content',
4481
4736
  description:
4482
4737
  'Function call whose result is written; a literal or bare variable renders nothing',
4738
+ optional: true,
4739
+ },
4740
+ {
4741
+ name: 'contentN',
4742
+ description:
4743
+ 'Additional function call whose result is written in turn; a literal or bare variable renders nothing',
4744
+ optional: true,
4483
4745
  },
4484
4746
  ],
4485
4747
  returnType: 'void',
4486
4748
  returnDescription:
4487
4749
  'No value is returned, so the call cannot be nested inside another function; the result is written straight into the rendered content.',
4488
- syntax: 'Output(content)',
4750
+ repeat: [{ startIndex: 0, groupSize: 1, minGroups: 0 }],
4751
+ syntax: 'Output([content, ...])',
4489
4752
  example: "%%=Output(Concat('Hello ', @firstName))=%%",
4490
4753
  isConfirmed: true,
4491
4754
  differsFromOfficialDocs: true,
4492
4755
  officialDocsNote:
4493
- 'The official reference states that a value which is not a function call, such as a string literal, makes the function return an error. On a live Engagement CloudPage on the child business unit (MID 518005426) a literal argument, a bare variable and a bare number each rendered nothing at all while the page still returned HTTP 200 and every surrounding marker printed, so no error surfaced anywhere. The same page also accepted zero arguments and up to three arguments, writing each one in turn.',
4756
+ 'The official reference states that a value which is not a function call, such as a string literal, makes the function return an error. On a live Engagement CloudPage on the child business unit a literal argument, a bare variable and a bare number each rendered nothing at all while the page still returned HTTP 200 and every surrounding marker printed, so no error surfaced anywhere. The same page also accepted zero arguments and up to three arguments, writing each one in turn.',
4494
4757
  },
4495
4758
  {
4496
4759
  name: 'OutputLine',
4760
+ supportedInCloudPage: true,
4761
+ supportedInEmail: true,
4497
4762
  mcnSince: 67,
4498
4763
  handlebarsEquivalent: null,
4499
4764
  mcnNotes: null,
@@ -4501,7 +4766,7 @@ export const FUNCTIONS = [
4501
4766
  guideUrl: 'https://ampscript.guide/outputline/',
4502
4767
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/outputline/',
4503
4768
  minArgs: 0,
4504
- maxArgs: Infinity,
4769
+ maxArgs: INF,
4505
4770
  category: 'Utility',
4506
4771
  description:
4507
4772
  'Writes the result of a nested function call into the rendered content, followed by a carriage return and line feed. A string literal, a bare variable or a number renders only the line break. The break is not an HTML line break, so an HTML view keeps everything on one line unless the content sits inside a preformatted element.',
@@ -4510,18 +4775,28 @@ export const FUNCTIONS = [
4510
4775
  name: 'content',
4511
4776
  description:
4512
4777
  'Function call whose result is written; a literal or bare variable renders only the line break',
4778
+ optional: true,
4779
+ },
4780
+ {
4781
+ name: 'contentN',
4782
+ description:
4783
+ 'Additional function call whose result is written in turn before the single trailing line break; a literal or bare variable renders only the line break',
4784
+ optional: true,
4513
4785
  },
4514
4786
  ],
4515
4787
  returnType: 'void',
4516
4788
  returnDescription:
4517
4789
  'No value is returned, so the call cannot be nested inside another function; the result and a carriage return plus line feed are written straight into the rendered content.',
4518
- syntax: 'OutputLine(content)',
4790
+ repeat: [{ startIndex: 0, groupSize: 1, minGroups: 0 }],
4791
+ syntax: 'OutputLine([content, ...])',
4519
4792
  example: "%%=OutputLine(Concat('Hello ', @firstName))=%%",
4520
4793
  isConfirmed: true,
4521
4794
  differsFromOfficialDocs: false,
4522
4795
  },
4523
4796
  {
4524
4797
  name: 'ProperCase',
4798
+ supportedInCloudPage: true,
4799
+ supportedInEmail: true,
4525
4800
  mcnSince: 67,
4526
4801
  handlebarsEquivalent: 'properCase',
4527
4802
  handlebarsExact: true,
@@ -4547,6 +4822,8 @@ export const FUNCTIONS = [
4547
4822
  },
4548
4823
  {
4549
4824
  name: 'QueryParameter',
4825
+ supportedInCloudPage: true,
4826
+ supportedInEmail: true,
4550
4827
  mcnSince: null,
4551
4828
  handlebarsEquivalent: null,
4552
4829
  mcnNotes: null,
@@ -4574,6 +4851,8 @@ export const FUNCTIONS = [
4574
4851
  },
4575
4852
  {
4576
4853
  name: 'RaiseError',
4854
+ supportedInCloudPage: true,
4855
+ supportedInEmail: true,
4577
4856
  mcnSince: 67,
4578
4857
  handlebarsEquivalent: 'raiseError',
4579
4858
  handlebarsExact: false,
@@ -4633,6 +4912,8 @@ export const FUNCTIONS = [
4633
4912
  },
4634
4913
  {
4635
4914
  name: 'Random',
4915
+ supportedInCloudPage: true,
4916
+ supportedInEmail: true,
4636
4917
  mcnSince: 67,
4637
4918
  handlebarsEquivalent: 'random',
4638
4919
  handlebarsExact: true,
@@ -4656,10 +4937,12 @@ export const FUNCTIONS = [
4656
4937
  isConfirmed: true,
4657
4938
  differsFromOfficialDocs: true,
4658
4939
  officialDocsNote:
4659
- 'The official reference states the bounds may be decimal numbers. On the child QA BU (MID 518005426) every decimal bound aborted the CloudPage with HTTP 422 — Random(1.2,1.8), Random(1,2.5), Random(1.0,3.0) and the quoted form Random("1.5","3.5") all failed, while the equivalent whole-number and numeric-string calls returned values normally. The same decimal calls also aborted on the parent BU (MID 7281698), so this is not a child-BU limitation. Only whole-number bounds are usable at runtime.',
4940
+ 'The official reference states the bounds may be decimal numbers. On the child BU every decimal bound aborted the CloudPage with HTTP 422 — Random(1.2,1.8), Random(1,2.5), Random(1.0,3.0) and the quoted form Random("1.5","3.5") all failed, while the equivalent whole-number and numeric-string calls returned values normally. The same decimal calls also aborted on the parent BU, so this is not a child-BU limitation. Only whole-number bounds are usable at runtime.',
4660
4941
  },
4661
4942
  {
4662
4943
  name: 'RatingStars',
4944
+ supportedInCloudPage: false,
4945
+ supportedInEmail: false,
4663
4946
  mcnSince: null,
4664
4947
  handlebarsEquivalent: null,
4665
4948
  mcnNotes: null,
@@ -4681,10 +4964,12 @@ export const FUNCTIONS = [
4681
4964
  verificationBlocked: true,
4682
4965
  verificationBlockedReason: 'no-test-data',
4683
4966
  officialDocsNote:
4684
- 'No working CloudPage invocation was found. Any valid-arity call aborts the whole page with HTTP 422 at compile time, even when placed inside an unreached IF gate, so it cannot be probed behind a query-string switch. Two signature shapes were each deployed as the whole page: the catalog form RatingStars(4, 5, "https://example.com/star.png") and the ampscript.guide form RatingStars(5, "yellow", 25). Both returned HTTP 422 on the child BU (MID 518005426) and again on the parent BU (MID 7281698). The surrounding harness structure (RequestParameter gating, IF/ELSE/ENDIF) returned HTTP 200 once the RatingStars call was removed, confirming the abort is caused by the function itself, not the harness. RatingStars is an Einstein Email Recommendations helper that appears to resolve only inside the recommendations rendering context, which a bare CloudPage does not supply.',
4967
+ 'No working CloudPage invocation was found. Any valid-arity call aborts the whole page with HTTP 422 at compile time, even when placed inside an unreached IF gate, so it cannot be probed behind a query-string switch. Two signature shapes were each deployed as the whole page: the catalog form RatingStars(4, 5, "https://example.com/star.png") and the ampscript.guide form RatingStars(5, "yellow", 25). Both returned HTTP 422 on the child BU and again on the parent BU. The surrounding harness structure (RequestParameter gating, IF/ELSE/ENDIF) returned HTTP 200 once the RatingStars call was removed, confirming the abort is caused by the function itself, not the harness. RatingStars is an Einstein Email Recommendations helper that appears to resolve only inside the recommendations rendering context, which a bare CloudPage does not supply.',
4685
4968
  },
4686
4969
  {
4687
4970
  name: 'Redirect',
4971
+ supportedInCloudPage: true,
4972
+ supportedInEmail: false,
4688
4973
  mcnSince: null,
4689
4974
  handlebarsEquivalent: null,
4690
4975
  mcnNotes: null,
@@ -4703,10 +4988,14 @@ export const FUNCTIONS = [
4703
4988
  syntax: 'Redirect(url)',
4704
4989
  example: "Redirect('https://example.com')",
4705
4990
  isConfirmed: true,
4706
- differsFromOfficialDocs: false,
4991
+ differsFromOfficialDocs: true,
4992
+ officialDocsNote:
4993
+ 'Email/send-context finding: Redirect is not valid in sendable email content. Rendered through the Email Preview API against a seeded sendable row, an isolated Redirect("https://sfmc.guide/robots.txt") was rejected with HTTP 400 errorcode 10005 ("Redirect Function is not valid in content. This function is only allowed in in content with an HTTP context."). It is a CloudPage / landing-page (non-sendable, HTTP-context) feature that emits a 302, and cannot be used inside a sendable email, where there is no HTTP response to redirect.',
4707
4994
  },
4708
4995
  {
4709
4996
  name: 'RedirectTo',
4997
+ supportedInCloudPage: true,
4998
+ supportedInEmail: true,
4710
4999
  mcnSince: null,
4711
5000
  handlebarsEquivalent: null,
4712
5001
  mcnNotes: null,
@@ -4729,6 +5018,8 @@ export const FUNCTIONS = [
4729
5018
  },
4730
5019
  {
4731
5020
  name: 'RegExMatch',
5021
+ supportedInCloudPage: true,
5022
+ supportedInEmail: true,
4732
5023
  mcnSince: null,
4733
5024
  handlebarsEquivalent: null,
4734
5025
  mcnNotes: null,
@@ -4738,7 +5029,7 @@ export const FUNCTIONS = [
4738
5029
  isConfirmed: true,
4739
5030
  differsFromOfficialDocs: false,
4740
5031
  minArgs: 3,
4741
- maxArgs: Infinity,
5032
+ maxArgs: INF,
4742
5033
  category: 'String',
4743
5034
  description:
4744
5035
  'Returns the first occurrence of a regular expression match in a string, selected by capture group. Matching is case-sensitive unless the IgnoreCase option is passed.',
@@ -4776,6 +5067,7 @@ export const FUNCTIONS = [
4776
5067
  returnType: 'string',
4777
5068
  returnDescription:
4778
5069
  'The text of the selected capture group, or an empty string when the pattern does not match or the group does not exist.',
5070
+ repeat: [{ startIndex: 3, groupSize: 1, minGroups: 0 }],
4779
5071
  syntax: 'RegExMatch(sourceString, regExPattern, returnValue[, regExOptions, ...])',
4780
5072
  example:
4781
5073
  'Var @couponCode, @regEx, @regExMatch\n' +
@@ -4785,6 +5077,8 @@ export const FUNCTIONS = [
4785
5077
  },
4786
5078
  {
4787
5079
  name: 'Replace',
5080
+ supportedInCloudPage: true,
5081
+ supportedInEmail: true,
4788
5082
  mcnSince: 67,
4789
5083
  handlebarsEquivalent: 'replace',
4790
5084
  handlebarsExact: false,
@@ -4817,6 +5111,8 @@ export const FUNCTIONS = [
4817
5111
  },
4818
5112
  {
4819
5113
  name: 'ReplaceList',
5114
+ supportedInCloudPage: true,
5115
+ supportedInEmail: true,
4820
5116
  mcnSince: 67,
4821
5117
  handlebarsEquivalent: null,
4822
5118
  mcnNotes: null,
@@ -4850,6 +5146,8 @@ export const FUNCTIONS = [
4850
5146
  },
4851
5147
  {
4852
5148
  name: 'RequestParameter',
5149
+ supportedInCloudPage: true,
5150
+ supportedInEmail: true,
4853
5151
  mcnSince: null,
4854
5152
  handlebarsEquivalent: null,
4855
5153
  mcnNotes: null,
@@ -4877,6 +5175,8 @@ export const FUNCTIONS = [
4877
5175
  },
4878
5176
  {
4879
5177
  name: 'RetrieveMSCRMRecords',
5178
+ supportedInCloudPage: false,
5179
+ supportedInEmail: false,
4880
5180
  mcnSince: null,
4881
5181
  handlebarsEquivalent: null,
4882
5182
  mcnNotes: null,
@@ -4925,6 +5225,8 @@ export const FUNCTIONS = [
4925
5225
  },
4926
5226
  {
4927
5227
  name: 'RetrieveMSCRMRecordsFetchXML',
5228
+ supportedInCloudPage: false,
5229
+ supportedInEmail: false,
4928
5230
  mcnSince: null,
4929
5231
  handlebarsEquivalent: null,
4930
5232
  mcnNotes: null,
@@ -4947,6 +5249,8 @@ export const FUNCTIONS = [
4947
5249
  },
4948
5250
  {
4949
5251
  name: 'RetrieveSalesforceJobSources',
5252
+ supportedInCloudPage: true,
5253
+ supportedInEmail: true,
4950
5254
  mcnSince: null,
4951
5255
  handlebarsEquivalent: null,
4952
5256
  mcnNotes: null,
@@ -4976,6 +5280,8 @@ export const FUNCTIONS = [
4976
5280
  },
4977
5281
  {
4978
5282
  name: 'RetrieveSalesforceObjects',
5283
+ supportedInCloudPage: true,
5284
+ supportedInEmail: true,
4979
5285
  mcnSince: 67,
4980
5286
  handlebarsEquivalent: 'query',
4981
5287
  handlebarsExact: false,
@@ -5042,6 +5348,8 @@ export const FUNCTIONS = [
5042
5348
  },
5043
5349
  {
5044
5350
  name: 'Row',
5351
+ supportedInCloudPage: true,
5352
+ supportedInEmail: true,
5045
5353
  mcnSince: 67,
5046
5354
  handlebarsEquivalent: 'get',
5047
5355
  handlebarsExact: false,
@@ -5067,6 +5375,8 @@ export const FUNCTIONS = [
5067
5375
  },
5068
5376
  {
5069
5377
  name: 'RowCount',
5378
+ supportedInCloudPage: true,
5379
+ supportedInEmail: true,
5070
5380
  mcnSince: 67,
5071
5381
  handlebarsEquivalent: 'length',
5072
5382
  handlebarsExact: false,
@@ -5088,6 +5398,8 @@ export const FUNCTIONS = [
5088
5398
  },
5089
5399
  {
5090
5400
  name: 'SetObjectProperty',
5401
+ supportedInCloudPage: true,
5402
+ supportedInEmail: false,
5091
5403
  mcnSince: null,
5092
5404
  handlebarsEquivalent: null,
5093
5405
  mcnNotes: null,
@@ -5116,9 +5428,14 @@ export const FUNCTIONS = [
5116
5428
  syntax: 'SetObjectProperty(apiObject, propertyName, propertyValue)',
5117
5429
  example: "SetObjectProperty(@apiObject, 'LastName', 'Smith')",
5118
5430
  isConfirmed: true,
5431
+ differsFromOfficialDocs: true,
5432
+ officialDocsNote:
5433
+ 'Email/send-context finding: the WSProxy object model is not valid in sendable email content. Rendered through the Email Preview API against a seeded sendable row, an isolated CreateObject(...) was rejected with HTTP 400 errorcode 10004 ("CreateObject Function is not valid in content. This function is only allowed in non sendable content."). Because this function is part of that object model (or depends on a CreateObject request object), it is a CloudPage / landing-page (non-sendable content) feature and cannot be used inside a sendable email.',
5119
5434
  },
5120
5435
  {
5121
5436
  name: 'SetSmsConversationNextKeyword',
5437
+ supportedInCloudPage: true,
5438
+ supportedInEmail: true,
5122
5439
  mcnSince: null,
5123
5440
  handlebarsEquivalent: null,
5124
5441
  mcnNotes: null,
@@ -5129,12 +5446,10 @@ export const FUNCTIONS = [
5129
5446
  category: 'MobileConnect',
5130
5447
  description:
5131
5448
  'Sets the keyword for the next path of an existing SMS conversation, applied when the contact next replies. Does not create a new conversation. Returns true when set inside a MobileConnect message context, and false in any other context (for example a CloudPage or email). The success path cannot be exercised outside a live MobileConnect send.',
5132
- isConfirmed: false,
5133
- verificationBlocked: true,
5134
- verificationBlockedReason: 'no-working-invocation',
5449
+ isConfirmed: true,
5135
5450
  differsFromOfficialDocs: true,
5136
5451
  officialDocsNote:
5137
- 'Runtime-observed on cred/DEV (MID 510007949), the only BU available (no parent-BU escalation). This is an ordinary function call, so it compiles and runs on a CloudPage: called there with a real short code, the authorized destination number and a keyword, it returned the literal boolean false (Empty() false) and the page rendered fully with no exception — no SMS was sent and no conversation state changed. This confirms the ampscript.guide claim that the function returns false outside a MobileConnect message context; the official Salesforce reference omits this and describes only the in-context behaviour. The success path (true, keyword actually set) requires a live MobileConnect message context that cannot be captured on this tenant, so the function is recorded blocked for the success path while the CloudPage false-return is proven. The catalogued signature was corrected here: the three parameters are originationNumber, destinationNumber and keyword, and the return is a boolean, not void. A docUrl to the official reference was also added.',
5452
+ 'The out-of-context return is confirmed in two independent runtime contexts: a CloudPage on the child BU and an email render on the child BU. Being an ordinary function call, it compiles and evaluates in both: on the CloudPage, called with a real short code, the authorized destination number and a keyword, it returned the literal boolean false with the page rendering fully, no SMS sent and no conversation state changed; in an email body the same call rendered the literal False through the Email Preview API. This confirms the ampscript.guide claim that the function returns false outside a MobileConnect message context; the official Salesforce reference omits this and describes only the in-context behaviour. The success path (true, keyword actually set) requires a live MobileConnect message context and cannot be reproduced in a CloudPage or email; only the out-of-context false-return is exercisable, and it is proven. The catalogued signature was corrected here: the three parameters are originationNumber, destinationNumber and keyword, and the return is a boolean, not void. A docUrl to the official reference was also added.',
5138
5453
  params: [
5139
5454
  {
5140
5455
  name: 'originationNumber',
@@ -5160,6 +5475,8 @@ export const FUNCTIONS = [
5160
5475
  },
5161
5476
  {
5162
5477
  name: 'SetStateMscrmRecord',
5478
+ supportedInCloudPage: false,
5479
+ supportedInEmail: false,
5163
5480
  mcnSince: null,
5164
5481
  handlebarsEquivalent: null,
5165
5482
  mcnNotes: null,
@@ -5205,6 +5522,8 @@ export const FUNCTIONS = [
5205
5522
  },
5206
5523
  {
5207
5524
  name: 'SHA1',
5525
+ supportedInCloudPage: true,
5526
+ supportedInEmail: true,
5208
5527
  mcnSince: null,
5209
5528
  handlebarsEquivalent: null,
5210
5529
  mcnNotes: null,
@@ -5244,6 +5563,8 @@ export const FUNCTIONS = [
5244
5563
  },
5245
5564
  {
5246
5565
  name: 'SHA256',
5566
+ supportedInCloudPage: true,
5567
+ supportedInEmail: true,
5247
5568
  mcnSince: null,
5248
5569
  handlebarsEquivalent: null,
5249
5570
  mcnNotes: null,
@@ -5283,6 +5604,8 @@ export const FUNCTIONS = [
5283
5604
  },
5284
5605
  {
5285
5606
  name: 'SHA512',
5607
+ supportedInCloudPage: true,
5608
+ supportedInEmail: true,
5286
5609
  mcnSince: null,
5287
5610
  handlebarsEquivalent: null,
5288
5611
  mcnNotes: null,
@@ -5322,6 +5645,8 @@ export const FUNCTIONS = [
5322
5645
  },
5323
5646
  {
5324
5647
  name: 'StringToDate',
5648
+ supportedInCloudPage: true,
5649
+ supportedInEmail: true,
5325
5650
  mcnSince: 67,
5326
5651
  handlebarsEquivalent: null,
5327
5652
  mcnNotes:
@@ -5352,6 +5677,8 @@ export const FUNCTIONS = [
5352
5677
  },
5353
5678
  {
5354
5679
  name: 'StringToHex',
5680
+ supportedInCloudPage: true,
5681
+ supportedInEmail: true,
5355
5682
  mcnSince: null,
5356
5683
  handlebarsEquivalent: null,
5357
5684
  mcnNotes: null,
@@ -5390,6 +5717,8 @@ export const FUNCTIONS = [
5390
5717
  },
5391
5718
  {
5392
5719
  name: 'Substring',
5720
+ supportedInCloudPage: true,
5721
+ supportedInEmail: true,
5393
5722
  mcnSince: 67,
5394
5723
  handlebarsEquivalent: 'substring',
5395
5724
  handlebarsExact: true,
@@ -5429,6 +5758,8 @@ export const FUNCTIONS = [
5429
5758
  },
5430
5759
  {
5431
5760
  name: 'Subtract',
5761
+ supportedInCloudPage: true,
5762
+ supportedInEmail: true,
5432
5763
  mcnSince: 67,
5433
5764
  handlebarsEquivalent: 'subtract',
5434
5765
  handlebarsExact: true,
@@ -5453,6 +5784,8 @@ export const FUNCTIONS = [
5453
5784
  },
5454
5785
  {
5455
5786
  name: 'SystemDateToLocalDate',
5787
+ supportedInCloudPage: true,
5788
+ supportedInEmail: true,
5456
5789
  mcnSince: null,
5457
5790
  handlebarsEquivalent: 'timeZoneConversion',
5458
5791
  handlebarsExact: false,
@@ -5483,6 +5816,8 @@ export const FUNCTIONS = [
5483
5816
  },
5484
5817
  {
5485
5818
  name: 'TransformXML',
5819
+ supportedInCloudPage: true,
5820
+ supportedInEmail: true,
5486
5821
  mcnSince: null,
5487
5822
  handlebarsEquivalent: null,
5488
5823
  mcnNotes: null,
@@ -5505,6 +5840,8 @@ export const FUNCTIONS = [
5505
5840
  },
5506
5841
  {
5507
5842
  name: 'TreatAsContent',
5843
+ supportedInCloudPage: true,
5844
+ supportedInEmail: true,
5508
5845
  mcnSince: null,
5509
5846
  handlebarsEquivalent: null,
5510
5847
  mcnNotes: null,
@@ -5534,6 +5871,8 @@ export const FUNCTIONS = [
5534
5871
  },
5535
5872
  {
5536
5873
  name: 'TreatAsContentArea',
5874
+ supportedInCloudPage: true,
5875
+ supportedInEmail: true,
5537
5876
  mcnSince: null,
5538
5877
  handlebarsEquivalent: null,
5539
5878
  mcnNotes: null,
@@ -5566,6 +5905,8 @@ export const FUNCTIONS = [
5566
5905
  },
5567
5906
  {
5568
5907
  name: 'Trim',
5908
+ supportedInCloudPage: true,
5909
+ supportedInEmail: true,
5569
5910
  mcnSince: 67,
5570
5911
  handlebarsEquivalent: 'trim',
5571
5912
  handlebarsExact: true,
@@ -5590,6 +5931,8 @@ export const FUNCTIONS = [
5590
5931
  },
5591
5932
  {
5592
5933
  name: 'UpdateData',
5934
+ supportedInCloudPage: true,
5935
+ supportedInEmail: false,
5593
5936
  mcnSince: null,
5594
5937
  handlebarsEquivalent: null,
5595
5938
  mcnNotes: null,
@@ -5597,7 +5940,9 @@ export const FUNCTIONS = [
5597
5940
  guideUrl: 'https://ampscript.guide/updatedata/',
5598
5941
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/updatedata/',
5599
5942
  isConfirmed: true,
5600
- differsFromOfficialDocs: false,
5943
+ differsFromOfficialDocs: true,
5944
+ officialDocsNote:
5945
+ 'Email/send-context finding: UpdateData is not valid in sendable email content. Rendered through the Email Preview API against a seeded sendable row, an isolated UpdateData(...) was rejected with HTTP 400 errorcode 10005 ("UpdateData Function is not valid in content. This function is only allowed in a non batch context."). A send is a batch operation, so the UpdateData/*Data write family cannot run inside a sendable email; use the UpdateDE variant instead, which the send parser accepts in sendable content. This is a CloudPage / landing-page (non-batch) feature.',
5601
5946
  minArgs: 6,
5602
5947
  maxArgs: INF,
5603
5948
  category: 'Data Extension',
@@ -5658,6 +6003,8 @@ export const FUNCTIONS = [
5658
6003
  },
5659
6004
  {
5660
6005
  name: 'UpdateDE',
6006
+ supportedInCloudPage: true,
6007
+ supportedInEmail: true,
5661
6008
  mcnSince: null,
5662
6009
  handlebarsEquivalent: null,
5663
6010
  mcnNotes: null,
@@ -5726,6 +6073,8 @@ export const FUNCTIONS = [
5726
6073
  },
5727
6074
  {
5728
6075
  name: 'UpdateMSCRMRecords',
6076
+ supportedInCloudPage: false,
6077
+ supportedInEmail: false,
5729
6078
  mcnSince: null,
5730
6079
  handlebarsEquivalent: null,
5731
6080
  mcnNotes: null,
@@ -5780,6 +6129,8 @@ export const FUNCTIONS = [
5780
6129
  },
5781
6130
  {
5782
6131
  name: 'UpdateSingleSalesforceObject',
6132
+ supportedInCloudPage: true,
6133
+ supportedInEmail: true,
5783
6134
  mcnSince: null,
5784
6135
  handlebarsEquivalent: null,
5785
6136
  mcnNotes: null,
@@ -5795,7 +6146,7 @@ export const FUNCTIONS = [
5795
6146
  isConfirmed: true,
5796
6147
  differsFromOfficialDocs: false,
5797
6148
  officialDocsNote:
5798
- 'The success token 1 was runtime-proven on cred/DEV (MID 510007949), which has an active Marketing Cloud Connect integration to a real Salesforce org: updating one field of a record created moments earlier in the same run (a benign Task) returned the literal 1 with the page rendering fully. The failure token 0 is NOT observable in CloudPage GET context: every safe induced failure (unknown object, a malformed ID, and a well-formed but non-existent Lead ID at both 15 and 18 characters, on a real field) aborted the whole page with HTTP 422 — the SOAP fault propagates as an uncatchable page abort (identical to CreateSalesforceObject and RetrieveSalesforceObjects against a bad target), so the documented 0 return never materialises to be read. returnEnum is therefore left unset: only 1 is provable here, and asserting a [0,1] enum would ship the unproven 0 token. returnType stays number and the 0/1 semantics are retained in the description as a documented fact attributed to the official reference. The 0-on-CloudPage-abort behaviour is a context observation, not a contradiction of the send/preview-context 0/1 contract, so differsFromOfficialDocs stays false.',
6149
+ 'The success token 1 was runtime-proven on the child BU, which has an active Marketing Cloud Connect integration to a real Salesforce org: updating one field of a record created moments earlier in the same run (a benign Task) returned the literal 1 with the page rendering fully. The failure token 0 is NOT observable in CloudPage GET context: every safe induced failure (unknown object, a malformed ID, and a well-formed but non-existent Lead ID at both 15 and 18 characters, on a real field) aborted the whole page with HTTP 422 — the SOAP fault propagates as an uncatchable page abort (identical to CreateSalesforceObject and RetrieveSalesforceObjects against a bad target), so the documented 0 return never materialises to be read. returnEnum is therefore left unset: only 1 is provable here, and asserting a [0,1] enum would ship the unproven 0 token. returnType stays number and the 0/1 semantics are retained in the description as a documented fact attributed to the official reference. The 0-on-CloudPage-abort behaviour is a context observation, not a contradiction of the send/preview-context 0/1 contract, so differsFromOfficialDocs stays false.',
5799
6150
  params: [
5800
6151
  {
5801
6152
  name: 'objectName',
@@ -5826,6 +6177,8 @@ export const FUNCTIONS = [
5826
6177
  },
5827
6178
  {
5828
6179
  name: 'Uppercase',
6180
+ supportedInCloudPage: true,
6181
+ supportedInEmail: true,
5829
6182
  mcnSince: 67,
5830
6183
  handlebarsEquivalent: 'uppercase',
5831
6184
  handlebarsExact: true,
@@ -5854,6 +6207,8 @@ export const FUNCTIONS = [
5854
6207
  },
5855
6208
  {
5856
6209
  name: 'UpsertContact',
6210
+ supportedInCloudPage: true,
6211
+ supportedInEmail: true,
5857
6212
  mcnSince: null,
5858
6213
  handlebarsEquivalent: null,
5859
6214
  mcnNotes: null,
@@ -5868,7 +6223,7 @@ export const FUNCTIONS = [
5868
6223
  isConfirmed: true,
5869
6224
  differsFromOfficialDocs: false,
5870
6225
  officialDocsNote:
5871
- 'Both return tokens were runtime-proven on cred/DEV (MID 510007949). The success status 0 was proven by creating a brand-new mobile contact keyed on an opaque, unreachable phone number in a reserved test range with a documented system attribute (_ZipCode); calling the same key a second time with a different value updated that contact and again returned 0, so both the create and update branches of the upsert return 0. The error status 1 was proven three independent ways (unsupported channel, unsupported match attribute, non-numeric phone) and again by passing an attribute name that is not a defined MobileConnect attribute — each returned 1 with the page rendering fully and no write performed. The return is a status code (0 success / 1 error), not a count of records. The phone-number argument accepts both an integer literal and a numeric string (both returned 0 for a successful create). runtime matches the official reference, so differsFromOfficialDocs stays false.',
6226
+ 'Both return tokens were runtime-proven on the child BU. The success status 0 was proven by creating a brand-new mobile contact keyed on an opaque, unreachable phone number in a reserved test range with a documented system attribute (_ZipCode); calling the same key a second time with a different value updated that contact and again returned 0, so both the create and update branches of the upsert return 0. The error status 1 was proven three independent ways (unsupported channel, unsupported match attribute, non-numeric phone) and again by passing an attribute name that is not a defined MobileConnect attribute — each returned 1 with the page rendering fully and no write performed. The return is a status code (0 success / 1 error), not a count of records. The phone-number argument accepts both an integer literal and a numeric string (both returned 0 for a successful create). runtime matches the official reference, so differsFromOfficialDocs stays false.',
5872
6227
  params: [
5873
6228
  {
5874
6229
  name: 'channel',
@@ -5916,6 +6271,8 @@ export const FUNCTIONS = [
5916
6271
  },
5917
6272
  {
5918
6273
  name: 'UpsertData',
6274
+ supportedInCloudPage: true,
6275
+ supportedInEmail: false,
5919
6276
  mcnSince: null,
5920
6277
  handlebarsEquivalent: null,
5921
6278
  mcnNotes: null,
@@ -5923,7 +6280,9 @@ export const FUNCTIONS = [
5923
6280
  guideUrl: 'https://ampscript.guide/upsertdata/',
5924
6281
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/upsertdata/',
5925
6282
  isConfirmed: true,
5926
- differsFromOfficialDocs: false,
6283
+ differsFromOfficialDocs: true,
6284
+ officialDocsNote:
6285
+ 'Email/send-context finding: UpsertData is not valid in sendable email content. Rendered through the Email Preview API against a seeded sendable row, an isolated UpsertData(...) was rejected with HTTP 400 errorcode 10005 ("UpsertData Function is not valid in content. This function is only allowed in a non batch context."). A send is a batch operation, so the UpsertData/*Data write family cannot run inside a sendable email; use the UpsertDE variant instead, which the send parser accepts in sendable content. This is a CloudPage / landing-page (non-batch) feature.',
5927
6286
  minArgs: 6,
5928
6287
  maxArgs: INF,
5929
6288
  category: 'Data Extension',
@@ -5994,6 +6353,8 @@ export const FUNCTIONS = [
5994
6353
  },
5995
6354
  {
5996
6355
  name: 'UpsertDE',
6356
+ supportedInCloudPage: true,
6357
+ supportedInEmail: true,
5997
6358
  mcnSince: null,
5998
6359
  handlebarsEquivalent: null,
5999
6360
  mcnNotes: null,
@@ -6072,6 +6433,8 @@ export const FUNCTIONS = [
6072
6433
  },
6073
6434
  {
6074
6435
  name: 'UpsertMSCRMRecord',
6436
+ supportedInCloudPage: false,
6437
+ supportedInEmail: false,
6075
6438
  mcnSince: null,
6076
6439
  handlebarsEquivalent: null,
6077
6440
  mcnNotes: null,
@@ -6144,6 +6507,8 @@ export const FUNCTIONS = [
6144
6507
  },
6145
6508
  {
6146
6509
  name: 'URLEncode',
6510
+ supportedInCloudPage: true,
6511
+ supportedInEmail: true,
6147
6512
  mcnSince: null,
6148
6513
  handlebarsEquivalent: null,
6149
6514
  mcnNotes: null,
@@ -6188,6 +6553,8 @@ export const FUNCTIONS = [
6188
6553
  },
6189
6554
  {
6190
6555
  name: 'Verb',
6556
+ supportedInCloudPage: false,
6557
+ supportedInEmail: false,
6191
6558
  mcnSince: null,
6192
6559
  handlebarsEquivalent: null,
6193
6560
  mcnNotes: null,
@@ -6202,7 +6569,7 @@ export const FUNCTIONS = [
6202
6569
  verificationBlocked: true,
6203
6570
  verificationBlockedReason: 'no-working-invocation',
6204
6571
  officialDocsNote:
6205
- 'Could not runtime-verify on the only available context (a CloudPage GET on cred/DEV, MID 510007949; no parent-BU escalation on this tenant). Verb is chained off Msg(0), and any page containing a Msg(0) construct aborts at compile time (HTTP 422) on a CloudPage while an otherwise identical page without it renders HTTP 200. This matches the official reference, which restricts the function to MobileConnect and forbids landing pages / other content types; a CloudPage supplies no mobile-originated message to parse.',
6572
+ 'Could not runtime-verify on the only available context (a CloudPage GET on the child BU; no parent-BU escalation on this tenant). Verb is chained off Msg(0), and any page containing a Msg(0) construct aborts at compile time (HTTP 422) on a CloudPage while an otherwise identical page without it renders HTTP 200. This matches the official reference, which restricts the function to MobileConnect and forbids landing pages / other content types; a CloudPage supplies no mobile-originated message to parse.',
6206
6573
  params: [],
6207
6574
  returnType: 'string',
6208
6575
  returnDescription: 'The keyword (first word) of the inbound mobile-originated message.',
@@ -6211,6 +6578,8 @@ export const FUNCTIONS = [
6211
6578
  },
6212
6579
  {
6213
6580
  name: 'v',
6581
+ supportedInCloudPage: true,
6582
+ supportedInEmail: true,
6214
6583
  mcnSince: 67,
6215
6584
  handlebarsEquivalent: null,
6216
6585
  mcnNotes: null,
@@ -6237,6 +6606,8 @@ export const FUNCTIONS = [
6237
6606
  },
6238
6607
  {
6239
6608
  name: 'WAT',
6609
+ supportedInCloudPage: false,
6610
+ supportedInEmail: false,
6240
6611
  mcnSince: null,
6241
6612
  handlebarsEquivalent: null,
6242
6613
  mcnNotes: null,
@@ -6273,10 +6644,14 @@ export const FUNCTIONS = [
6273
6644
  example: "%%=WAT('Omniture', '1234', '5678')=%%",
6274
6645
  isConfirmed: false,
6275
6646
  verificationBlocked: true,
6276
- verificationBlockedReason: 'no-working-invocation',
6647
+ verificationBlockedReason: 'no-test-data',
6648
+ officialDocsNote:
6649
+ 'On a CloudPage every invocation aborted at HTTP 422 on both the child BU and the parent BU. An email-context render on the parent BU changed the picture: the Email Preview API RECOGNISES and evaluates the function and fails with a precise message that the named tracking parameter set does not exist (Tracking Parameter Name: Omniture). So WAT is not a broken function — it resolves a Web Analytics Tracking parameter set that must first be configured on the account (a Salesforce-support / Sender Profile setup), and none exists on these BUs to resolve. The block is a missing-test-data gate, not a broken invocation.',
6277
6650
  },
6278
6651
  {
6279
6652
  name: 'WATP',
6653
+ supportedInCloudPage: false,
6654
+ supportedInEmail: false,
6280
6655
  mcnSince: null,
6281
6656
  handlebarsEquivalent: null,
6282
6657
  mcnNotes: null,
@@ -6305,6 +6680,8 @@ export const FUNCTIONS = [
6305
6680
  },
6306
6681
  {
6307
6682
  name: 'WrapLongURL',
6683
+ supportedInCloudPage: true,
6684
+ supportedInEmail: true,
6308
6685
  mcnSince: null,
6309
6686
  handlebarsEquivalent: null,
6310
6687
  mcnNotes: null,
@@ -6318,7 +6695,7 @@ export const FUNCTIONS = [
6318
6695
  isConfirmed: true,
6319
6696
  differsFromOfficialDocs: true,
6320
6697
  officialDocsNote:
6321
- 'The official reference states that a URL longer than 975 characters comes back as a shortened link that redirects through the platform. On a live Engagement CloudPage on the child business unit (MID 518005426) a 1048-character URL was returned byte for byte unchanged at the same length, twice in one render, and the same held for a 27-character URL, an empty string and a string that is not a URL at all. The community guide notes that shortening only happens on a send, which the official page does not mention.',
6698
+ 'The official reference states that a URL longer than 975 characters comes back as a shortened link that redirects through the platform. On a live Engagement CloudPage on the child business unit a 1048-character URL was returned byte for byte unchanged at the same length, twice in one render, and the same held for a 27-character URL, an empty string and a string that is not a URL at all. The community guide notes that shortening only happens on a send, which the official page does not mention.',
6322
6699
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/wraplongurl/',
6323
6700
  params: [{ name: 'url', description: 'URL to shorten', type: 'string|number' }],
6324
6701
  returnType: 'string',