ampscript-data 3.5.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 +469 -74
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,20 +952,23 @@ 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,
905
964
  docUrl: 'https://developer.salesforce.com/docs/marketing/marketing-cloud-ampscript/references/mc-ampscript-data-extension/mc-ampscript-reference-data-extension-claim-row-value.html',
906
965
  guideUrl: 'https://ampscript.guide/claimrowvalue/',
907
966
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/claimrowvalue/',
908
- minArgs: 3,
967
+ minArgs: 6,
909
968
  maxArgs: INF,
910
969
  category: 'Data Extension',
911
- description: 'Atomically claims a row and returns a specific column value from it.',
970
+ description:
971
+ 'Atomically claims a row and returns a specific column value from it, or a caller-supplied fallback when no unclaimed rows remain.',
912
972
  params: [
913
973
  {
914
974
  name: 'dataExt',
@@ -930,40 +990,59 @@ export const FUNCTIONS = [
930
990
  type: 'string',
931
991
  },
932
992
  {
933
- name: 'valueIfClaimed',
993
+ name: 'fallbackValue',
934
994
  mcnSince: null,
935
995
  mcnNotes: null,
936
- description: 'A fallback value returned if there are no unclaimed rows',
937
- optional: true,
996
+ description:
997
+ 'Value returned when no unclaimed rows remain (required at runtime, despite ampscript.guide marking it optional)',
938
998
  },
939
999
  {
940
- name: 'claimantColumnN',
1000
+ name: 'claimantColumn',
941
1001
  mcnSince: null,
942
1002
  mcnNotes: null,
943
1003
  description:
944
- 'The column the function uses to track the subscriber who claimed the row',
1004
+ 'The column the function uses to track the subscriber who claimed the row (required at runtime)',
1005
+ type: 'string',
1006
+ },
1007
+ {
1008
+ name: 'claimantValue',
1009
+ mcnSince: null,
1010
+ mcnNotes: null,
1011
+ description:
1012
+ 'The value to enter in the claimant column when the function claims a row (required at runtime)',
1013
+ },
1014
+ {
1015
+ name: 'additionalColumnNameN',
1016
+ mcnSince: null,
1017
+ mcnNotes: null,
1018
+ description:
1019
+ 'Name of a further column to write on the claimed row (record extra context at claim time). Repeatable as name/value pairs.',
945
1020
  type: 'string',
946
1021
  optional: true,
947
1022
  },
948
1023
  {
949
- name: 'claimantValueN',
1024
+ name: 'additionalColumnValueN',
950
1025
  mcnSince: null,
951
1026
  mcnNotes: null,
952
1027
  description:
953
- 'The value to enter in the claimant column when the function claims a row',
1028
+ 'Value written to the paired additionalColumnNameN column on the claimed row',
954
1029
  optional: true,
955
1030
  },
956
1031
  ],
957
1032
  returnType: 'string',
958
- returnDescription: 'The value from the requested column of the claimed row.',
959
- repeat: [{ startIndex: 4, groupSize: 2, minGroups: 0 }],
960
- syntax: 'ClaimRowValue(dataExt, returnValueColumn, claimColumn[, valueIfClaimed, claimantColumnN, claimantValueN, ...])',
961
- example: "%%=ClaimRowValue('Coupons', 'Code', 'Claimed', '', 'SubKey', _subscriberkey)=%%",
1033
+ returnDescription:
1034
+ 'The value from the requested column of the claimed row, or the fallbackValue when no unclaimed rows remain.',
1035
+ repeat: [{ startIndex: 6, groupSize: 2, minGroups: 0 }],
1036
+ syntax: 'ClaimRowValue(dataExt, returnValueColumn, claimColumn, fallbackValue, claimantColumn, claimantValue[, additionalColumnNameN, additionalColumnValueN, ...])',
1037
+ example:
1038
+ "%%=ClaimRowValue('Coupons', 'Code', 'Claimed', 'SOLD OUT', 'SubKey', _subscriberkey)=%%",
962
1039
  isConfirmed: true,
963
1040
  differsFromOfficialDocs: false,
964
1041
  },
965
1042
  {
966
1043
  name: 'CloudPagesURL',
1044
+ supportedInCloudPage: true,
1045
+ supportedInEmail: true,
967
1046
  mcnSince: null,
968
1047
  handlebarsEquivalent: null,
969
1048
  mcnNotes: null,
@@ -1017,6 +1096,8 @@ export const FUNCTIONS = [
1017
1096
  },
1018
1097
  {
1019
1098
  name: 'Concat',
1099
+ supportedInCloudPage: true,
1100
+ supportedInEmail: true,
1020
1101
  mcnSince: 67,
1021
1102
  handlebarsEquivalent: 'concat',
1022
1103
  handlebarsExact: true,
@@ -1053,6 +1134,8 @@ export const FUNCTIONS = [
1053
1134
  },
1054
1135
  {
1055
1136
  name: 'ContentArea',
1137
+ supportedInCloudPage: true,
1138
+ supportedInEmail: true,
1056
1139
  mcnSince: null,
1057
1140
  handlebarsEquivalent: null,
1058
1141
  mcnNotes: null,
@@ -1121,6 +1204,8 @@ export const FUNCTIONS = [
1121
1204
  },
1122
1205
  {
1123
1206
  name: 'ContentAreaByName',
1207
+ supportedInCloudPage: true,
1208
+ supportedInEmail: true,
1124
1209
  mcnSince: null,
1125
1210
  handlebarsEquivalent: null,
1126
1211
  mcnNotes: null,
@@ -1187,6 +1272,8 @@ export const FUNCTIONS = [
1187
1272
  },
1188
1273
  {
1189
1274
  name: 'ContentBlockByID',
1275
+ supportedInCloudPage: true,
1276
+ supportedInEmail: true,
1190
1277
  mcnSince: 67,
1191
1278
  handlebarsEquivalent: null,
1192
1279
  mcnNotes: null,
@@ -1250,6 +1337,8 @@ export const FUNCTIONS = [
1250
1337
  },
1251
1338
  {
1252
1339
  name: 'ContentBlockByKey',
1340
+ supportedInCloudPage: true,
1341
+ supportedInEmail: true,
1253
1342
  mcnSince: 67,
1254
1343
  handlebarsEquivalent: 'getContentBlock',
1255
1344
  handlebarsExact: false,
@@ -1314,6 +1403,8 @@ export const FUNCTIONS = [
1314
1403
  },
1315
1404
  {
1316
1405
  name: 'ContentBlockByName',
1406
+ supportedInCloudPage: true,
1407
+ supportedInEmail: true,
1317
1408
  mcnSince: 67,
1318
1409
  handlebarsEquivalent: null,
1319
1410
  mcnNotes: null,
@@ -1378,6 +1469,8 @@ export const FUNCTIONS = [
1378
1469
  },
1379
1470
  {
1380
1471
  name: 'ContentImageByID',
1472
+ supportedInCloudPage: true,
1473
+ supportedInEmail: true,
1381
1474
  mcnSince: null,
1382
1475
  handlebarsEquivalent: null,
1383
1476
  mcnNotes: null,
@@ -1415,6 +1508,8 @@ export const FUNCTIONS = [
1415
1508
  },
1416
1509
  {
1417
1510
  name: 'ContentImageByKey',
1511
+ supportedInCloudPage: true,
1512
+ supportedInEmail: true,
1418
1513
  mcnSince: null,
1419
1514
  handlebarsEquivalent: null,
1420
1515
  mcnNotes: null,
@@ -1451,6 +1546,8 @@ export const FUNCTIONS = [
1451
1546
  },
1452
1547
  {
1453
1548
  name: 'CreateMSCRMRecord',
1549
+ supportedInCloudPage: false,
1550
+ supportedInEmail: false,
1454
1551
  mcnSince: null,
1455
1552
  handlebarsEquivalent: null,
1456
1553
  mcnNotes: null,
@@ -1503,6 +1600,8 @@ export const FUNCTIONS = [
1503
1600
  },
1504
1601
  {
1505
1602
  name: 'CreateObject',
1603
+ supportedInCloudPage: true,
1604
+ supportedInEmail: false,
1506
1605
  mcnSince: null,
1507
1606
  handlebarsEquivalent: null,
1508
1607
  mcnNotes: null,
@@ -1522,9 +1621,14 @@ export const FUNCTIONS = [
1522
1621
  syntax: 'CreateObject(objectName)',
1523
1622
  example: "%%=CreateObject('DataExtensionObject')=%%",
1524
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.',
1525
1627
  },
1526
1628
  {
1527
1629
  name: 'CreateSalesforceObject',
1630
+ supportedInCloudPage: true,
1631
+ supportedInEmail: true,
1528
1632
  mcnSince: null,
1529
1633
  handlebarsEquivalent: null,
1530
1634
  mcnNotes: null,
@@ -1539,7 +1643,7 @@ export const FUNCTIONS = [
1539
1643
  isConfirmed: true,
1540
1644
  differsFromOfficialDocs: false,
1541
1645
  officialDocsNote:
1542
- '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.',
1543
1647
  params: [
1544
1648
  {
1545
1649
  name: 'objectName',
@@ -1576,6 +1680,8 @@ export const FUNCTIONS = [
1576
1680
  },
1577
1681
  {
1578
1682
  name: 'CreateSmsConversation',
1683
+ supportedInCloudPage: true,
1684
+ supportedInEmail: true,
1579
1685
  mcnSince: null,
1580
1686
  handlebarsEquivalent: null,
1581
1687
  mcnNotes: null,
@@ -1586,12 +1692,10 @@ export const FUNCTIONS = [
1586
1692
  category: 'MobileConnect',
1587
1693
  description:
1588
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.',
1589
- isConfirmed: false,
1590
- verificationBlocked: true,
1591
- verificationBlockedReason: 'no-working-invocation',
1695
+ isConfirmed: true,
1592
1696
  differsFromOfficialDocs: true,
1593
1697
  officialDocsNote:
1594
- "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.",
1595
1699
  params: [
1596
1700
  {
1597
1701
  name: 'originationNumber',
@@ -1622,6 +1726,8 @@ export const FUNCTIONS = [
1622
1726
  },
1623
1727
  {
1624
1728
  name: 'DataExtensionRowCount',
1729
+ supportedInCloudPage: true,
1730
+ supportedInEmail: true,
1625
1731
  mcnSince: null,
1626
1732
  handlebarsEquivalent: null,
1627
1733
  mcnNotes: null,
@@ -1650,6 +1756,8 @@ export const FUNCTIONS = [
1650
1756
  },
1651
1757
  {
1652
1758
  name: 'DateAdd',
1759
+ supportedInCloudPage: true,
1760
+ supportedInEmail: true,
1653
1761
  mcnSince: 67,
1654
1762
  handlebarsEquivalent: 'dateAdd',
1655
1763
  handlebarsExact: true,
@@ -1692,6 +1800,8 @@ export const FUNCTIONS = [
1692
1800
  },
1693
1801
  {
1694
1802
  name: 'DateDiff',
1803
+ supportedInCloudPage: true,
1804
+ supportedInEmail: true,
1695
1805
  mcnSince: 67,
1696
1806
  handlebarsEquivalent: 'dateDiff',
1697
1807
  handlebarsExact: true,
@@ -1735,6 +1845,8 @@ export const FUNCTIONS = [
1735
1845
  },
1736
1846
  {
1737
1847
  name: 'DateParse',
1848
+ supportedInCloudPage: true,
1849
+ supportedInEmail: true,
1738
1850
  mcnSince: 67,
1739
1851
  handlebarsEquivalent: null,
1740
1852
  mcnNotes: null,
@@ -1774,6 +1886,8 @@ export const FUNCTIONS = [
1774
1886
  },
1775
1887
  {
1776
1888
  name: 'DatePart',
1889
+ supportedInCloudPage: true,
1890
+ supportedInEmail: true,
1777
1891
  mcnSince: null,
1778
1892
  handlebarsEquivalent: null,
1779
1893
  mcnNotes: null,
@@ -1824,6 +1938,8 @@ export const FUNCTIONS = [
1824
1938
  },
1825
1939
  {
1826
1940
  name: 'DecryptSymmetric',
1941
+ supportedInCloudPage: true,
1942
+ supportedInEmail: true,
1827
1943
  mcnSince: null,
1828
1944
  handlebarsEquivalent: null,
1829
1945
  mcnNotes: null,
@@ -1888,6 +2004,8 @@ export const FUNCTIONS = [
1888
2004
  },
1889
2005
  {
1890
2006
  name: 'DeleteData',
2007
+ supportedInCloudPage: true,
2008
+ supportedInEmail: false,
1891
2009
  mcnSince: null,
1892
2010
  handlebarsEquivalent: null,
1893
2011
  mcnNotes: null,
@@ -1895,7 +2013,9 @@ export const FUNCTIONS = [
1895
2013
  guideUrl: 'https://ampscript.guide/deletedata/',
1896
2014
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/deletedata/',
1897
2015
  isConfirmed: true,
1898
- 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.',
1899
2019
  minArgs: 3,
1900
2020
  maxArgs: INF,
1901
2021
  category: 'Data Extension',
@@ -1935,6 +2055,8 @@ export const FUNCTIONS = [
1935
2055
  },
1936
2056
  {
1937
2057
  name: 'DeleteDE',
2058
+ supportedInCloudPage: true,
2059
+ supportedInEmail: true,
1938
2060
  mcnSince: null,
1939
2061
  handlebarsEquivalent: null,
1940
2062
  mcnNotes: null,
@@ -1981,6 +2103,8 @@ export const FUNCTIONS = [
1981
2103
  },
1982
2104
  {
1983
2105
  name: 'DescribeMSCRMEntities',
2106
+ supportedInCloudPage: false,
2107
+ supportedInEmail: false,
1984
2108
  mcnSince: null,
1985
2109
  handlebarsEquivalent: null,
1986
2110
  mcnNotes: null,
@@ -2003,6 +2127,8 @@ export const FUNCTIONS = [
2003
2127
  },
2004
2128
  {
2005
2129
  name: 'DescribeMSCRMEntityAttributes',
2130
+ supportedInCloudPage: false,
2131
+ supportedInEmail: false,
2006
2132
  mcnSince: null,
2007
2133
  handlebarsEquivalent: null,
2008
2134
  mcnNotes: null,
@@ -2025,6 +2151,8 @@ export const FUNCTIONS = [
2025
2151
  },
2026
2152
  {
2027
2153
  name: 'Divide',
2154
+ supportedInCloudPage: true,
2155
+ supportedInEmail: true,
2028
2156
  mcnSince: 67,
2029
2157
  handlebarsEquivalent: 'divide',
2030
2158
  handlebarsExact: true,
@@ -2050,6 +2178,8 @@ export const FUNCTIONS = [
2050
2178
  },
2051
2179
  {
2052
2180
  name: 'Domain',
2181
+ supportedInCloudPage: true,
2182
+ supportedInEmail: true,
2053
2183
  mcnSince: null,
2054
2184
  handlebarsEquivalent: null,
2055
2185
  mcnNotes: null,
@@ -2078,6 +2208,8 @@ export const FUNCTIONS = [
2078
2208
  },
2079
2209
  {
2080
2210
  name: 'Empty',
2211
+ supportedInCloudPage: true,
2212
+ supportedInEmail: true,
2081
2213
  mcnSince: 67,
2082
2214
  handlebarsEquivalent: 'isEmpty',
2083
2215
  handlebarsExact: true,
@@ -2107,6 +2239,8 @@ export const FUNCTIONS = [
2107
2239
  },
2108
2240
  {
2109
2241
  name: 'EncryptSymmetric',
2242
+ supportedInCloudPage: true,
2243
+ supportedInEmail: true,
2110
2244
  mcnSince: null,
2111
2245
  handlebarsEquivalent: null,
2112
2246
  mcnNotes: null,
@@ -2166,6 +2300,8 @@ export const FUNCTIONS = [
2166
2300
  },
2167
2301
  {
2168
2302
  name: 'EndImpressionRegion',
2303
+ supportedInCloudPage: true,
2304
+ supportedInEmail: true,
2169
2305
  mcnSince: null,
2170
2306
  handlebarsEquivalent: null,
2171
2307
  mcnNotes: null,
@@ -2196,6 +2332,8 @@ export const FUNCTIONS = [
2196
2332
  },
2197
2333
  {
2198
2334
  name: 'EndSmsConversation',
2335
+ supportedInCloudPage: true,
2336
+ supportedInEmail: true,
2199
2337
  mcnSince: null,
2200
2338
  handlebarsEquivalent: null,
2201
2339
  mcnNotes: null,
@@ -2206,12 +2344,10 @@ export const FUNCTIONS = [
2206
2344
  category: 'MobileConnect',
2207
2345
  description:
2208
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.',
2209
- isConfirmed: false,
2210
- verificationBlocked: true,
2211
- verificationBlockedReason: 'no-working-invocation',
2347
+ isConfirmed: true,
2212
2348
  differsFromOfficialDocs: true,
2213
2349
  officialDocsNote:
2214
- '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.',
2215
2351
  params: [
2216
2352
  {
2217
2353
  name: 'originationNumber',
@@ -2232,6 +2368,8 @@ export const FUNCTIONS = [
2232
2368
  },
2233
2369
  {
2234
2370
  name: 'ExecuteFilter',
2371
+ supportedInCloudPage: true,
2372
+ supportedInEmail: false,
2235
2373
  mcnSince: null,
2236
2374
  handlebarsEquivalent: null,
2237
2375
  mcnNotes: null,
@@ -2239,7 +2377,9 @@ export const FUNCTIONS = [
2239
2377
  guideUrl: 'https://ampscript.guide/executefilter/',
2240
2378
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/executefilter/',
2241
2379
  isConfirmed: true,
2242
- 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.',
2243
2383
  minArgs: 1,
2244
2384
  maxArgs: 1,
2245
2385
  category: 'Data Extension',
@@ -2259,6 +2399,8 @@ export const FUNCTIONS = [
2259
2399
  },
2260
2400
  {
2261
2401
  name: 'ExecuteFilterOrderedRows',
2402
+ supportedInCloudPage: true,
2403
+ supportedInEmail: false,
2262
2404
  mcnSince: null,
2263
2405
  handlebarsEquivalent: null,
2264
2406
  mcnNotes: null,
@@ -2266,7 +2408,9 @@ export const FUNCTIONS = [
2266
2408
  guideUrl: 'https://ampscript.guide/executefilterorderedrows/',
2267
2409
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/executefilterorderedrows/',
2268
2410
  isConfirmed: true,
2269
- 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.',
2270
2414
  minArgs: 3,
2271
2415
  maxArgs: 3,
2272
2416
  category: 'Data Extension',
@@ -2299,6 +2443,8 @@ export const FUNCTIONS = [
2299
2443
  },
2300
2444
  {
2301
2445
  name: 'Field',
2446
+ supportedInCloudPage: true,
2447
+ supportedInEmail: true,
2302
2448
  mcnSince: 67,
2303
2449
  handlebarsEquivalent: 'get',
2304
2450
  handlebarsExact: false,
@@ -2334,6 +2480,8 @@ export const FUNCTIONS = [
2334
2480
  },
2335
2481
  {
2336
2482
  name: 'Format',
2483
+ supportedInCloudPage: true,
2484
+ supportedInEmail: true,
2337
2485
  mcnSince: 67,
2338
2486
  handlebarsEquivalent: 'format',
2339
2487
  handlebarsExact: false,
@@ -2346,7 +2494,7 @@ export const FUNCTIONS = [
2346
2494
  isConfirmed: true,
2347
2495
  differsFromOfficialDocs: true,
2348
2496
  officialDocsNote:
2349
- '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.',
2350
2498
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/format/',
2351
2499
  description:
2352
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.',
@@ -2388,6 +2536,8 @@ export const FUNCTIONS = [
2388
2536
  },
2389
2537
  {
2390
2538
  name: 'FormatCurrency',
2539
+ supportedInCloudPage: true,
2540
+ supportedInEmail: true,
2391
2541
  mcnSince: 67,
2392
2542
  handlebarsEquivalent: 'formatCurrency',
2393
2543
  handlebarsExact: false,
@@ -2442,6 +2592,8 @@ export const FUNCTIONS = [
2442
2592
  },
2443
2593
  {
2444
2594
  name: 'FormatDate',
2595
+ supportedInCloudPage: true,
2596
+ supportedInEmail: true,
2445
2597
  mcnSince: 67,
2446
2598
  handlebarsEquivalent: 'format',
2447
2599
  handlebarsExact: false,
@@ -2455,7 +2607,7 @@ export const FUNCTIONS = [
2455
2607
  isConfirmed: true,
2456
2608
  differsFromOfficialDocs: true,
2457
2609
  officialDocsNote:
2458
- '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.',
2459
2611
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/formatdate/',
2460
2612
  description:
2461
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.',
@@ -2498,6 +2650,8 @@ export const FUNCTIONS = [
2498
2650
  },
2499
2651
  {
2500
2652
  name: 'FormatNumber',
2653
+ supportedInCloudPage: true,
2654
+ supportedInEmail: true,
2501
2655
  mcnSince: 67,
2502
2656
  handlebarsEquivalent: 'formatNumber',
2503
2657
  handlebarsExact: true,
@@ -2540,6 +2694,8 @@ export const FUNCTIONS = [
2540
2694
  },
2541
2695
  {
2542
2696
  name: 'GetJWT',
2697
+ supportedInCloudPage: true,
2698
+ supportedInEmail: true,
2543
2699
  mcnSince: null,
2544
2700
  handlebarsEquivalent: null,
2545
2701
  mcnNotes: null,
@@ -2581,6 +2737,8 @@ export const FUNCTIONS = [
2581
2737
  },
2582
2738
  {
2583
2739
  name: 'GetJWTByKeyName',
2740
+ supportedInCloudPage: true,
2741
+ supportedInEmail: true,
2584
2742
  mcnSince: null,
2585
2743
  handlebarsEquivalent: null,
2586
2744
  mcnNotes: null,
@@ -2614,6 +2772,8 @@ export const FUNCTIONS = [
2614
2772
  },
2615
2773
  {
2616
2774
  name: 'GetPortfolioItem',
2775
+ supportedInCloudPage: false,
2776
+ supportedInEmail: false,
2617
2777
  mcnSince: null,
2618
2778
  handlebarsEquivalent: null,
2619
2779
  mcnNotes: null,
@@ -2637,10 +2797,12 @@ export const FUNCTIONS = [
2637
2797
  isConfirmed: true,
2638
2798
  nonFunctionalAtRuntime: true,
2639
2799
  officialDocsNote:
2640
- '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.',
2641
2801
  },
2642
2802
  {
2643
2803
  name: 'GetPublishedSocialContent',
2804
+ supportedInCloudPage: false,
2805
+ supportedInEmail: false,
2644
2806
  mcnSince: null,
2645
2807
  handlebarsEquivalent: null,
2646
2808
  mcnNotes: null,
@@ -2659,11 +2821,14 @@ export const FUNCTIONS = [
2659
2821
  example: "%%=GetPublishedSocialContent('socialContentId')=%%",
2660
2822
  isConfirmed: true,
2661
2823
  nonFunctionalAtRuntime: true,
2824
+ differsFromOfficialDocs: true,
2662
2825
  officialDocsNote:
2663
- '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.',
2664
2827
  },
2665
2828
  {
2666
2829
  name: 'GetSendTime',
2830
+ supportedInCloudPage: true,
2831
+ supportedInEmail: true,
2667
2832
  mcnSince: null,
2668
2833
  handlebarsEquivalent: null,
2669
2834
  mcnNotes: null,
@@ -2690,15 +2855,15 @@ export const FUNCTIONS = [
2690
2855
  'A real date value the other date functions accept directly, in the same system time zone as Now().',
2691
2856
  syntax: 'GetSendTime([boolAllSubscribers])',
2692
2857
  example: '%%=GetSendTime(1)=%%',
2693
- isConfirmed: false,
2694
- verificationBlocked: true,
2695
- verificationBlockedReason: 'needs-auth-context',
2858
+ isConfirmed: true,
2696
2859
  differsFromOfficialDocs: false,
2697
2860
  officialDocsNote:
2698
- '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.',
2699
2862
  },
2700
2863
  {
2701
2864
  name: 'GetSocialPublishURL',
2865
+ supportedInCloudPage: true,
2866
+ supportedInEmail: true,
2702
2867
  mcnSince: null,
2703
2868
  handlebarsEquivalent: null,
2704
2869
  mcnNotes: null,
@@ -2755,6 +2920,8 @@ export const FUNCTIONS = [
2755
2920
  },
2756
2921
  {
2757
2922
  name: 'GetSocialPublishURLByName',
2923
+ supportedInCloudPage: true,
2924
+ supportedInEmail: true,
2758
2925
  mcnSince: null,
2759
2926
  handlebarsEquivalent: null,
2760
2927
  mcnNotes: null,
@@ -2813,6 +2980,8 @@ export const FUNCTIONS = [
2813
2980
  },
2814
2981
  {
2815
2982
  name: 'GUID',
2983
+ supportedInCloudPage: true,
2984
+ supportedInEmail: true,
2816
2985
  mcnSince: null,
2817
2986
  handlebarsEquivalent: null,
2818
2987
  mcnNotes: null,
@@ -2835,6 +3004,8 @@ export const FUNCTIONS = [
2835
3004
  },
2836
3005
  {
2837
3006
  name: 'HTTPGet',
3007
+ supportedInCloudPage: true,
3008
+ supportedInEmail: true,
2838
3009
  mcnSince: null,
2839
3010
  handlebarsEquivalent: null,
2840
3011
  mcnNotes: null,
@@ -2886,6 +3057,8 @@ export const FUNCTIONS = [
2886
3057
  },
2887
3058
  {
2888
3059
  name: 'HTTPPost',
3060
+ supportedInCloudPage: true,
3061
+ supportedInEmail: true,
2889
3062
  mcnSince: null,
2890
3063
  handlebarsEquivalent: null,
2891
3064
  mcnNotes: null,
@@ -2898,7 +3071,7 @@ export const FUNCTIONS = [
2898
3071
  isConfirmed: true,
2899
3072
  differsFromOfficialDocs: true,
2900
3073
  officialDocsNote:
2901
- '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.',
2902
3075
  description:
2903
3076
  'Performs an HTTP POST request and returns the HTTP status code. The response body is written to the optional output variable.',
2904
3077
  params: [
@@ -2959,6 +3132,8 @@ export const FUNCTIONS = [
2959
3132
  },
2960
3133
  {
2961
3134
  name: 'HTTPPost2',
3135
+ supportedInCloudPage: true,
3136
+ supportedInEmail: true,
2962
3137
  mcnSince: null,
2963
3138
  handlebarsEquivalent: null,
2964
3139
  mcnNotes: null,
@@ -2971,7 +3146,7 @@ export const FUNCTIONS = [
2971
3146
  isConfirmed: true,
2972
3147
  differsFromOfficialDocs: true,
2973
3148
  officialDocsNote:
2974
- '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.',
2975
3150
  description:
2976
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.',
2977
3152
  params: [
@@ -3033,6 +3208,8 @@ export const FUNCTIONS = [
3033
3208
  },
3034
3209
  {
3035
3210
  name: 'HTTPPostWithRetry',
3211
+ supportedInCloudPage: true,
3212
+ supportedInEmail: true,
3036
3213
  mcnSince: null,
3037
3214
  handlebarsEquivalent: null,
3038
3215
  mcnNotes: null,
@@ -3045,7 +3222,7 @@ export const FUNCTIONS = [
3045
3222
  isConfirmed: true,
3046
3223
  differsFromOfficialDocs: true,
3047
3224
  officialDocsNote:
3048
- '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.',
3049
3226
  description:
3050
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.',
3051
3228
  params: [
@@ -3127,13 +3304,15 @@ export const FUNCTIONS = [
3127
3304
  },
3128
3305
  {
3129
3306
  name: 'HTTPRequestHeader',
3307
+ supportedInCloudPage: true,
3308
+ supportedInEmail: false,
3130
3309
  mcnSince: null,
3131
3310
  handlebarsEquivalent: null,
3132
3311
  mcnNotes: null,
3133
3312
  isConfirmed: true,
3134
3313
  differsFromOfficialDocs: true,
3135
3314
  officialDocsNote:
3136
- '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.',
3137
3316
  docUrl: 'https://developer.salesforce.com/docs/marketing/marketing-cloud-ampscript/references/mc-ampscript-http/mc-ampscript-reference-http-request-header.html',
3138
3317
  guideUrl: 'https://ampscript.guide/httprequestheader/',
3139
3318
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/httprequestheader/',
@@ -3156,6 +3335,8 @@ export const FUNCTIONS = [
3156
3335
  },
3157
3336
  {
3158
3337
  name: 'IIf',
3338
+ supportedInCloudPage: true,
3339
+ supportedInEmail: true,
3159
3340
  mcnSince: 67,
3160
3341
  handlebarsEquivalent: 'iif',
3161
3342
  handlebarsExact: true,
@@ -3195,6 +3376,8 @@ export const FUNCTIONS = [
3195
3376
  },
3196
3377
  {
3197
3378
  name: 'Image',
3379
+ supportedInCloudPage: false,
3380
+ supportedInEmail: false,
3198
3381
  mcnSince: null,
3199
3382
  handlebarsEquivalent: null,
3200
3383
  mcnNotes: null,
@@ -3232,10 +3415,12 @@ export const FUNCTIONS = [
3232
3415
  deprecatedReason:
3233
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.',
3234
3417
  officialDocsNote:
3235
- '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.',
3236
3419
  },
3237
3420
  {
3238
3421
  name: 'IndexOf',
3422
+ supportedInCloudPage: true,
3423
+ supportedInEmail: true,
3239
3424
  mcnSince: 67,
3240
3425
  handlebarsEquivalent: 'indexOf',
3241
3426
  handlebarsExact: false,
@@ -3271,6 +3456,8 @@ export const FUNCTIONS = [
3271
3456
  },
3272
3457
  {
3273
3458
  name: 'InsertData',
3459
+ supportedInCloudPage: true,
3460
+ supportedInEmail: false,
3274
3461
  mcnSince: null,
3275
3462
  handlebarsEquivalent: null,
3276
3463
  mcnNotes: null,
@@ -3278,7 +3465,9 @@ export const FUNCTIONS = [
3278
3465
  guideUrl: 'https://ampscript.guide/insertdata/',
3279
3466
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/insertdata/',
3280
3467
  isConfirmed: true,
3281
- 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.',
3282
3471
  minArgs: 3,
3283
3472
  maxArgs: INF,
3284
3473
  category: 'Data Extension',
@@ -3316,6 +3505,8 @@ export const FUNCTIONS = [
3316
3505
  },
3317
3506
  {
3318
3507
  name: 'InsertDE',
3508
+ supportedInCloudPage: true,
3509
+ supportedInEmail: true,
3319
3510
  mcnSince: null,
3320
3511
  handlebarsEquivalent: null,
3321
3512
  mcnNotes: null,
@@ -3362,6 +3553,8 @@ export const FUNCTIONS = [
3362
3553
  },
3363
3554
  {
3364
3555
  name: 'InvokeCreate',
3556
+ supportedInCloudPage: true,
3557
+ supportedInEmail: false,
3365
3558
  mcnSince: null,
3366
3559
  handlebarsEquivalent: null,
3367
3560
  mcnNotes: null,
@@ -3404,9 +3597,14 @@ export const FUNCTIONS = [
3404
3597
  syntax: 'InvokeCreate(apiObject, @statusMessage, @errorCode[, createOptionsObject])',
3405
3598
  example: '%%=InvokeCreate(@apiObject, @statusMessage, @errorCode)=%%',
3406
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.',
3407
3603
  },
3408
3604
  {
3409
3605
  name: 'InvokeDelete',
3606
+ supportedInCloudPage: true,
3607
+ supportedInEmail: false,
3410
3608
  mcnSince: null,
3411
3609
  handlebarsEquivalent: null,
3412
3610
  mcnNotes: null,
@@ -3449,9 +3647,14 @@ export const FUNCTIONS = [
3449
3647
  syntax: 'InvokeDelete(apiObject, @statusMessage, @errorCode[, deleteOptionsObject])',
3450
3648
  example: '%%=InvokeDelete(@apiObject, @statusMessage, @errorCode)=%%',
3451
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.',
3452
3653
  },
3453
3654
  {
3454
3655
  name: 'InvokeExecute',
3656
+ supportedInCloudPage: true,
3657
+ supportedInEmail: false,
3455
3658
  mcnSince: null,
3456
3659
  handlebarsEquivalent: null,
3457
3660
  mcnNotes: null,
@@ -3486,9 +3689,14 @@ export const FUNCTIONS = [
3486
3689
  syntax: 'InvokeExecute(apiObject[, @statusMessage, @requestId])',
3487
3690
  example: '%%[ SET @rows = InvokeExecute(@apiObject, @statusMessage, @requestId) ]%%',
3488
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.',
3489
3695
  },
3490
3696
  {
3491
3697
  name: 'InvokePerform',
3698
+ supportedInCloudPage: true,
3699
+ supportedInEmail: false,
3492
3700
  mcnSince: null,
3493
3701
  handlebarsEquivalent: null,
3494
3702
  mcnNotes: null,
@@ -3522,9 +3730,14 @@ export const FUNCTIONS = [
3522
3730
  syntax: 'InvokePerform(apiObject, actionToPerform[, @statusMessage])',
3523
3731
  example: "%%=InvokePerform(@apiObject, 'Start', @statusMessage)=%%",
3524
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.',
3525
3736
  },
3526
3737
  {
3527
3738
  name: 'InvokeRetrieve',
3739
+ supportedInCloudPage: true,
3740
+ supportedInEmail: false,
3528
3741
  mcnSince: null,
3529
3742
  handlebarsEquivalent: null,
3530
3743
  mcnNotes: null,
@@ -3563,9 +3776,14 @@ export const FUNCTIONS = [
3563
3776
  syntax: 'InvokeRetrieve(apiObject[, @statusMessage, @requestId])',
3564
3777
  example: '%%[ SET @rows = InvokeRetrieve(@apiObject, @statusMessage, @requestId) ]%%',
3565
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.',
3566
3782
  },
3567
3783
  {
3568
3784
  name: 'InvokeUpdate',
3785
+ supportedInCloudPage: true,
3786
+ supportedInEmail: false,
3569
3787
  mcnSince: null,
3570
3788
  handlebarsEquivalent: null,
3571
3789
  mcnNotes: null,
@@ -3610,9 +3828,14 @@ export const FUNCTIONS = [
3610
3828
  syntax: 'InvokeUpdate(apiObject[, @statusMessage, @errorCode, updateOptions])',
3611
3829
  example: '%%=InvokeUpdate(@apiObject, @statusMessage, @errorCode)=%%',
3612
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.',
3613
3834
  },
3614
3835
  {
3615
3836
  name: 'IsCHTMLBrowser',
3837
+ supportedInCloudPage: true,
3838
+ supportedInEmail: false,
3616
3839
  mcnSince: null,
3617
3840
  handlebarsEquivalent: null,
3618
3841
  mcnNotes: null,
@@ -3622,10 +3845,12 @@ export const FUNCTIONS = [
3622
3845
  minArgs: 1,
3623
3846
  maxArgs: 1,
3624
3847
  isConfirmed: true,
3625
- 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.',
3626
3851
  category: 'Utility',
3627
3852
  description:
3628
- '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.',
3629
3854
  params: [
3630
3855
  {
3631
3856
  name: 'userAgent',
@@ -3642,6 +3867,8 @@ export const FUNCTIONS = [
3642
3867
  },
3643
3868
  {
3644
3869
  name: 'IsEmailAddress',
3870
+ supportedInCloudPage: true,
3871
+ supportedInEmail: true,
3645
3872
  mcnSince: null,
3646
3873
  handlebarsEquivalent: null,
3647
3874
  mcnNotes: null,
@@ -3653,7 +3880,7 @@ export const FUNCTIONS = [
3653
3880
  isConfirmed: true,
3654
3881
  differsFromOfficialDocs: true,
3655
3882
  officialDocsNote:
3656
- '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.',
3657
3884
  category: 'Utility',
3658
3885
  description:
3659
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.',
@@ -3674,6 +3901,8 @@ export const FUNCTIONS = [
3674
3901
  },
3675
3902
  {
3676
3903
  name: 'IsNull',
3904
+ supportedInCloudPage: true,
3905
+ supportedInEmail: true,
3677
3906
  mcnSince: 67,
3678
3907
  handlebarsEquivalent: 'isEmpty',
3679
3908
  handlebarsExact: false,
@@ -3700,12 +3929,14 @@ export const FUNCTIONS = [
3700
3929
  isConfirmed: true,
3701
3930
  differsFromOfficialDocs: true,
3702
3931
  officialDocsNote:
3703
- '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.',
3704
3933
  syntax: 'IsNull(value)',
3705
3934
  example: '%%=IsNull(@value)=%%',
3706
3935
  },
3707
3936
  {
3708
3937
  name: 'IsNullDefault',
3938
+ supportedInCloudPage: true,
3939
+ supportedInEmail: true,
3709
3940
  mcnSince: null,
3710
3941
  handlebarsEquivalent: 'fallback',
3711
3942
  handlebarsExact: false,
@@ -3739,6 +3970,8 @@ export const FUNCTIONS = [
3739
3970
  },
3740
3971
  {
3741
3972
  name: 'IsPhoneNumber',
3973
+ supportedInCloudPage: true,
3974
+ supportedInEmail: true,
3742
3975
  mcnSince: null,
3743
3976
  handlebarsEquivalent: null,
3744
3977
  mcnNotes: null,
@@ -3768,6 +4001,8 @@ export const FUNCTIONS = [
3768
4001
  },
3769
4002
  {
3770
4003
  name: 'Length',
4004
+ supportedInCloudPage: true,
4005
+ supportedInEmail: true,
3771
4006
  mcnSince: 67,
3772
4007
  handlebarsEquivalent: 'length',
3773
4008
  handlebarsExact: true,
@@ -3796,6 +4031,8 @@ export const FUNCTIONS = [
3796
4031
  },
3797
4032
  {
3798
4033
  name: 'LiveContentMicrositeURL',
4034
+ supportedInCloudPage: false,
4035
+ supportedInEmail: false,
3799
4036
  mcnSince: null,
3800
4037
  handlebarsEquivalent: null,
3801
4038
  mcnNotes: null,
@@ -3811,7 +4048,7 @@ export const FUNCTIONS = [
3811
4048
  deprecatedReason:
3812
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.',
3813
4050
  officialDocsNote:
3814
- "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.",
3815
4052
  params: [
3816
4053
  {
3817
4054
  name: 'contentType',
@@ -3833,6 +4070,8 @@ export const FUNCTIONS = [
3833
4070
  },
3834
4071
  {
3835
4072
  name: 'LocalDateToSystemDate',
4073
+ supportedInCloudPage: true,
4074
+ supportedInEmail: true,
3836
4075
  mcnSince: null,
3837
4076
  handlebarsEquivalent: 'timeZoneConversion',
3838
4077
  handlebarsExact: false,
@@ -3863,6 +4102,8 @@ export const FUNCTIONS = [
3863
4102
  },
3864
4103
  {
3865
4104
  name: 'LongSFID',
4105
+ supportedInCloudPage: true,
4106
+ supportedInEmail: true,
3866
4107
  mcnSince: null,
3867
4108
  handlebarsEquivalent: null,
3868
4109
  mcnNotes: null,
@@ -3884,6 +4125,8 @@ export const FUNCTIONS = [
3884
4125
  },
3885
4126
  {
3886
4127
  name: 'Lookup',
4128
+ supportedInCloudPage: true,
4129
+ supportedInEmail: true,
3887
4130
  mcnSince: 67,
3888
4131
  handlebarsEquivalent: 'queryFirst',
3889
4132
  handlebarsExact: false,
@@ -3935,6 +4178,8 @@ export const FUNCTIONS = [
3935
4178
  },
3936
4179
  {
3937
4180
  name: 'LookupOrderedRows',
4181
+ supportedInCloudPage: true,
4182
+ supportedInEmail: true,
3938
4183
  mcnSince: null,
3939
4184
  handlebarsEquivalent: 'query',
3940
4185
  handlebarsExact: false,
@@ -3993,6 +4238,8 @@ export const FUNCTIONS = [
3993
4238
  },
3994
4239
  {
3995
4240
  name: 'LookupOrderedRowsCS',
4241
+ supportedInCloudPage: true,
4242
+ supportedInEmail: true,
3996
4243
  mcnSince: null,
3997
4244
  handlebarsEquivalent: 'query',
3998
4245
  handlebarsExact: false,
@@ -4050,6 +4297,8 @@ export const FUNCTIONS = [
4050
4297
  },
4051
4298
  {
4052
4299
  name: 'LookupRows',
4300
+ supportedInCloudPage: true,
4301
+ supportedInEmail: true,
4053
4302
  mcnSince: null,
4054
4303
  handlebarsEquivalent: 'query',
4055
4304
  handlebarsExact: false,
@@ -4093,6 +4342,8 @@ export const FUNCTIONS = [
4093
4342
  },
4094
4343
  {
4095
4344
  name: 'LookupRowsCS',
4345
+ supportedInCloudPage: true,
4346
+ supportedInEmail: true,
4096
4347
  mcnSince: null,
4097
4348
  handlebarsEquivalent: 'query',
4098
4349
  handlebarsExact: false,
@@ -4136,6 +4387,8 @@ export const FUNCTIONS = [
4136
4387
  },
4137
4388
  {
4138
4389
  name: 'Lowercase',
4390
+ supportedInCloudPage: true,
4391
+ supportedInEmail: true,
4139
4392
  mcnSince: 67,
4140
4393
  handlebarsEquivalent: 'lowercase',
4141
4394
  handlebarsExact: true,
@@ -4163,6 +4416,8 @@ export const FUNCTIONS = [
4163
4416
  },
4164
4417
  {
4165
4418
  name: 'MD5',
4419
+ supportedInCloudPage: true,
4420
+ supportedInEmail: true,
4166
4421
  mcnSince: null,
4167
4422
  handlebarsEquivalent: null,
4168
4423
  mcnNotes: null,
@@ -4202,6 +4457,8 @@ export const FUNCTIONS = [
4202
4457
  },
4203
4458
  {
4204
4459
  name: 'MMS_Content_URL',
4460
+ supportedInCloudPage: false,
4461
+ supportedInEmail: false,
4205
4462
  mcnSince: null,
4206
4463
  handlebarsEquivalent: null,
4207
4464
  mcnNotes: null,
@@ -4216,7 +4473,7 @@ export const FUNCTIONS = [
4216
4473
  verificationBlocked: true,
4217
4474
  verificationBlockedReason: 'no-working-invocation',
4218
4475
  officialDocsNote:
4219
- '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.',
4220
4477
  params: [
4221
4478
  {
4222
4479
  name: 'position',
@@ -4232,6 +4489,8 @@ export const FUNCTIONS = [
4232
4489
  },
4233
4490
  {
4234
4491
  name: 'MicrositeURL',
4492
+ supportedInCloudPage: true,
4493
+ supportedInEmail: true,
4235
4494
  mcnSince: null,
4236
4495
  handlebarsEquivalent: null,
4237
4496
  mcnNotes: null,
@@ -4281,6 +4540,8 @@ export const FUNCTIONS = [
4281
4540
  },
4282
4541
  {
4283
4542
  name: 'Mod',
4543
+ supportedInCloudPage: true,
4544
+ supportedInEmail: true,
4284
4545
  mcnSince: 67,
4285
4546
  handlebarsEquivalent: 'modulo',
4286
4547
  handlebarsExact: true,
@@ -4307,6 +4568,8 @@ export const FUNCTIONS = [
4307
4568
  },
4308
4569
  {
4309
4570
  name: 'Msg',
4571
+ supportedInCloudPage: false,
4572
+ supportedInEmail: false,
4310
4573
  mcnSince: null,
4311
4574
  handlebarsEquivalent: null,
4312
4575
  mcnNotes: null,
@@ -4321,7 +4584,7 @@ export const FUNCTIONS = [
4321
4584
  verificationBlocked: true,
4322
4585
  verificationBlockedReason: 'no-working-invocation',
4323
4586
  officialDocsNote:
4324
- '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.',
4325
4588
  params: [
4326
4589
  {
4327
4590
  name: 'index',
@@ -4336,6 +4599,8 @@ export const FUNCTIONS = [
4336
4599
  },
4337
4600
  {
4338
4601
  name: 'Multiply',
4602
+ supportedInCloudPage: true,
4603
+ supportedInEmail: true,
4339
4604
  mcnSince: 67,
4340
4605
  handlebarsEquivalent: 'multiply',
4341
4606
  handlebarsExact: true,
@@ -4360,6 +4625,8 @@ export const FUNCTIONS = [
4360
4625
  },
4361
4626
  {
4362
4627
  name: 'Noun',
4628
+ supportedInCloudPage: false,
4629
+ supportedInEmail: false,
4363
4630
  mcnSince: null,
4364
4631
  handlebarsEquivalent: null,
4365
4632
  mcnNotes: null,
@@ -4374,7 +4641,7 @@ export const FUNCTIONS = [
4374
4641
  verificationBlocked: true,
4375
4642
  verificationBlockedReason: 'no-working-invocation',
4376
4643
  officialDocsNote:
4377
- '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.',
4378
4645
  params: [
4379
4646
  {
4380
4647
  name: 'position',
@@ -4390,6 +4657,8 @@ export const FUNCTIONS = [
4390
4657
  },
4391
4658
  {
4392
4659
  name: 'Nouns',
4660
+ supportedInCloudPage: false,
4661
+ supportedInEmail: false,
4393
4662
  mcnSince: null,
4394
4663
  handlebarsEquivalent: null,
4395
4664
  mcnNotes: null,
@@ -4404,7 +4673,7 @@ export const FUNCTIONS = [
4404
4673
  verificationBlocked: true,
4405
4674
  verificationBlockedReason: 'no-working-invocation',
4406
4675
  officialDocsNote:
4407
- '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.',
4408
4677
  params: [],
4409
4678
  returnType: 'string',
4410
4679
  returnDescription: 'All content that follows the keyword in the inbound message.',
@@ -4413,6 +4682,8 @@ export const FUNCTIONS = [
4413
4682
  },
4414
4683
  {
4415
4684
  name: 'Now',
4685
+ supportedInCloudPage: true,
4686
+ supportedInEmail: true,
4416
4687
  mcnSince: 67,
4417
4688
  handlebarsEquivalent: 'now',
4418
4689
  handlebarsExact: false,
@@ -4446,6 +4717,8 @@ export const FUNCTIONS = [
4446
4717
  },
4447
4718
  {
4448
4719
  name: 'Output',
4720
+ supportedInCloudPage: true,
4721
+ supportedInEmail: false,
4449
4722
  mcnSince: 67,
4450
4723
  handlebarsEquivalent: null,
4451
4724
  mcnNotes: null,
@@ -4453,7 +4726,7 @@ export const FUNCTIONS = [
4453
4726
  guideUrl: 'https://ampscript.guide/output/',
4454
4727
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/output/',
4455
4728
  minArgs: 0,
4456
- maxArgs: Infinity,
4729
+ maxArgs: INF,
4457
4730
  category: 'Utility',
4458
4731
  description:
4459
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.',
@@ -4462,20 +4735,30 @@ export const FUNCTIONS = [
4462
4735
  name: 'content',
4463
4736
  description:
4464
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,
4465
4745
  },
4466
4746
  ],
4467
4747
  returnType: 'void',
4468
4748
  returnDescription:
4469
4749
  'No value is returned, so the call cannot be nested inside another function; the result is written straight into the rendered content.',
4470
- syntax: 'Output(content)',
4750
+ repeat: [{ startIndex: 0, groupSize: 1, minGroups: 0 }],
4751
+ syntax: 'Output([content, ...])',
4471
4752
  example: "%%=Output(Concat('Hello ', @firstName))=%%",
4472
4753
  isConfirmed: true,
4473
4754
  differsFromOfficialDocs: true,
4474
4755
  officialDocsNote:
4475
- '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.',
4476
4757
  },
4477
4758
  {
4478
4759
  name: 'OutputLine',
4760
+ supportedInCloudPage: true,
4761
+ supportedInEmail: true,
4479
4762
  mcnSince: 67,
4480
4763
  handlebarsEquivalent: null,
4481
4764
  mcnNotes: null,
@@ -4483,7 +4766,7 @@ export const FUNCTIONS = [
4483
4766
  guideUrl: 'https://ampscript.guide/outputline/',
4484
4767
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/outputline/',
4485
4768
  minArgs: 0,
4486
- maxArgs: Infinity,
4769
+ maxArgs: INF,
4487
4770
  category: 'Utility',
4488
4771
  description:
4489
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.',
@@ -4492,18 +4775,28 @@ export const FUNCTIONS = [
4492
4775
  name: 'content',
4493
4776
  description:
4494
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,
4495
4785
  },
4496
4786
  ],
4497
4787
  returnType: 'void',
4498
4788
  returnDescription:
4499
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.',
4500
- syntax: 'OutputLine(content)',
4790
+ repeat: [{ startIndex: 0, groupSize: 1, minGroups: 0 }],
4791
+ syntax: 'OutputLine([content, ...])',
4501
4792
  example: "%%=OutputLine(Concat('Hello ', @firstName))=%%",
4502
4793
  isConfirmed: true,
4503
4794
  differsFromOfficialDocs: false,
4504
4795
  },
4505
4796
  {
4506
4797
  name: 'ProperCase',
4798
+ supportedInCloudPage: true,
4799
+ supportedInEmail: true,
4507
4800
  mcnSince: 67,
4508
4801
  handlebarsEquivalent: 'properCase',
4509
4802
  handlebarsExact: true,
@@ -4529,6 +4822,8 @@ export const FUNCTIONS = [
4529
4822
  },
4530
4823
  {
4531
4824
  name: 'QueryParameter',
4825
+ supportedInCloudPage: true,
4826
+ supportedInEmail: true,
4532
4827
  mcnSince: null,
4533
4828
  handlebarsEquivalent: null,
4534
4829
  mcnNotes: null,
@@ -4556,6 +4851,8 @@ export const FUNCTIONS = [
4556
4851
  },
4557
4852
  {
4558
4853
  name: 'RaiseError',
4854
+ supportedInCloudPage: true,
4855
+ supportedInEmail: true,
4559
4856
  mcnSince: 67,
4560
4857
  handlebarsEquivalent: 'raiseError',
4561
4858
  handlebarsExact: false,
@@ -4615,6 +4912,8 @@ export const FUNCTIONS = [
4615
4912
  },
4616
4913
  {
4617
4914
  name: 'Random',
4915
+ supportedInCloudPage: true,
4916
+ supportedInEmail: true,
4618
4917
  mcnSince: 67,
4619
4918
  handlebarsEquivalent: 'random',
4620
4919
  handlebarsExact: true,
@@ -4638,10 +4937,12 @@ export const FUNCTIONS = [
4638
4937
  isConfirmed: true,
4639
4938
  differsFromOfficialDocs: true,
4640
4939
  officialDocsNote:
4641
- '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.',
4642
4941
  },
4643
4942
  {
4644
4943
  name: 'RatingStars',
4944
+ supportedInCloudPage: false,
4945
+ supportedInEmail: false,
4645
4946
  mcnSince: null,
4646
4947
  handlebarsEquivalent: null,
4647
4948
  mcnNotes: null,
@@ -4663,10 +4964,12 @@ export const FUNCTIONS = [
4663
4964
  verificationBlocked: true,
4664
4965
  verificationBlockedReason: 'no-test-data',
4665
4966
  officialDocsNote:
4666
- '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.',
4667
4968
  },
4668
4969
  {
4669
4970
  name: 'Redirect',
4971
+ supportedInCloudPage: true,
4972
+ supportedInEmail: false,
4670
4973
  mcnSince: null,
4671
4974
  handlebarsEquivalent: null,
4672
4975
  mcnNotes: null,
@@ -4685,10 +4988,14 @@ export const FUNCTIONS = [
4685
4988
  syntax: 'Redirect(url)',
4686
4989
  example: "Redirect('https://example.com')",
4687
4990
  isConfirmed: true,
4688
- 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.',
4689
4994
  },
4690
4995
  {
4691
4996
  name: 'RedirectTo',
4997
+ supportedInCloudPage: true,
4998
+ supportedInEmail: true,
4692
4999
  mcnSince: null,
4693
5000
  handlebarsEquivalent: null,
4694
5001
  mcnNotes: null,
@@ -4711,6 +5018,8 @@ export const FUNCTIONS = [
4711
5018
  },
4712
5019
  {
4713
5020
  name: 'RegExMatch',
5021
+ supportedInCloudPage: true,
5022
+ supportedInEmail: true,
4714
5023
  mcnSince: null,
4715
5024
  handlebarsEquivalent: null,
4716
5025
  mcnNotes: null,
@@ -4720,7 +5029,7 @@ export const FUNCTIONS = [
4720
5029
  isConfirmed: true,
4721
5030
  differsFromOfficialDocs: false,
4722
5031
  minArgs: 3,
4723
- maxArgs: Infinity,
5032
+ maxArgs: INF,
4724
5033
  category: 'String',
4725
5034
  description:
4726
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.',
@@ -4758,6 +5067,7 @@ export const FUNCTIONS = [
4758
5067
  returnType: 'string',
4759
5068
  returnDescription:
4760
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 }],
4761
5071
  syntax: 'RegExMatch(sourceString, regExPattern, returnValue[, regExOptions, ...])',
4762
5072
  example:
4763
5073
  'Var @couponCode, @regEx, @regExMatch\n' +
@@ -4767,6 +5077,8 @@ export const FUNCTIONS = [
4767
5077
  },
4768
5078
  {
4769
5079
  name: 'Replace',
5080
+ supportedInCloudPage: true,
5081
+ supportedInEmail: true,
4770
5082
  mcnSince: 67,
4771
5083
  handlebarsEquivalent: 'replace',
4772
5084
  handlebarsExact: false,
@@ -4799,6 +5111,8 @@ export const FUNCTIONS = [
4799
5111
  },
4800
5112
  {
4801
5113
  name: 'ReplaceList',
5114
+ supportedInCloudPage: true,
5115
+ supportedInEmail: true,
4802
5116
  mcnSince: 67,
4803
5117
  handlebarsEquivalent: null,
4804
5118
  mcnNotes: null,
@@ -4832,6 +5146,8 @@ export const FUNCTIONS = [
4832
5146
  },
4833
5147
  {
4834
5148
  name: 'RequestParameter',
5149
+ supportedInCloudPage: true,
5150
+ supportedInEmail: true,
4835
5151
  mcnSince: null,
4836
5152
  handlebarsEquivalent: null,
4837
5153
  mcnNotes: null,
@@ -4859,6 +5175,8 @@ export const FUNCTIONS = [
4859
5175
  },
4860
5176
  {
4861
5177
  name: 'RetrieveMSCRMRecords',
5178
+ supportedInCloudPage: false,
5179
+ supportedInEmail: false,
4862
5180
  mcnSince: null,
4863
5181
  handlebarsEquivalent: null,
4864
5182
  mcnNotes: null,
@@ -4907,6 +5225,8 @@ export const FUNCTIONS = [
4907
5225
  },
4908
5226
  {
4909
5227
  name: 'RetrieveMSCRMRecordsFetchXML',
5228
+ supportedInCloudPage: false,
5229
+ supportedInEmail: false,
4910
5230
  mcnSince: null,
4911
5231
  handlebarsEquivalent: null,
4912
5232
  mcnNotes: null,
@@ -4929,6 +5249,8 @@ export const FUNCTIONS = [
4929
5249
  },
4930
5250
  {
4931
5251
  name: 'RetrieveSalesforceJobSources',
5252
+ supportedInCloudPage: true,
5253
+ supportedInEmail: true,
4932
5254
  mcnSince: null,
4933
5255
  handlebarsEquivalent: null,
4934
5256
  mcnNotes: null,
@@ -4958,6 +5280,8 @@ export const FUNCTIONS = [
4958
5280
  },
4959
5281
  {
4960
5282
  name: 'RetrieveSalesforceObjects',
5283
+ supportedInCloudPage: true,
5284
+ supportedInEmail: true,
4961
5285
  mcnSince: 67,
4962
5286
  handlebarsEquivalent: 'query',
4963
5287
  handlebarsExact: false,
@@ -5024,6 +5348,8 @@ export const FUNCTIONS = [
5024
5348
  },
5025
5349
  {
5026
5350
  name: 'Row',
5351
+ supportedInCloudPage: true,
5352
+ supportedInEmail: true,
5027
5353
  mcnSince: 67,
5028
5354
  handlebarsEquivalent: 'get',
5029
5355
  handlebarsExact: false,
@@ -5049,6 +5375,8 @@ export const FUNCTIONS = [
5049
5375
  },
5050
5376
  {
5051
5377
  name: 'RowCount',
5378
+ supportedInCloudPage: true,
5379
+ supportedInEmail: true,
5052
5380
  mcnSince: 67,
5053
5381
  handlebarsEquivalent: 'length',
5054
5382
  handlebarsExact: false,
@@ -5070,6 +5398,8 @@ export const FUNCTIONS = [
5070
5398
  },
5071
5399
  {
5072
5400
  name: 'SetObjectProperty',
5401
+ supportedInCloudPage: true,
5402
+ supportedInEmail: false,
5073
5403
  mcnSince: null,
5074
5404
  handlebarsEquivalent: null,
5075
5405
  mcnNotes: null,
@@ -5098,9 +5428,14 @@ export const FUNCTIONS = [
5098
5428
  syntax: 'SetObjectProperty(apiObject, propertyName, propertyValue)',
5099
5429
  example: "SetObjectProperty(@apiObject, 'LastName', 'Smith')",
5100
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.',
5101
5434
  },
5102
5435
  {
5103
5436
  name: 'SetSmsConversationNextKeyword',
5437
+ supportedInCloudPage: true,
5438
+ supportedInEmail: true,
5104
5439
  mcnSince: null,
5105
5440
  handlebarsEquivalent: null,
5106
5441
  mcnNotes: null,
@@ -5111,12 +5446,10 @@ export const FUNCTIONS = [
5111
5446
  category: 'MobileConnect',
5112
5447
  description:
5113
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.',
5114
- isConfirmed: false,
5115
- verificationBlocked: true,
5116
- verificationBlockedReason: 'no-working-invocation',
5449
+ isConfirmed: true,
5117
5450
  differsFromOfficialDocs: true,
5118
5451
  officialDocsNote:
5119
- '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.',
5120
5453
  params: [
5121
5454
  {
5122
5455
  name: 'originationNumber',
@@ -5142,6 +5475,8 @@ export const FUNCTIONS = [
5142
5475
  },
5143
5476
  {
5144
5477
  name: 'SetStateMscrmRecord',
5478
+ supportedInCloudPage: false,
5479
+ supportedInEmail: false,
5145
5480
  mcnSince: null,
5146
5481
  handlebarsEquivalent: null,
5147
5482
  mcnNotes: null,
@@ -5187,6 +5522,8 @@ export const FUNCTIONS = [
5187
5522
  },
5188
5523
  {
5189
5524
  name: 'SHA1',
5525
+ supportedInCloudPage: true,
5526
+ supportedInEmail: true,
5190
5527
  mcnSince: null,
5191
5528
  handlebarsEquivalent: null,
5192
5529
  mcnNotes: null,
@@ -5226,6 +5563,8 @@ export const FUNCTIONS = [
5226
5563
  },
5227
5564
  {
5228
5565
  name: 'SHA256',
5566
+ supportedInCloudPage: true,
5567
+ supportedInEmail: true,
5229
5568
  mcnSince: null,
5230
5569
  handlebarsEquivalent: null,
5231
5570
  mcnNotes: null,
@@ -5265,6 +5604,8 @@ export const FUNCTIONS = [
5265
5604
  },
5266
5605
  {
5267
5606
  name: 'SHA512',
5607
+ supportedInCloudPage: true,
5608
+ supportedInEmail: true,
5268
5609
  mcnSince: null,
5269
5610
  handlebarsEquivalent: null,
5270
5611
  mcnNotes: null,
@@ -5304,6 +5645,8 @@ export const FUNCTIONS = [
5304
5645
  },
5305
5646
  {
5306
5647
  name: 'StringToDate',
5648
+ supportedInCloudPage: true,
5649
+ supportedInEmail: true,
5307
5650
  mcnSince: 67,
5308
5651
  handlebarsEquivalent: null,
5309
5652
  mcnNotes:
@@ -5334,6 +5677,8 @@ export const FUNCTIONS = [
5334
5677
  },
5335
5678
  {
5336
5679
  name: 'StringToHex',
5680
+ supportedInCloudPage: true,
5681
+ supportedInEmail: true,
5337
5682
  mcnSince: null,
5338
5683
  handlebarsEquivalent: null,
5339
5684
  mcnNotes: null,
@@ -5372,6 +5717,8 @@ export const FUNCTIONS = [
5372
5717
  },
5373
5718
  {
5374
5719
  name: 'Substring',
5720
+ supportedInCloudPage: true,
5721
+ supportedInEmail: true,
5375
5722
  mcnSince: 67,
5376
5723
  handlebarsEquivalent: 'substring',
5377
5724
  handlebarsExact: true,
@@ -5411,6 +5758,8 @@ export const FUNCTIONS = [
5411
5758
  },
5412
5759
  {
5413
5760
  name: 'Subtract',
5761
+ supportedInCloudPage: true,
5762
+ supportedInEmail: true,
5414
5763
  mcnSince: 67,
5415
5764
  handlebarsEquivalent: 'subtract',
5416
5765
  handlebarsExact: true,
@@ -5435,6 +5784,8 @@ export const FUNCTIONS = [
5435
5784
  },
5436
5785
  {
5437
5786
  name: 'SystemDateToLocalDate',
5787
+ supportedInCloudPage: true,
5788
+ supportedInEmail: true,
5438
5789
  mcnSince: null,
5439
5790
  handlebarsEquivalent: 'timeZoneConversion',
5440
5791
  handlebarsExact: false,
@@ -5465,6 +5816,8 @@ export const FUNCTIONS = [
5465
5816
  },
5466
5817
  {
5467
5818
  name: 'TransformXML',
5819
+ supportedInCloudPage: true,
5820
+ supportedInEmail: true,
5468
5821
  mcnSince: null,
5469
5822
  handlebarsEquivalent: null,
5470
5823
  mcnNotes: null,
@@ -5487,6 +5840,8 @@ export const FUNCTIONS = [
5487
5840
  },
5488
5841
  {
5489
5842
  name: 'TreatAsContent',
5843
+ supportedInCloudPage: true,
5844
+ supportedInEmail: true,
5490
5845
  mcnSince: null,
5491
5846
  handlebarsEquivalent: null,
5492
5847
  mcnNotes: null,
@@ -5516,6 +5871,8 @@ export const FUNCTIONS = [
5516
5871
  },
5517
5872
  {
5518
5873
  name: 'TreatAsContentArea',
5874
+ supportedInCloudPage: true,
5875
+ supportedInEmail: true,
5519
5876
  mcnSince: null,
5520
5877
  handlebarsEquivalent: null,
5521
5878
  mcnNotes: null,
@@ -5548,6 +5905,8 @@ export const FUNCTIONS = [
5548
5905
  },
5549
5906
  {
5550
5907
  name: 'Trim',
5908
+ supportedInCloudPage: true,
5909
+ supportedInEmail: true,
5551
5910
  mcnSince: 67,
5552
5911
  handlebarsEquivalent: 'trim',
5553
5912
  handlebarsExact: true,
@@ -5572,6 +5931,8 @@ export const FUNCTIONS = [
5572
5931
  },
5573
5932
  {
5574
5933
  name: 'UpdateData',
5934
+ supportedInCloudPage: true,
5935
+ supportedInEmail: false,
5575
5936
  mcnSince: null,
5576
5937
  handlebarsEquivalent: null,
5577
5938
  mcnNotes: null,
@@ -5579,7 +5940,9 @@ export const FUNCTIONS = [
5579
5940
  guideUrl: 'https://ampscript.guide/updatedata/',
5580
5941
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/updatedata/',
5581
5942
  isConfirmed: true,
5582
- 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.',
5583
5946
  minArgs: 6,
5584
5947
  maxArgs: INF,
5585
5948
  category: 'Data Extension',
@@ -5640,6 +6003,8 @@ export const FUNCTIONS = [
5640
6003
  },
5641
6004
  {
5642
6005
  name: 'UpdateDE',
6006
+ supportedInCloudPage: true,
6007
+ supportedInEmail: true,
5643
6008
  mcnSince: null,
5644
6009
  handlebarsEquivalent: null,
5645
6010
  mcnNotes: null,
@@ -5708,6 +6073,8 @@ export const FUNCTIONS = [
5708
6073
  },
5709
6074
  {
5710
6075
  name: 'UpdateMSCRMRecords',
6076
+ supportedInCloudPage: false,
6077
+ supportedInEmail: false,
5711
6078
  mcnSince: null,
5712
6079
  handlebarsEquivalent: null,
5713
6080
  mcnNotes: null,
@@ -5762,6 +6129,8 @@ export const FUNCTIONS = [
5762
6129
  },
5763
6130
  {
5764
6131
  name: 'UpdateSingleSalesforceObject',
6132
+ supportedInCloudPage: true,
6133
+ supportedInEmail: true,
5765
6134
  mcnSince: null,
5766
6135
  handlebarsEquivalent: null,
5767
6136
  mcnNotes: null,
@@ -5777,7 +6146,7 @@ export const FUNCTIONS = [
5777
6146
  isConfirmed: true,
5778
6147
  differsFromOfficialDocs: false,
5779
6148
  officialDocsNote:
5780
- '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.',
5781
6150
  params: [
5782
6151
  {
5783
6152
  name: 'objectName',
@@ -5808,6 +6177,8 @@ export const FUNCTIONS = [
5808
6177
  },
5809
6178
  {
5810
6179
  name: 'Uppercase',
6180
+ supportedInCloudPage: true,
6181
+ supportedInEmail: true,
5811
6182
  mcnSince: 67,
5812
6183
  handlebarsEquivalent: 'uppercase',
5813
6184
  handlebarsExact: true,
@@ -5836,6 +6207,8 @@ export const FUNCTIONS = [
5836
6207
  },
5837
6208
  {
5838
6209
  name: 'UpsertContact',
6210
+ supportedInCloudPage: true,
6211
+ supportedInEmail: true,
5839
6212
  mcnSince: null,
5840
6213
  handlebarsEquivalent: null,
5841
6214
  mcnNotes: null,
@@ -5850,7 +6223,7 @@ export const FUNCTIONS = [
5850
6223
  isConfirmed: true,
5851
6224
  differsFromOfficialDocs: false,
5852
6225
  officialDocsNote:
5853
- '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.',
5854
6227
  params: [
5855
6228
  {
5856
6229
  name: 'channel',
@@ -5898,6 +6271,8 @@ export const FUNCTIONS = [
5898
6271
  },
5899
6272
  {
5900
6273
  name: 'UpsertData',
6274
+ supportedInCloudPage: true,
6275
+ supportedInEmail: false,
5901
6276
  mcnSince: null,
5902
6277
  handlebarsEquivalent: null,
5903
6278
  mcnNotes: null,
@@ -5905,7 +6280,9 @@ export const FUNCTIONS = [
5905
6280
  guideUrl: 'https://ampscript.guide/upsertdata/',
5906
6281
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/upsertdata/',
5907
6282
  isConfirmed: true,
5908
- 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.',
5909
6286
  minArgs: 6,
5910
6287
  maxArgs: INF,
5911
6288
  category: 'Data Extension',
@@ -5976,6 +6353,8 @@ export const FUNCTIONS = [
5976
6353
  },
5977
6354
  {
5978
6355
  name: 'UpsertDE',
6356
+ supportedInCloudPage: true,
6357
+ supportedInEmail: true,
5979
6358
  mcnSince: null,
5980
6359
  handlebarsEquivalent: null,
5981
6360
  mcnNotes: null,
@@ -6054,6 +6433,8 @@ export const FUNCTIONS = [
6054
6433
  },
6055
6434
  {
6056
6435
  name: 'UpsertMSCRMRecord',
6436
+ supportedInCloudPage: false,
6437
+ supportedInEmail: false,
6057
6438
  mcnSince: null,
6058
6439
  handlebarsEquivalent: null,
6059
6440
  mcnNotes: null,
@@ -6126,6 +6507,8 @@ export const FUNCTIONS = [
6126
6507
  },
6127
6508
  {
6128
6509
  name: 'URLEncode',
6510
+ supportedInCloudPage: true,
6511
+ supportedInEmail: true,
6129
6512
  mcnSince: null,
6130
6513
  handlebarsEquivalent: null,
6131
6514
  mcnNotes: null,
@@ -6170,6 +6553,8 @@ export const FUNCTIONS = [
6170
6553
  },
6171
6554
  {
6172
6555
  name: 'Verb',
6556
+ supportedInCloudPage: false,
6557
+ supportedInEmail: false,
6173
6558
  mcnSince: null,
6174
6559
  handlebarsEquivalent: null,
6175
6560
  mcnNotes: null,
@@ -6184,7 +6569,7 @@ export const FUNCTIONS = [
6184
6569
  verificationBlocked: true,
6185
6570
  verificationBlockedReason: 'no-working-invocation',
6186
6571
  officialDocsNote:
6187
- '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.',
6188
6573
  params: [],
6189
6574
  returnType: 'string',
6190
6575
  returnDescription: 'The keyword (first word) of the inbound mobile-originated message.',
@@ -6193,6 +6578,8 @@ export const FUNCTIONS = [
6193
6578
  },
6194
6579
  {
6195
6580
  name: 'v',
6581
+ supportedInCloudPage: true,
6582
+ supportedInEmail: true,
6196
6583
  mcnSince: 67,
6197
6584
  handlebarsEquivalent: null,
6198
6585
  mcnNotes: null,
@@ -6219,6 +6606,8 @@ export const FUNCTIONS = [
6219
6606
  },
6220
6607
  {
6221
6608
  name: 'WAT',
6609
+ supportedInCloudPage: false,
6610
+ supportedInEmail: false,
6222
6611
  mcnSince: null,
6223
6612
  handlebarsEquivalent: null,
6224
6613
  mcnNotes: null,
@@ -6255,10 +6644,14 @@ export const FUNCTIONS = [
6255
6644
  example: "%%=WAT('Omniture', '1234', '5678')=%%",
6256
6645
  isConfirmed: false,
6257
6646
  verificationBlocked: true,
6258
- 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.',
6259
6650
  },
6260
6651
  {
6261
6652
  name: 'WATP',
6653
+ supportedInCloudPage: false,
6654
+ supportedInEmail: false,
6262
6655
  mcnSince: null,
6263
6656
  handlebarsEquivalent: null,
6264
6657
  mcnNotes: null,
@@ -6287,6 +6680,8 @@ export const FUNCTIONS = [
6287
6680
  },
6288
6681
  {
6289
6682
  name: 'WrapLongURL',
6683
+ supportedInCloudPage: true,
6684
+ supportedInEmail: true,
6290
6685
  mcnSince: null,
6291
6686
  handlebarsEquivalent: null,
6292
6687
  mcnNotes: null,
@@ -6300,7 +6695,7 @@ export const FUNCTIONS = [
6300
6695
  isConfirmed: true,
6301
6696
  differsFromOfficialDocs: true,
6302
6697
  officialDocsNote:
6303
- '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.',
6304
6699
  sfmcGuideUrl: 'https://sfmc.guide/engagement/ampscript/functions/wraplongurl/',
6305
6700
  params: [{ name: 'url', description: 'URL to shorten', type: 'string|number' }],
6306
6701
  returnType: 'string',