64-bit schemas
Last update: May 2, 2024
CREATED FOR:
- User
In order to facilite the transition from Campaign Standard to Campaign v8, several tables have been changed from 32 to 64 bits. Indeed, Campaign Standard supports 64-bit PK in several out-of-the-box schemas, whereas Campaign v8 supports 32-bit PK in most schemas.
Limitations
- This technical change only applies to customers migrating from Campaign Standard.
- Schema and broadlog extention is not supported in 64 bits. It will remain in 32 bits.
- Logs related to deliveries sent to technical users will not be available in Campaign v8.
- Only PostgreSQL is supported.
Modified schemas
Here is the list of schemas changed to 64 bits and their modified attributes.
| Schema name | Atribute name |
|---|---|
| nms:broadLogRcp | id |
| nms:trackingLogRcp | id |
| nms:excludeLogRcp | id |
| nms:broadLogVisitor | id |
| nms:trackingLogVisitor | id |
| nms:propositionRcp | interactionId |
| nms:propositionVisitor | interactionId |
| nms:webTrackingLog | id |
| nms:tmpBroadcast | message-id |
| nms:tmpMarketingPressure | message-id |
| nms:tmpBroadcastExclusion | message-id |
| nms:tmpBroadcastPaper | message-id |
| nms:broadLogAppSubRcp | id |
| nms:trackingLogAppSubRcp | id |
| nms:excludeLogAppSubRcp | id |
| nms:webEvent | broadLogSrc-id, broadLogRemkt-id |
| nms:broadLogMid | mktBroadLogId |
| nms:mirrorPageSearch | remoteMessageId |
Experience Cloud
