I am trying to filter a date from the GI and the array is returning an error. The filter actually goes through correctly and I can see the filter details in the cell, but the query returns a #value error. Below is the valid filter. The last one is the date filter. It shows "and ARMStartdate le 2024-12-31T000:00:00:000Z" in the cell telling me it's valid. Why won't this work. I tried it with another date field and got the same error. The dates in the query are in MM/DD/YY format
Thank you. That would tend to indicate the that the filter (and, thus, the query) has gotten too long for the ERP to handle.
I would suggest sharing this information with the Velixo Help Desk (support@velixo.com). They may have suggestions for making the query more manageable. Alternatively, if the entire GI is fairly small, you could do what the message suggests and bring in the entire record set and then perform the filtering:
0 Votes
6 Comments
Sorted by
H
Harry Lewisposted
29 days ago
Admin
Can you show the "invalid" message?
0 Votes
D
David Racerposted
29 days ago
Sure #VALUE is showing in the formula box of the GI instead of the entire GI
0 Votes
H
Harry Lewisposted
29 days ago
Admin
When you select that cell and hover over the yellow triangle, what additional information is displayed?
0 Votes
D
David Racerposted
29 days ago
Could not recognize the ODATA syntax
Most likely your filter contains a function Which is not supported server side such as (tolower(), startswith() or contains ()
If possible try to reformulate the filter expression without using any unsupported function cells
Alternatively if this query is not too large to load without a filter consider enabling client side filtering for the inquiry in velixos Generic inquiry options
0 Votes
H
Harry Lewisposted
29 days ago
AdminAnswer
Thank you. That would tend to indicate the that the filter (and, thus, the query) has gotten too long for the ERP to handle.
I would suggest sharing this information with the Velixo Help Desk (support@velixo.com). They may have suggestions for making the query more manageable. Alternatively, if the entire GI is fairly small, you could do what the message suggests and bring in the entire record set and then perform the filtering:
0 Votes
I am trying to filter a date from the GI and the array is returning an error. The filter actually goes through correctly and I can see the filter details in the cell, but the query returns a #value error. Below is the valid filter. The last one is the date filter. It shows "and ARMStartdate le 2024-12-31T000:00:00:000Z" in the cell telling me it's valid. Why won't this work. I tried it with another date field and got the same error. The dates in the query are in MM/DD/YY format
=GIFILTER("Ithaka","DR-Weekly Sales report","Glaccount",B8:B19,"InventoryID","<>"&"""","Status",C8:C10,"ARMStartDate","<="&"12/31/24")
0 Votes
Harry Lewis posted 29 days ago Admin Best Answer
Thank you. That would tend to indicate the that the filter (and, thus, the query) has gotten too long for the ERP to handle.
I would suggest sharing this information with the Velixo Help Desk (support@velixo.com). They may have suggestions for making the query more manageable. Alternatively, if the entire GI is fairly small, you could do what the message suggests and bring in the entire record set and then perform the filtering:
0 Votes
6 Comments
Harry Lewis posted 29 days ago Admin
Can you show the "invalid" message?
0 Votes
David Racer posted 29 days ago
Sure #VALUE is showing in the formula box of the GI instead of the entire GI
0 Votes
Harry Lewis posted 29 days ago Admin
When you select that cell and hover over the yellow triangle, what additional information is displayed?
0 Votes
David Racer posted 29 days ago
Could not recognize the ODATA syntax
Most likely your filter contains a function Which is not supported server side such as (tolower(), startswith() or contains ()
If possible try to reformulate the filter expression without using any unsupported function cells
Alternatively if this query is not too large to load without a filter consider enabling client side filtering for the inquiry in velixos Generic inquiry options
0 Votes
Harry Lewis posted 29 days ago Admin Answer
Thank you. That would tend to indicate the that the filter (and, thus, the query) has gotten too long for the ERP to handle.
I would suggest sharing this information with the Velixo Help Desk (support@velixo.com). They may have suggestions for making the query more manageable. Alternatively, if the entire GI is fairly small, you could do what the message suggests and bring in the entire record set and then perform the filtering:
0 Votes
David Racer posted 29 days ago
Thanks. Will do
0 Votes
Login or Sign up to post a comment