Welcome to the nuBuilder Forums!
Register and log in to access exclusive forums and content available only to registered users.
Register and log in to access exclusive forums and content available only to registered users.
BrowseForm coloring when EditForm fields change
-
kev1n
- nuBuilder Team
- Posts: 4299
- Joined: Sun Oct 14, 2018 6:43 pm
- Has thanked: 71 times
- Been thanked: 445 times
- Contact:
Re: BrowseForm coloring when EditForm fields change
How/where do you record that a field's value is changed?
-
kknm
- Posts: 366
- Joined: Sat Apr 11, 2020 12:03 am
- Has thanked: 3 times
- Been thanked: 4 times
- Contact:
Re: BrowseForm coloring when EditForm fields change
This is the question I wanted to ask you. Let me explain...
Let's say I have a directory of devices that have 10 characteristics each. I'm making a form in which I can change some of the characteristics. According to my knowledge, I would have to create a form with 10 old features and 10 new features in order to compare the fields. But this form will not fit on the screen. Therefore, I want to avoid creating 10 additional fields, and just mark the changed fields with a different color. It is enough for me to see that these fields have changed according to the date (only one additional field).
Let's say I have a directory of devices that have 10 characteristics each. I'm making a form in which I can change some of the characteristics. According to my knowledge, I would have to create a form with 10 old features and 10 new features in order to compare the fields. But this form will not fit on the screen. Therefore, I want to avoid creating 10 additional fields, and just mark the changed fields with a different color. It is enough for me to see that these fields have changed according to the date (only one additional field).
-
kev1n
- nuBuilder Team
- Posts: 4299
- Joined: Sun Oct 14, 2018 6:43 pm
- Has thanked: 71 times
- Been thanked: 445 times
- Contact:
Re: BrowseForm coloring when EditForm fields change
I am aware that this sounds a bit abstract but you could record the changes in a JSON structure.
When saving, it checks whether a field content has changed and if so, the corresponding field (with date) is logged. The JSON in turn is written to a single, additional field. This of course requires knowledge of JSON
When saving, it checks whether a field content has changed and if so, the corresponding field (with date) is logged. The JSON in turn is written to a single, additional field. This of course requires knowledge of JSON