RE: Value not save in database

gayatria0439 — Mon, 25 Nov 2024 10:41:06 GMT

Point to remember:
The data will not be saved because it is a pre-populated value generated using variables based on the dropdown selection. As a result, this value will not be saved into ruleInput. If you wish to save the value of local!cashNotesvals into ruleInput, you should configure this in the submit button's saveInto property or in other editable or user-interaction fields by using a!save and ensure that a null check is performed. If the value is null, save the auto-populated value from the dropdown; if not, save the manually entered value.

RE: Value not save in database

Stefan Helzle — Sat, 11 Nov 2023 07:52:49 GMT

You store the entered value into three different variables. What is the reason for this?

Then you can simplify your code a lot:

a!paragraphField(
  label: "operations",
  showCharacterCount: true(),
  value: local!cashNotesval,
  saveInto: {
    ri!comments,
    local!cashNotesval,
    ri!Transaction.comment_txt,
  },
)

Then, which variable do you update in that drop down and which variable do you store to the database? In that dropdown, you have to make sure to modify the variable that you store to DB.