Forum Discussion
QBuserQBuser
8 years agoQrew Cadet
I am not sure I am following #1. What is the difference between looking up the customer id and relating it like you mention? Is the lookup field the issue or is the issue that I am using a Text Formula field in the relationship? Could I create a new field and use the ToText function to get around this?
Can you help me on how I would go about doing #2? I prefer that a button would not have to be clicked if possible. It would be good if it could run after the table is updated in the middle of the night.
Can you help me on how I would go about doing #2? I prefer that a button would not have to be clicked if possible. It would be good if it could run after the table is updated in the middle of the night.
- QBuserQBuser8 years agoQrew CadetMy Customer Field is actually a forecast group field from another table so that is why I am looking it up. Location is not a look up field. I also have reporting year which looks up the year based on dates from another table since the year runs September-August. My formula looks like
[Reporting Year]&" - "&[Month Text]&[Month Half]&[Forecast Group]&[FacName]
- QuickBaseCoachD8 years agoQrew CaptainThis sounds like it will require one on one assistance to sort out a solution. I can be contacted via my gmail address on my Contact me page. QuickBaseCoach.com
- QBuserQBuser8 years agoQrew CadetI gave this some more thought and figured out that I could replace my lookup fields with some IF statements to generate the data. This then fixed the summary error. I would have preferred looking up the values so that they are easier to update in the future, but looks like this is the best and easiest solution until quickbase fixes the issue.