hubspot-api-client 10.0.0 → 11.1.0

data/lib/hubspot/codegen/cms/hubdb/models/hub_db_table_row_v3.rb

@@ -1,7 +1,7 @@
 =begin
 #HubDB endpoints
 
-#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `live` versions and you can publish and unpublish the live version. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, pushed to live version, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
+#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 
 The version of the OpenAPI document: v3
 
@@ -28,6 +28,9 @@ module Hubspot
         # Timestamp at which the row is created
         attr_accessor :created_at
 
+        # Timestamp at which the row is updated last time
+        attr_accessor :updated_at
+
         # Specifies the value for the column child table id
         attr_accessor :child_table_id
 
@@ -41,6 +44,7 @@ module Hubspot
             :'path' => :'path',
             :'name' => :'name',
             :'created_at' => :'createdAt',
+            :'updated_at' => :'updatedAt',
             :'child_table_id' => :'childTableId',
             :'values' => :'values'
           }
@@ -53,6 +57,7 @@ module Hubspot
             :'path' => :'String',
             :'name' => :'String',
             :'created_at' => :'DateTime',
+            :'updated_at' => :'DateTime',
             :'child_table_id' => :'String',
             :'values' => :'Hash<String, Object>'
           }
@@ -95,6 +100,10 @@ module Hubspot
             self.created_at = attributes[:'created_at']
           end
 
+          if attributes.key?(:'updated_at')
+            self.updated_at = attributes[:'updated_at']
+          end
+
           if attributes.key?(:'child_table_id')
             self.child_table_id = attributes[:'child_table_id']
           end
@@ -110,26 +119,6 @@ module Hubspot
         # @return Array for valid properties with the reasons
         def list_invalid_properties
           invalid_properties = Array.new
-          if @id.nil?
-            invalid_properties.push('invalid value for "id", id cannot be nil.')
-          end
-
-          if @path.nil?
-            invalid_properties.push('invalid value for "path", path cannot be nil.')
-          end
-
-          if @name.nil?
-            invalid_properties.push('invalid value for "name", name cannot be nil.')
-          end
-
-          if @created_at.nil?
-            invalid_properties.push('invalid value for "created_at", created_at cannot be nil.')
-          end
-
-          if @child_table_id.nil?
-            invalid_properties.push('invalid value for "child_table_id", child_table_id cannot be nil.')
-          end
-
           if @values.nil?
             invalid_properties.push('invalid value for "values", values cannot be nil.')
           end
@@ -140,11 +129,6 @@ module Hubspot
         # Check to see if the all the properties in the model are valid
         # @return true if the model is valid
         def valid?
-          return false if @id.nil?
-          return false if @path.nil?
-          return false if @name.nil?
-          return false if @created_at.nil?
-          return false if @child_table_id.nil?
           return false if @values.nil?
           true
         end
@@ -158,6 +142,7 @@ module Hubspot
               path == o.path &&
               name == o.name &&
               created_at == o.created_at &&
+              updated_at == o.updated_at &&
               child_table_id == o.child_table_id &&
               values == o.values
         end
@@ -171,7 +156,7 @@ module Hubspot
         # Calculates hash code according to all attributes.
         # @return [Integer] Hash code
         def hash
-          [id, path, name, created_at, child_table_id, values].hash
+          [id, path, name, created_at, updated_at, child_table_id, values].hash
         end
 
         # Builds the object from hash

data/lib/hubspot/codegen/cms/hubdb/models/{hub_db_table_row_v3_input.rb → hub_db_table_row_v3_request.rb}

@@ -1,7 +1,7 @@
 =begin
 #HubDB endpoints
 
-#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `live` versions and you can publish and unpublish the live version. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, pushed to live version, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
+#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 
 The version of the OpenAPI document: v3
 
@@ -15,26 +15,26 @@ require 'date'
 module Hubspot
   module Cms
     module Hubdb
-      class HubDbTableRowV3Input
+      class HubDbTableRowV3Request
         # Specifies the value for `hs_path` column, which will be used as slug in the dynamic pages
         attr_accessor :path
 
+        # Specifies the value for `hs_name` column, which will be used as title in the dynamic pages
+        attr_accessor :name
+
         # Specifies the value for the column child table id
         attr_accessor :child_table_id
 
-        # Object of key value pairs with the column name and column value
+        # List of key value pairs with the column name and column value
         attr_accessor :values
 
-        # Specifies the value for `hs_name` column, which will be used as title in the dynamic pages
-        attr_accessor :name
-
         # Attribute mapping from ruby-style variable name to JSON key.
         def self.attribute_map
           {
             :'path' => :'path',
+            :'name' => :'name',
             :'child_table_id' => :'childTableId',
-            :'values' => :'values',
-            :'name' => :'name'
+            :'values' => :'values'
           }
         end
 
@@ -42,9 +42,9 @@ module Hubspot
         def self.openapi_types
           {
             :'path' => :'String',
-            :'child_table_id' => :'String',
-            :'values' => :'Hash<String, String>',
-            :'name' => :'String'
+            :'name' => :'String',
+            :'child_table_id' => :'Integer',
+            :'values' => :'Hash<String, Object>'
           }
         end
 
@@ -58,13 +58,13 @@ module Hubspot
         # @param [Hash] attributes Model attributes in the form of hash
         def initialize(attributes = {})
           if (!attributes.is_a?(Hash))
-            fail ArgumentError, "The input argument (attributes) must be a hash in `Hubspot::Cms::Hubdb::HubDbTableRowV3Input` initialize method"
+            fail ArgumentError, "The input argument (attributes) must be a hash in `Hubspot::Cms::Hubdb::HubDbTableRowV3Request` initialize method"
           end
 
           # check to see if the attribute exists and convert string to symbol for hash key
           attributes = attributes.each_with_object({}) { |(k, v), h|
             if (!self.class.attribute_map.key?(k.to_sym))
-              fail ArgumentError, "`#{k}` is not a valid attribute in `Hubspot::Cms::Hubdb::HubDbTableRowV3Input`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect
+              fail ArgumentError, "`#{k}` is not a valid attribute in `Hubspot::Cms::Hubdb::HubDbTableRowV3Request`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect
             end
             h[k.to_sym] = v
           }
@@ -73,6 +73,10 @@ module Hubspot
             self.path = attributes[:'path']
           end
 
+          if attributes.key?(:'name')
+            self.name = attributes[:'name']
+          end
+
           if attributes.key?(:'child_table_id')
             self.child_table_id = attributes[:'child_table_id']
           end
@@ -82,22 +86,23 @@ module Hubspot
               self.values = value
             end
           end
-
-          if attributes.key?(:'name')
-            self.name = attributes[:'name']
-          end
         end
 
         # Show invalid properties with the reasons. Usually used together with valid?
         # @return Array for valid properties with the reasons
         def list_invalid_properties
           invalid_properties = Array.new
+          if @values.nil?
+            invalid_properties.push('invalid value for "values", values cannot be nil.')
+          end
+
           invalid_properties
         end
 
         # Check to see if the all the properties in the model are valid
         # @return true if the model is valid
         def valid?
+          return false if @values.nil?
           true
         end
 
@@ -107,9 +112,9 @@ module Hubspot
           return true if self.equal?(o)
           self.class == o.class &&
               path == o.path &&
+              name == o.name &&
               child_table_id == o.child_table_id &&
-              values == o.values &&
-              name == o.name
+              values == o.values
         end
 
         # @see the `==` method
@@ -121,7 +126,7 @@ module Hubspot
         # Calculates hash code according to all attributes.
         # @return [Integer] Hash code
         def hash
-          [path, child_table_id, values, name].hash
+          [path, name, child_table_id, values].hash
         end
 
         # Builds the object from hash

data/lib/hubspot/codegen/cms/hubdb/models/hub_db_table_v3.rb

@@ -1,7 +1,7 @@
 =begin
 #HubDB endpoints
 
-#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `live` versions and you can publish and unpublish the live version. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, pushed to live version, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
+#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 
 The version of the OpenAPI document: v3
 

data/lib/hubspot/codegen/cms/hubdb/models/{hub_db_table_v3_input.rb → hub_db_table_v3_request.rb}

@@ -1,7 +1,7 @@
 =begin
 #HubDB endpoints
 
-#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `live` versions and you can publish and unpublish the live version. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, pushed to live version, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
+#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 
 The version of the OpenAPI document: v3
 
@@ -15,56 +15,56 @@ require 'date'
 module Hubspot
   module Cms
     module Hubdb
-      class HubDbTableV3Input
-        # Specifies the key value pairs of the metadata fields with the associated column ids  input
-        attr_accessor :dynamic_meta_tags
+      class HubDbTableV3Request
+        # Name of the table
+        attr_accessor :name
 
-        # Specifies whether the table can be read by public without authorization input
-        attr_accessor :allow_public_api_access
+        # Label of the table
+        attr_accessor :label
 
-        # Specifies whether the table can be used for creation of dynamic pages input
+        # Specifies whether the table can be used for creation of dynamic pages
         attr_accessor :use_for_pages
 
-        # List of columns in the table input
-        attr_accessor :columns
+        # Specifies whether the table can be read by public without authorization
+        attr_accessor :allow_public_api_access
 
-        # Name of the table input
-        attr_accessor :name
+        # Specifies whether child tables can be created
+        attr_accessor :allow_child_tables
 
-        # Specifies creation of multi-level dynamic pages using child tables input
+        # Specifies creation of multi-level dynamic pages using child tables
         attr_accessor :enable_child_table_pages
 
-        # Label of the table input
-        attr_accessor :label
+        # List of columns in the table
+        attr_accessor :columns
 
-        # Specifies whether child tables can be created input
-        attr_accessor :allow_child_tables
+        # Specifies the key value pairs of the metadata fields with the associated column ids
+        attr_accessor :dynamic_meta_tags
 
         # Attribute mapping from ruby-style variable name to JSON key.
         def self.attribute_map
           {
-            :'dynamic_meta_tags' => :'dynamicMetaTags',
-            :'allow_public_api_access' => :'allowPublicApiAccess',
-            :'use_for_pages' => :'useForPages',
-            :'columns' => :'columns',
             :'name' => :'name',
-            :'enable_child_table_pages' => :'enableChildTablePages',
             :'label' => :'label',
-            :'allow_child_tables' => :'allowChildTables'
+            :'use_for_pages' => :'useForPages',
+            :'allow_public_api_access' => :'allowPublicApiAccess',
+            :'allow_child_tables' => :'allowChildTables',
+            :'enable_child_table_pages' => :'enableChildTablePages',
+            :'columns' => :'columns',
+            :'dynamic_meta_tags' => :'dynamicMetaTags'
           }
         end
 
         # Attribute type mapping.
         def self.openapi_types
           {
-            :'dynamic_meta_tags' => :'Hash<String, Integer>',
-            :'allow_public_api_access' => :'Boolean',
-            :'use_for_pages' => :'Boolean',
-            :'columns' => :'Array<ColumnInput>',
             :'name' => :'String',
-            :'enable_child_table_pages' => :'Boolean',
             :'label' => :'String',
-            :'allow_child_tables' => :'Boolean'
+            :'use_for_pages' => :'Boolean',
+            :'allow_public_api_access' => :'Boolean',
+            :'allow_child_tables' => :'Boolean',
+            :'enable_child_table_pages' => :'Boolean',
+            :'columns' => :'Array<ColumnRequest>',
+            :'dynamic_meta_tags' => :'Hash<String, Integer>'
           }
         end
 
@@ -78,51 +78,51 @@ module Hubspot
         # @param [Hash] attributes Model attributes in the form of hash
         def initialize(attributes = {})
           if (!attributes.is_a?(Hash))
-            fail ArgumentError, "The input argument (attributes) must be a hash in `Hubspot::Cms::Hubdb::HubDbTableV3Input` initialize method"
+            fail ArgumentError, "The input argument (attributes) must be a hash in `Hubspot::Cms::Hubdb::HubDbTableV3Request` initialize method"
           end
 
           # check to see if the attribute exists and convert string to symbol for hash key
           attributes = attributes.each_with_object({}) { |(k, v), h|
             if (!self.class.attribute_map.key?(k.to_sym))
-              fail ArgumentError, "`#{k}` is not a valid attribute in `Hubspot::Cms::Hubdb::HubDbTableV3Input`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect
+              fail ArgumentError, "`#{k}` is not a valid attribute in `Hubspot::Cms::Hubdb::HubDbTableV3Request`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect
             end
             h[k.to_sym] = v
           }
 
-          if attributes.key?(:'dynamic_meta_tags')
-            if (value = attributes[:'dynamic_meta_tags']).is_a?(Hash)
-              self.dynamic_meta_tags = value
-            end
+          if attributes.key?(:'name')
+            self.name = attributes[:'name']
           end
 
-          if attributes.key?(:'allow_public_api_access')
-            self.allow_public_api_access = attributes[:'allow_public_api_access']
+          if attributes.key?(:'label')
+            self.label = attributes[:'label']
           end
 
           if attributes.key?(:'use_for_pages')
             self.use_for_pages = attributes[:'use_for_pages']
           end
 
-          if attributes.key?(:'columns')
-            if (value = attributes[:'columns']).is_a?(Array)
-              self.columns = value
-            end
+          if attributes.key?(:'allow_public_api_access')
+            self.allow_public_api_access = attributes[:'allow_public_api_access']
           end
 
-          if attributes.key?(:'name')
-            self.name = attributes[:'name']
+          if attributes.key?(:'allow_child_tables')
+            self.allow_child_tables = attributes[:'allow_child_tables']
           end
 
           if attributes.key?(:'enable_child_table_pages')
             self.enable_child_table_pages = attributes[:'enable_child_table_pages']
           end
 
-          if attributes.key?(:'label')
-            self.label = attributes[:'label']
+          if attributes.key?(:'columns')
+            if (value = attributes[:'columns']).is_a?(Array)
+              self.columns = value
+            end
           end
 
-          if attributes.key?(:'allow_child_tables')
-            self.allow_child_tables = attributes[:'allow_child_tables']
+          if attributes.key?(:'dynamic_meta_tags')
+            if (value = attributes[:'dynamic_meta_tags']).is_a?(Hash)
+              self.dynamic_meta_tags = value
+            end
           end
         end
 
@@ -154,14 +154,14 @@ module Hubspot
         def ==(o)
           return true if self.equal?(o)
           self.class == o.class &&
-              dynamic_meta_tags == o.dynamic_meta_tags &&
-              allow_public_api_access == o.allow_public_api_access &&
-              use_for_pages == o.use_for_pages &&
-              columns == o.columns &&
               name == o.name &&
-              enable_child_table_pages == o.enable_child_table_pages &&
               label == o.label &&
-              allow_child_tables == o.allow_child_tables
+              use_for_pages == o.use_for_pages &&
+              allow_public_api_access == o.allow_public_api_access &&
+              allow_child_tables == o.allow_child_tables &&
+              enable_child_table_pages == o.enable_child_table_pages &&
+              columns == o.columns &&
+              dynamic_meta_tags == o.dynamic_meta_tags
         end
 
         # @see the `==` method
@@ -173,7 +173,7 @@ module Hubspot
         # Calculates hash code according to all attributes.
         # @return [Integer] Hash code
         def hash
-          [dynamic_meta_tags, allow_public_api_access, use_for_pages, columns, name, enable_child_table_pages, label, allow_child_tables].hash
+          [name, label, use_for_pages, allow_public_api_access, allow_child_tables, enable_child_table_pages, columns, dynamic_meta_tags].hash
         end
 
         # Builds the object from hash

data/lib/hubspot/codegen/cms/hubdb/models/import_result.rb

@@ -1,7 +1,7 @@
 =begin
 #HubDB endpoints
 
-#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `live` versions and you can publish and unpublish the live version. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, pushed to live version, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
+#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 
 The version of the OpenAPI document: v3
 

data/lib/hubspot/codegen/cms/hubdb/models/next_page.rb

@@ -1,7 +1,7 @@
 =begin
 #HubDB endpoints
 
-#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `live` versions and you can publish and unpublish the live version. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, pushed to live version, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
+#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 
 The version of the OpenAPI document: v3
 

data/lib/hubspot/codegen/cms/hubdb/models/option.rb

@@ -1,7 +1,7 @@
 =begin
 #HubDB endpoints
 
-#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `live` versions and you can publish and unpublish the live version. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, pushed to live version, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the live version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
+#HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 
 The version of the OpenAPI document: v3