Hi Everyone,
Have an issue with filtering a GI through the REST API.
Below is the setup for my endpoint filter.
And this is my request body
I’m getting the below error
If I send a word like “test” instead of the actual ID then there is no error however if I send a number formatted as a string then it isn’t happy.
Has anyone seen this before / know a fix?
+17
I’m assuming that the code level and data type were different, hence you are getting this issue.
I’m assuming that the code level and data type were different, hence you are getting this issue.
Hi
+17
All looks good to me except that field INPUT MASK, you provided 99999…., which can allow only digits. Can you please change this input mask and verify?
+17
Can you please share the GI?
+17
+17
Do you have any logic implemented in the graph and assigning values?
Hi
I’m pretty sure that it has something to do with the field being filtered being a key field, I have another request that also passes a number as a string and has no issue however in that case the field is not a key.
+5
Are there more than one result using that ID? If it's a key field it is expecting a single response. If you send "123" does it give the same error?
Hi
+2
A couple of ideas
Could this be a naming convention issue I notice your Field Name for the table is ShopifyLocationID and the name of the Parameter for your GI that is used in the condition is also ShopifyLocationID… could it be getting confused?
By that I mean how is the Parameter vs the Field Identified in your Endpoint Mapping (I see in the first screen shot the parameter declared as the Filter but can’t see any more than the “Shopify Location ID” in the Mapped Field)…
I would try renaming this filter/remapping endpoint and see if you have the same issues…
The other option is I noticed you have this exposed via oData you could try filtering it in the URL parameter call and see if you get a similar error there, might give us a different error message to try to help find the issue...
Hi there,
I am working with the Rest API and ODATA4. to pull data from Acumatica.
The query syntax allows for the inclusion of a $filter parameter in the REST query to limit the data returned.
In the video presentations I can see a few of the comparisons supported: eq for equal, and I think that it does gt and lt for greater than less than etc - but I’m wondering if there’s some comprehensive documentation anywhere that would describe all the different types of filtering you could do for example “in” (as like a sql “in” statement) would be very useful. A search on the website didn’t reveal anything.
Many thanks in advance,
Daniel Graham
Thanks very much for this - that’s hugely helpful.
Daniel Graham
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
