Ok, I don't think we are getting all the details to best help.
I setup a little test> I created a "Generate PO" table with column [Hot Linking] as a Date. I then setup a column in another table as a REF to capture the MAXROW() value. If this is setup correctly you will automatically get a Virtual Column in the Generate PO table. See image below.
With this setup, I am not seeing any issues. So the question is...what is different about your setup?
Generate PO Table with Virtual Column
Column to REF the Generate PO MAXROW()
MAXROW() Expression Parsed Result Looks Good
โ
Yes, please report it to AppSheet Support.
To get by the error, try removing the "true" parameter. Its not needed as it is assumed when the parameter is omitted.
However, the big question is what kind of data is "Hot Linking". It should be something that can be sorted to determine the max value of the row to be returned.
I added the "true" parameter to check if it's working. It's not working with both true or blank.
"Hot Linking" is a date data type. Hopefully Maxrow sorts dates
Ok, I don't think we are getting all the details to best help.
I setup a little test> I created a "Generate PO" table with column [Hot Linking] as a Date. I then setup a column in another table as a REF to capture the MAXROW() value. If this is setup correctly you will automatically get a Virtual Column in the Generate PO table. See image below.
With this setup, I am not seeing any issues. So the question is...what is different about your setup?
Generate PO Table with Virtual Column
Column to REF the Generate PO MAXROW()
MAXROW() Expression Parsed Result Looks Good
โ
Sorry My bad. I just realised Hotlinking was of datatype text instead of Date.
"Generate PO" should be a Table name
Generate PO is a table name
I am using this instead
INDEX(ORDERBY(Generate PO[PO Number],[Hot Linking],True),1)
@amyplin can you please check
User | Count |
---|---|
37 | |
30 | |
29 | |
20 | |
18 |