In my budget app, when I want to add a new transaction I'm getting inconsistent behavior utilizing formula using data in the row I'm adding.
Scenario 1 : I use ACCOUNT NAME to automatically search and set ACCOUNT ID and ACCOUNT # automatically from a list and set them as Initial Value using SELECT and [_THIS.ROW].[ACCOUNT NAME]. Everything works as intended. I can even switch Account Name in the form and Initial Values of ID and # update accordingly after form submission.
But when working with a DATE in the form, I cannot ever get it to recognize manual values I want to input.
Scenario 2: I use DATE to set MONTH (formula calculating first day of the month from _THIS.ROW's DATE) and WEEK (formula calculating the date of the first day of the week from _THIS.ROW's DATE).
I get two completely different behaviors. If I set the Initial Value of DATE to be blank, then MONTH is blank and WEEK is 1/1/70 after I submit the form no matter what I put in the DATE of the form.
If I set the initial value of DATE to be TODAY() or any other DATE, MONTH and WEEK are set correctly based on the DATE of TODAY() even though I am setting a completely different date in the DATE column in the submission form.
Why are the behaviors inconsistent with DATE? I've even tried _THIS.ROW_AFTER and putting the formula in the "formula" and "Initial Value". All results in Scenario 2 above. I'd just like it to operate using the data I'm submitting in the form....Like it does with ACCOUNT NAME....
Any ideas why DATE is special?
Solved! Go to Solution.
You shouldn't be using THISROW in the bottom 2 expressions. It's only needed to disambiguate the context, like within a SELECT.
User | Count |
---|---|
18 | |
11 | |
7 | |
4 | |
3 |