Skip to main content
kavyam0002
kavyam0002
September 23, 2022
Solved

dropdown

  • September 23, 2022
  • 5 replies
  • 0 views

Hi

for this code am getting the error can someone suggest me what mistake i have done here

  a!dropdownField(
                  placeholderLabel: cons!CR_APP_TXT_PLACEHOLDER_VALUE,
                  disabled: ri!IsReadOnly_bool,
                  choiceLabels: touniformstring(
                    rule!APN_distinct(
                      index(
                        local!getContractIds_cdt,
                        "contractId_int", {}
                      ) ) ),
                  choiceValues: touniformstring(
                    rule!APN_distinct(
                      index(
                        local!getContractIds_cdt,
                        "contractId_int",
                        {} ) ) ),
                  value: if(
                    rule!APN_isEmpty( fv!item.value_txt ),
                    {},
                    apply(
                      trim(
                        _
                      ),
                      split(
                        fv!item.value_txt,
                        ";"
                      )
                    )
                  ),
                  saveInto: ri!crAPPContractExtension_cdt.value_txt
                ),

    Best answer by kavyam0002

    yes, i made mistake that saveinto was wrong - instead of saving into fv!item was used CDT- so it will use the multiple rows of that CDT to save the values

    5 replies

    D
    deepakg681722
    September 23, 2022

    You actual value which you stored is LD{someIntegerValue} but in your dropdown you are showing some other value(0,1 etc.)  that's why.

    U
    ujjwalr0002
    September 23, 2022

    Hi if you read the error it is because the radio button is not having the desired choice values as is mentioned clearly.

    It will only accept 0 and 1 as per your choice values setup

    harshitb6843
    harshitb6843
    September 23, 2022

    As Ujjwal said, Appian mostly throws errors that are easy to read and understand. My suggestion would be to READ the error and try to figure out what went wrong. 

      mikes0011
      mikes0011
      Brainy
      September 23, 2022
      Appian mostly throws errors that are easy to read and understand.

      for real. at least for this error message, it's pretty clear.

      The Expression Guru
      kavyam0002
      kavyam0002AuthorAnswer
      September 23, 2022

      yes, i made mistake that saveinto was wrong - instead of saving into fv!item was used CDT- so it will use the multiple rows of that CDT to save the values

        Terms & ConditionsAccessibility statement