Forum Discussion

DanSupport_'s avatar
DanSupport_
Quickbase Staff
9 years ago

Dealing with Oregon in field of state abbreviations?

Originally posted in the former community durning migration:





How best to deal with Oregon in field of state abbreviations?

"OR" creates problems when you run a search because it's read as the "or" function.  Looks odd to have one state spelled out. And, I'd much rather use the abbreviation for space concerns in various reports. So I'm hoping someone has figured out how to use the OR abbreviation.

Thanks in advance.
  • DanSupport_'s avatar
    DanSupport_
    Quickbase Staff
    Answer

    Just to make sure that you are aware, but the lower case "or" is treated normally and its only the upper case "OR" which is treated like specially.  Google works the same way.

    So if this is being built into a built in report, then you can just use the lower case.

    If its an then you would need to train your users.

    I have answered this question as a comment because I'm not sure if my answer solves your issue.  If it does solve it, you can answer in the answer box to close out this question.

    Mark


    Was this answer helpful?

    Comment/Answer by:

    Original
    Mark_Shnier , Your QuickBase Coach, Principal
    QuickBase Solution Provider 20 days ago



    • BrianCafferelli's avatar
      BrianCafferelli
      Quickbase Staff
      Also, when you are setting up your initial filters for a report you can use the lowercase "or" and it will match even if your field's use the uppercase "OR". For example, this filter will display all records where my State field is equal to "MA" or "OR":

      (State) (is equal to) (the value) (<other...>) (MA OR or)

      This way you do not have to change your data to the lowercase "or".
    • QuickBaseCoachD's avatar
      QuickBaseCoachD
      Qrew Captain
      btw, I have not personally tested this, but in the last release a week or so ago, Dynamic filters on OR as in the state of Oregon, now work.
    • BrianCafferelli's avatar
      BrianCafferelli
      Quickbase Staff
      Yes, that's right! Thank you for reminding me. :-) In the last release (June 2017), we resolved this bug: "QBE009714 - Filtering by a facet that contains OR/AND fails" so between that and the workaround for initial filters which I mentioned yesterday, it should be a bit easier to work with capital "OR" now.