Customers Table ----< CustomersDonations Table >----- Donations Table
To add a donation I've created a portal in the customer details layout that views the CustomersDonations Table. When you add a line to the portal, it creates a new donation in the Donations Table.
That doesn't add up. Either your portal is to the Donations table instead of the CustomerDonations Table or adding a line in the portal is really adding a new record to CustomerDonations not Donations.
Telling us that you have modified a copy of "the invoices starter solution" doesn't tell us as much as you might think. Each version of FileMaker has a different version of this file. You modified the starter solution from which version of FileMaker?
Thanks for the reply!
I modified a copy from filemaker pro 13. I realize now that I have a field inside of the donations table that wants to calculate the fiscal year of each donation made this is referring to a field in company dashboard where the user can input the starting month of the company fiscal year.
I tried to make the field Company Dashboard::Fiscal Year Month global, but it still doesn't want to evaluate it. I wonder if it's how I'm writing my function? When I replace Company Dashboard::Fiscal Year Month with "04" (ie. April) the function evaluates perfectly. I would however prefer to call upon the global variable so the fiscal starting month can be customized by the user.
This calculation is being inside of the Donations Table.
months = Month(Get(CurrentDate)) - Company Dashboard::Fiscal Year Month ;
If( months > 0 ;
Year (Get(CurrentDate)) & "–" & Right (Year (Get(CurrentDate))+1; 2);
Year (Get(CurrentDate)) - 1 & "–" & Right (Year(Get(CurrentDate)) ; 2)
If you specify global storage for Company Dashboard::Fiscal Year Month, and this is a field of type calculation, not a number or text field with an auto-enter calculation. This should work as you want it to. That will, BTW, turn this calculation field into an unstored calculation due to the reference to a global field.
Thanks! I actually wanted to keep that field as a text input field so it could be customized by the user. I ended up creating a TO that worked just as well.