Hi WAB community,
I am trying to figure out why the "in the last" query is not working in WAB developer edition. I tried with all other date queries such as: is on, is not on, is between, is after, and etc.are working fine. I have attached a screen shot, any body have an idea is it a bug or I am doing wrong?
Solved! Go to Solution.
Robert,
I discussed this with ESRI Tech, where he checked and figure out it is a bug. He will test with his own data to confirm the issue.
Thanks,
Irfan afsar
Irfan,
What does your browsers web console say when you apply that query? Have you looked at the network tab in your browsers developer tools to see what the SQL query that is submitted to the server looks like?
Robert,
Thanks, I really appreciate your response! In browser web console this is the message:
:3344/webappbuilder/apps/8/widgets/Query/SingleQueryLoader.js?wab_dv=2.5:297 Error: Failed to execute query.
at Object.f.load (js.arcgis.com/3.21/init.js:998)
at js.arcgis.com/3.21/init.js:87
at c (js.arcgis.com/3.21/init.js:103)
at d (js.arcgis.com/3.21/init.js:103)
at b.Deferred.resolve.callback (js.arcgis.com/3.21/init.js:105)
at c (js.arcgis.com/3.21/init.js:104)
at d (js.arcgis.com/3.21/init.js:103)
at b.Deferred.resolve.callback (js.arcgis.com/3.21/init.js:105)
at js.arcgis.com/3.21/init.js:92
at k (js.arcgis.com/3.21/init.js:107)
On network tab in developer tool I got that message:
Irfan,
OK, I ran a test on this as well and I can confirm that the "in the last" query does not work. You need to contact tech support and report this issue.
Robert,
I discussed this with ESRI Tech, where he checked and figure out it is a bug. He will test with his own data to confirm the issue.
Thanks,
Irfan afsar
OK, Don't forget to mark this question as answered by clicking on the "Correct Answer" link on the reply that answered your question.
Interesting, I also noticed this problem yesterday in the WAB hosted version on AGOL. I thought I was just setting up the query wrong .
I got the answer form esri tech some of arcgis server version have this bug too, but in my case this error was due to mistake in the hosted map service on arcgis server.