Forum Discussion

NikkiWalters's avatar
NikkiWalters
Qrew Cadet
7 years ago

Formula used for a secondary field for a field tracking changes

I have a multiple choice field tracking changes "SAM (2018)".  I added a second field "SAM (2018)* to act as a clean field for reporting and used this formula:  NotLeft(Right([SAM (2018)],"]"),0)

The formula is not pulling in just the name, it is also pulling in the separation lines.  See image below.  I have tried to adjust the formula without success.   Not sure where I am going wrong.  I only want it to pull "Unassigned" not  the --------------.  Any help would be appreciated.

  • ChrisChris's avatar
    ChrisChris
    Qrew Assistant Captain
    7 years ago

    Are the number of hyphens consistent? NotLeft(Right([SAM (2018)],"]"),14)

  • QuickBaseCoachD's avatar
    QuickBaseCoachD
    Qrew Captain
    7 years ago
    Do you really need those separation lines?  I think that they come in what you ask to have the data on separate lines in the logging field setup.
  • NikkiWalters's avatar
    NikkiWalters
    Qrew Cadet
    7 years ago

    Thanks for your help.   I changed the logging field to same line. This got rid of the dashes, but I am still unable to get it exact so that my data matches in my second field for filters & summaries. I have tried 0, -1, -2. with this formula  NotLeft(Right([SAM (2018)],"]"),-2)

    See below, all should be one summary line.

    Appreciate any additional ideas.

  • QuickBaseCoachD's avatar
    QuickBaseCoachD
    Qrew Captain
    7 years ago
    I suggest logging so that the new changes are at the bottom.  That is the default setting for the logging field.

    "Show new entries at the bottom of the field"

    Then this will work

    Trim(Right([my update field],"]"))