Formula Parser In JavaScript
THERE IS AN ASK OF YOU AT THE BOTTOM OF THIS POST - SKIP THE DETAILS IF YOU DON'T UNDERSTAND MY TECHNICAL RATIONALE As some of you may be aware I am deep into creating a QuickBase Formula Parer in ...
Forum Discussion
NEW ASK
I want your most complex formulas for testing my parser. I don't need any field values or other information just the raw formula as pasted into the textarea of the field editor page. Feel free to include formula variables, comments, poor formatting or even a formula that does not work.
You can enter your formulas here:
https://haversineconsulting.quickbase.com/db/bmn6xsqv2?a=nwr
Please only contribute formulas that are not confidential as at times others may view the submissions and I will be using them for testing with other developers.
I have added all the formulas listed in QuickBase's formula reference table but these formulas are rather simple. When entering your contributed formuls please selected the option "Contributed" for the Source field.
As this project progresses I will provide a script to extract all formulas from an application or perhaps even an account if you want to contribute to my testing efforts on a larger scale.
Thanks in advance.
I want your most complex formulas for testing my parser. I don't need any field values or other information just the raw formula as pasted into the textarea of the field editor page. Feel free to include formula variables, comments, poor formatting or even a formula that does not work.
You can enter your formulas here:
https://haversineconsulting.quickbase.com/db/bmn6xsqv2?a=nwr
Please only contribute formulas that are not confidential as at times others may view the submissions and I will be using them for testing with other developers.
I have added all the formulas listed in QuickBase's formula reference table but these formulas are rather simple. When entering your contributed formuls please selected the option "Contributed" for the Source field.
As this project progresses I will provide a script to extract all formulas from an application or perhaps even an account if you want to contribute to my testing efforts on a larger scale.
Thanks in advance.
- FWIW, my parser now works on all the examples in the formula function table
https://login.quickbase.com/db/6ewwzuuj?a=td
I only had two small errors dealing with unary operators and numbers starting with a leading period which were quickly corrected.
On the other hand I found at least four typos in QuickBase's documentation:
Nz([Mon]) + Nz([Tues] + Nz([Wed]) + Nz([Thurs]) + Nz([Fri])
https://login.quickbase.com/db/6ewwzuuj?a=dr&r=p
To WeekdayN([Order Date])
https://login.quickbase.com/db/6ewwzuuj?a=dr&r=e3
Nz([Length of Project], [Estimated Length of Project]
https://login.quickbase.com/db/6ewwzuuj?a=dr&r=fa
Month(ToDate("Jan 10, 2000")
https://login.quickbase.com/db/6ewwzuuj?a=dr&r=9
Can you spot the errors?
ASK: Please Give Me Your Formulas
https://community.quickbase.com/quickbase/topics/formula-parser-in-javascript#reply_18555784 - formula added.
- Thanks - this is extremely helpful to sound out errors and helps me refine the grammar.
Object nesting exceeded jsDump.maxDepth (100)
https://haversineconsulting.quickbase.com/db/bmn6xsqv2?a=dr&rid=332
FWIW, I think your formula could probably be naively improved.
And I am curious: are the hyphens in your formula labels being introduced by QuickBase relationships or did you explicitly name these formulas with hypens?
Either way, the first thing I would do to improve your formula natively would be so simplify the names so I could hold it in my head all at once. In this an other areas of QuickBase there is a lot of noise being generated in the naming of fields either due to tables having 1000s of fields orautomatically naming fields associated with relationships. - For full disclosure this formula was created a number of years ago before I had integrated MS Sql Server into our processes - I've since removed spaces from names. Those hyphens were not due to relationship naming, they were entered that way. I typically rename all relationship lookup fields from what Quickbase creates. The process that this particular formula is involved in has 1000+ fields involved, some of which contain values entered / calculated in quickbase, some with values from our legacy system etc. Was my first run at that type of thing and had to come up with a naming convention to keep it all straight once in quickbase. I do it somewhat differently now.
