Sage 100

Check for null values and blanks.  Sage usually cleans those up for work tables, but that would depend on their programming.

@Phil McIntosh I have tested it on Standard and Advanced.

@Kevin Moyes it seems to be complaining about the formula field @AgeingDate which comes from the report screen at runtime. Definitely not blank.

The formula works if I replace @AgeingDate with another date field, say InvoiceDate, and also works if I use #3/7/2023#

Check for null values and blanks.  Sage usually cleans those up for work tables, but that would depend on their programming.

If it's a formula field, make sure you include the curly brackets.

@Phil McIntosh I have tested it on Standard and Advanced.

@Kevin Moyes it seems to be complaining about the formula field @AgeingDate which comes from the report screen at runtime. Definitely not blank.

The formula works if I replace @AgeingDate with another date field, say InvoiceDate, and also works if I use #3/7/2023#

Check for null values and blanks.  Sage usually cleans those up for work tables, but that would depend on their programming.

It does have the curly brackets, there are no syntax errors, the formula verifies. When I typed it above I was abbreviating for clarity.

If it's a formula field, make sure you include the curly brackets.

@Phil McIntosh I have tested it on Standard and Advanced.

@Kevin Moyes it seems to be complaining about the formula field @AgeingDate which comes from the report screen at runtime. Definitely not blank.

The formula works if I replace @AgeingDate with another date field, say InvoiceDate, and also works if I use #3/7/2023#

Check for null values and blanks.  Sage usually cleans those up for work tables, but that would depend on their programming.

From the report screen at runtime?  You mean a report parameter?  Make sure it is set to Date type, and not as a range, nor allowing multiple values.

It does have the curly brackets, there are no syntax errors, the formula verifies. When I typed it above I was abbreviating for clarity.

If it's a formula field, make sure you include the curly brackets.

@Phil McIntosh I have tested it on Standard and Advanced.

@Kevin Moyes it seems to be complaining about the formula field @AgeingDate which comes from the report screen at runtime. Definitely not blank.

The formula works if I replace @AgeingDate with another date field, say InvoiceDate, and also works if I use #3/7/2023#

Check for null values and blanks.  Sage usually cleans those up for work tables, but that would depend on their programming.

From the report screen at runtime?  You mean a report parameter?  Make sure it is set to Date type, and not as a range, nor allowing multiple values.

It does have the curly brackets, there are no syntax errors, the formula verifies. When I typed it above I was abbreviating for clarity.

If it's a formula field, make sure you include the curly brackets.

@Phil McIntosh I have tested it on Standard and Advanced.

@Kevin Moyes it seems to be complaining about the formula field @AgeingDate which comes from the report screen at runtime. Definitely not blank.

The formula works if I replace @AgeingDate with another date field, say InvoiceDate, and also works if I use #3/7/2023#

Check for null values and blanks.  Sage usually cleans those up for work tables, but that would depend on their programming.

Now that I have looked to confirm the formula, expecting it to be Formula = "", it's actually Formula = CurrentDate.

You know what happens when you assume!

So maybe my work around of adding a parameter for AgeingDate (they have to enter the same date as on the report screen) is the best option?

From the report screen at runtime?  You mean a report parameter?  Make sure it is set to Date type, and not as a range, nor allowing multiple values.

It does have the curly brackets, there are no syntax errors, the formula verifies. When I typed it above I was abbreviating for clarity.

If it's a formula field, make sure you include the curly brackets.

@Phil McIntosh I have tested it on Standard and Advanced.

@Kevin Moyes it seems to be complaining about the formula field @AgeingDate which comes from the report screen at runtime. Definitely not blank.

The formula works if I replace @AgeingDate with another date field, say InvoiceDate, and also works if I use #3/7/2023#

Check for null values and blanks.  Sage usually cleans those up for work tables, but that would depend on their programming.

Just confirmed - the field @AgeingDate is set to whatever is entered on the report screen, despite the formula being set to CurrentDate.

 So why does it not work in the DateDiff formula?

Now that I have looked to confirm the formula, expecting it to be Formula = "", it's actually Formula = CurrentDate.

You know what happens when you assume!

So maybe my work around of adding a parameter for AgeingDate (they have to enter the same date as on the report screen) is the best option?

From the report screen at runtime?  You mean a report parameter?  Make sure it is set to Date type, and not as a range, nor allowing multiple values.

It does have the curly brackets, there are no syntax errors, the formula verifies. When I typed it above I was abbreviating for clarity.

If it's a formula field, make sure you include the curly brackets.

@Phil McIntosh I have tested it on Standard and Advanced.

@Kevin Moyes it seems to be complaining about the formula field @AgeingDate which comes from the report screen at runtime. Definitely not blank.

The formula works if I replace @AgeingDate with another date field, say InvoiceDate, and also works if I use #3/7/2023#

Check for null values and blanks.  Sage usually cleans those up for work tables, but that would depend on their programming.

It's probably coming in as text.  Add another formula to convert that field to a date?

Just confirmed - the field @AgeingDate is set to whatever is entered on the report screen, despite the formula being set to CurrentDate.

 So why does it not work in the DateDiff formula?

Now that I have looked to confirm the formula, expecting it to be Formula = "", it's actually Formula = CurrentDate.

You know what happens when you assume!

So maybe my work around of adding a parameter for AgeingDate (they have to enter the same date as on the report screen) is the best option?

From the report screen at runtime?  You mean a report parameter?  Make sure it is set to Date type, and not as a range, nor allowing multiple values.

It does have the curly brackets, there are no syntax errors, the formula verifies. When I typed it above I was abbreviating for clarity.

If it's a formula field, make sure you include the curly brackets.

@Phil McIntosh I have tested it on Standard and Advanced.

@Kevin Moyes it seems to be complaining about the formula field @AgeingDate which comes from the report screen at runtime. Definitely not blank.

The formula works if I replace @AgeingDate with another date field, say InvoiceDate, and also works if I use #3/7/2023#

Check for null values and blanks.  Sage usually cleans those up for work tables, but that would depend on their programming.