Updated 029 How to overwrite the custom fields (markdown)

Amigo 2019-07-09 09:05:48 +02:00
parent 1adb8d1b93
commit d6d695e1c5

@ -6,13 +6,13 @@ It may happen that you would prefer to use some of the default fields in a diffe
* ### Example Of Default Fields Displayed in List view
In the Experts area the 'Id field', the 'State field' and as well as the Ordering field are shown. The Ordering field does not show the order number. To be able to move and order it, click on that "Up/Down" button(see video),. [00:01:45](https://www.youtube.com/watch?v=FHQfIhWHYyQ&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m45s) All that is done by default. The other values are not displayed in the List View. Once a client requested that it should be possible to see the date on which something had been created as well as the identity of the person who created it. Component Builder then needed to be adapted so that those things could also be overwritten. What has been done is: If a field is created in Component Builder, as a field would normally be created and any of these names should be given to it, 'Created by' or 'Created date', but exactly the same name. [00:02:23](https://www.youtube.com/watch?v=FHQfIhWHYyQ&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m23s) Then it will overwrite the default.<<<<<<<<<<<
In the Experts area the 'Id field', the 'Status field' and as well as the Ordering field are shown. The Ordering field does not show the order number. To be able to move and order it, click on that "Up/Down" button(see video),. [00:01:45](https://www.youtube.com/watch?v=FHQfIhWHYyQ&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m45s) All that is done by default. The other values are not displayed in the List View. Once a client requested that it should be possible to see the date on which something had been created as well as the identity of the person who created it. Component Builder then needed to be adapted so that those things could also be overwritten. What has been done is: If a field is created in Component Builder, as a field would normally be created and any of these names should be given to it, 'Created by' or 'Created date', but exactly the same name. [00:02:23](https://www.youtube.com/watch?v=FHQfIhWHYyQ&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m23s) Then it will override the default.
* ### Example Create_By Field In View
In this specific job order view, there is a field created-by. I can open that in a new tab, there is also a field created-date. let's open that one. [00:02:57](https://www.youtube.com/watch?v=FHQfIhWHYyQ&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m57s) So in the field that I used the name and created_by, it's a user is the type of field. The label is created by, and 'the user that created this' is the description. [00:03:26](https://www.youtube.com/watch?v=FHQfIhWHYyQ&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m26s) That's all that's needed for a user type. Then in the created-date, it's a calendar type. I used created, the date, it was created, the label and some of its defaults.
In this specific Job Order view, there is a field 'Created-by'. That may be opened in a new tab, there is also a field 'Created-date'. [00:02:57](https://www.youtube.com/watch?v=FHQfIhWHYyQ&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m57s) So in this field the 'Name' and 'Created_by', and 'User' is the type of field that is used. The label is 'Created by', and the user that 'Created this' is the description. [00:03:26](https://www.youtube.com/watch?v=FHQfIhWHYyQ&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h03m26s) That's all that is needed for a user type. Then in the Created-date, it's a calendar type. 'Created', the date, it was created, the label and some of its defaults are used.<<<<<<<<<<<<<<<,
### Compiled In Code