ACCESS_HISTORY view (Account Usage and Organization Usage): User-defined values in the objects_modified_by_ddl column

Attention

This behavior change is in the 2026_01 bundle.

For the current status of the bundle, refer to Bundle history.

With this behavior change, the objects_modified_by_ddl column of the ACCOUNT_USAGE.ACCESS_HISTORY and ORGANIZATION_USAGE.ACCESS_HISTORY views never uses a user-defined value as the key of a JSON key-value pair. The change behaves as follows:

Before the change:

User-specified values like column names and tag names are keys in the JSON object. For example:

{
  "columns": {
    "A": {
      "objectId": {"value": 0},
      "subOperationType": "ADD",
      "tags": {
        "DB1.SCH.TAG1": {
          "objectId": {"value": 0},
          "subOperationType": "ADD",
          "tagValue": {"value": "v1"}
        }
      }
    }
  }
}
After the change:

User-specified information is captured as a value of a key-value pair. For example:

{
  "columns": [
    {
      "objectName": "A",
      "objectId": {"value": 0},
      "subOperationType": "ADD",
      "tags": [
        {
          "objectName": "DB1.SCH.TAG1",
          "objectId": {"value": 0},
          "subOperationType": "ADD",
          "tagValue": {"value": "v1"}
        }
      ]
    }
  ]
}

Ref: 2178