Why does reference field and associated summary field still work correctly despite this error?

  • 0
  • 1
  • Question
  • Updated 3 years ago
  • Answered
Take a look at the attachment......

Ok, first off, I actually do understand why this error is showing. It is because there is an existing summary field between these tables and because the RID field, which is part of the concatenate formula field, is a lookup field. Also, I recently changed the reference field from a normal text field to a formula text field.

The question then is, why does my summary field STILL WORK properly?  If I click OK to the error message and then cancel out of field properties, the summary still works.  

And what are the possible consequences to the data in my app?  Will that summary field always be correct?   

For your reference, if I attempt to create a brand new summary field, QuickBase will not let me and it again states the same error.  So I'm stuck with only the previously existing summary fields.
Photo of Robin CC

Robin CC

  • 200 Points 100 badge 2x thumb

Posted 3 years ago

  • 0
  • 1
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 64,658 Points 50k badge 2x thumb
In my experience, your app may give wrong results when you try that cheat. I had done that myself in the past to cheat and it can lead to weird and delayed results.