When you purchase something from our store, as part of the buying and selling process, we collect the personal information you give us such as your name, address and email address. We'll also use the () method to create new upload resources - you can see all the alternative upload creation methods in the Create a new upload endpoint documentation.SECTION 1 - WHAT DO WE DO WITH YOUR INFORMATION? You need to specify the block model ID and all the fields, just like a normal record. In this example we'll use the buildBlockRecord() function to help us creating blocks more easily. The structured text field accepts three different types of blocks: This will allow us to compose the description by combining text and blocks of different kind. To make our dog's description more dynamic we are going to add a Structured text field. You just need to specify the block model ID and all the fields, like a normal record: The modular content field accepts three different types of blocks:Ī "Prize" block model (ID: 1235, API key: prize_block): Field API keyĪ "Description" block model (ID: 1236, API key: description_block): Field API keyĪ "Carousel" block model (ID: 1237, API key: carousel_block): Field API key This is our "Dog" model (ID: 1234, API key: dog): Field API key Each block model will have its set of fields and can be repeated as many times as needed. This will allow us to compose the description by combining multiple blocks of different kind. To make our dog's description more dynamic we are going to add a Modular content field. When a record is being created, this field must contain an Array of objects representing the inner block records: ![]() When a record is being read, this field returns an Array representing the IDs of the inner block records. This field accepts an Array representing the IDs of the linked records. This field accepts a String representing the ID of the linked record. ![]() This field accepts an Array of objects with the following properties: Property Focal point can only be specified for image assets.Īn object containing custom keys that you can use on your frontend projects Values must be expressed as Float between 0 and 1. Title for the asset, if you want to override the asset's default value (see Upload default_field_metadata)Īlternate text for the asset, if you want to override the asset's default value (see Upload default_field_metadata)įocal point for the asset, if you want to override the asset's default value (see Upload default_field_metadata). Unique identifier of the video within the provider The field accepts String values that satisfy the following regular expression: /^ (?:\- )*$/. ![]() The field accepts String values that are valid JSON. ![]() The field accepts an object with the following properties: Property If you're on legacy timezone management, remember that when sending an ISO8601 datetime you should keep in mind that the system will ignore any provided timezone, and will use the project's timezone instead. The field accepts String values in ISO 8601 date-time format (ie. The field accepts String values in ISO 8601 date format (ie.
0 Comments
Leave a Reply. |