There might be form elements that are visible to the user, but not connected to any attribute and therefore to any data in the database. They may have an empty data path property or don't have it at all. There also might exist form attributes that are not connected to any form element and therefore invisible to the user. But more often than not, we use connector to element attribute pairs. When we want a user to see and edit some database data. This is what we use a field form element for. The most natural way of establishing the connection between an attribute and an element looks like this. I'm just dragging the attribute I want to show under form and dropping it to the elements list. What the platform did here is it automatically added a new element of the field type white field, because this is how we display and added a single attribute value in one center price. We use fields. Every single element in this list is a field, as you can see. At the same time, all these fields are look and work quite differently. The description is a string felt I can type in like this. The product type is a dropdown list with enumeration values, and these three fields down here show drop downs with a recently used values allow adding a new value at this part. Or open the catalog choice form like this. How come the same element behaves that differently for a different attributes? Well, there are some settings as always same-old. First of all, the filled element cannot live without the data path property being set. I can't add a field element with an empty data path, but it will have no idea what it's doing here. One thing and show up on the forum. As soon as the filled element is connected to some attribute, it jumps on board and displays itself on the form. It also starts offering a bunch of functionality and appearance options, depending on the data type of the attribute it's connected to. First of all, there are types. Each of these is carefully honed for a very specific type of attribute data. When you drop an attribute to the element list, the platform gives it the best fit for the job type. But if you want to fill out the description using radio buttons for whatever reason, the platform won't try to stop you. A form element connected to a reference type attribute cannot be typed in by a user manually. Its value needs to be chosen from a list. Like this product type attribute, for example, which can accept on the product types enumeration values. Therefore, these kind of element has only these three options. There are only two values in this enumeration so it's perfectly logical to use radio buttons. Radio button field type requires a fixed list of failures to choose from. I'm going to the choice lists setting and click and fill. Looks like I can add any number of other values to the list. But this is not the case. I can use only values to the enumeration contains. I can delete some values though. If I don't need all of them in here. I can also select between these two appearances and this is how the tumbler looks like. As for the catalog graph type attributes like these three guys here, their values cannot be selected from the fixed list. The elements representing them on the forum feature a different kind of a dropdown, each shows that the recently chosen values allows me to add a new catalog item on the fly. I opened the selected item and added it. Or open the full catalog items list in a separate window like this. Chosen the correct field element type and setting up its main properties, which can be delegated to the platform, covers all typical needs when it comes to displaying and editing attributes. But of course we can set up the field element in almost any way imaginable if we so desire. For example, this is our servers buttons, arsenal. Let me show you some of them. This is a dropdown list button we've seen already. This is the choice list button we usually use to open the full list of values to choose from. We also have the clear button to delete the current value and the spin button to increase or decrease in numerical field value. The open button to open the item currently selected and so on. After we added these buttons, they can handle their events and to customize their behavior in any way we like. This is how we use the field elements.
