# Set CSS in Data Design {% hint style="info" %} **Block Information** Available in: Page Flow Toolbox Category: Dynamic Style/CSS Block Type: [Regular](/app-editor/page-flow/block-anatomy.md#regular-block) {% endhint %} **`Set CSS in Data Design`** is a [regular block](/app-editor/page-flow/block-anatomy.md#regular-block) that allows you to add and/or remove [CSS classes](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/class) from elements that were generated using the [Content from Data Design](/app-editor/page-flow/toolbox-blocks/content-from-data-design.md) block and dynamically added to the page or form.

Set CSS in Data Design in block

The behavior of the block is similar to the [Set CSS](/app-editor/page-flow/toolbox-blocks/set-css.md) block, with some important differences: * Works only with elements generated using [Content from Data Design](/app-editor/page-flow/toolbox-blocks/content-from-data-design.md) block that are dynamically added. * Element Selection: You can only choose an element placed inside the selected [Data Design](/app-editor/page-editor/built-in-elements/data-design.md) element. The block consists of the following (from top to bottom): * *Data Design*: [Selectable Input](/app-editor/page-flow/block-anatomy.md#selectable-input) to choose the [Data Design](/app-editor/page-editor/built-in-elements/data-design.md) element whose element you want to target. * *Element*: [Selectable Input](/app-editor/page-flow/block-anatomy.md#selectable-input) to choose the element, within the selected [Data Design](/app-editor/page-editor/built-in-elements/data-design.md), you want to add/remove the CSS classes for. * *ID*: Optional [Value Parameter](/app-editor/page-flow/block-anatomy.md#value-parameters) that accepts a [*text*](/app-editor/page-flow/references/value-types.md) value representing the unique value that was provided to the [Content from Data Design](/app-editor/page-flow/toolbox-blocks/content-from-data-design.md) block. See below for more details. * *ID2*: Optional [Value Parameter](/app-editor/page-flow/block-anatomy.md#value-parameters) that accepts a [*text*](/app-editor/page-flow/references/value-types.md) value representing the secondary identifier that can be used to identify the desired element. See below for more details. * *Add Classes*: [Value Parameter](/app-editor/page-flow/block-anatomy.md#value-parameters) that accepts a [*text*](/app-editor/page-flow/references/value-types.md) value containing the classes (multiple classes can be separated by a space) to be added. Can be empty if you do not want to add any CSS classes. * *Remove Classes*: [Value Parameter](/app-editor/page-flow/block-anatomy.md#value-parameters) that accepts a [*text*](/app-editor/page-flow/references/value-types.md) value containing the classes (multiple classes can be separated by a space) to be removed. Can be empty if you do not want to remove any CSS classes. *** ## ID and ID2 usage The behavior of this block depends on the ID and ID2 [value parameters](/app-editor/page-flow/block-anatomy.md#value-parameters) and is detailed below: * ID and ID2 not provided: Operate on the selected element for all generated instances of the same [Data Design](/app-editor/page-editor/built-in-elements/data-design.md) element. * ID2 provided and ID not provided: Operate on the selected element for all generated instances of the same [Data Design](/app-editor/page-editor/built-in-elements/data-design.md) element with the same ID2 value. * ID provided and ID2 not provided: Operate on the selected element for all generated instances of the same [Data Design](/app-editor/page-editor/built-in-elements/data-design.md) element with the same ID value. Since we recommend the ID value to be unique, this would choose one from all the generated instances of the associated [Data Design](/app-editor/page-editor/built-in-elements/data-design.md) element. * ID and ID2 provided: Operate on the selected element for all generated instances of the same [Data Design](/app-editor/page-editor/built-in-elements/data-design.md) element with the same ID and ID2 value. *** ## Usage Examples {% hint style="info" %} **NOTE: Please refer to the prerequisite information shown** [**here**](/app-editor/page-flow/references/prerequisite-for-dynamic-content-block-examples.md) **before seeing the example.** {% endhint %} The image below shows an example in which the CSS class `table-info` is added to the [Text](/app-editor/page-editor/editing-text.md) element that displays the current stock price (*Text460*) for Company 2, which as rendered with the ID *ST101* .

Set CSS in Data Design block example 1

The result of the above example is highlighted below, where the stock price for the Company 2 is displayed with a different background color due to the CSS class `table-info` that was applied.

Result of example 1

In the second example, we will illustrate the situation where neither ID nor ID2 are provided. In this scenario, the system will alter the CSS classes for the same [Text](/app-editor/page-editor/editing-text.md) element (*Text460*) across all generated instances. Specifically, we are adding two classes: `bg-danger` (which sets the background color to red) and `text-light` (which sets the text color to white).

Set CSS in Data Design block example 2

The result of the above example is highlighted below where the [Text](/app-editor/page-editor/editing-text.md) element displaying the current stock price (*Text460*) shows text with a red background and white text for both the companies.

Result of example 2

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.zingy.ai/app-editor/page-flow/toolbox-blocks/set-css-in-data-design.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.