Data source is not accessible

5376
12
10-22-2013 01:18 PM
BenStaud
New Contributor II
I have two, nearly identical, data sources.  One is hosted by a third party on their Arc Server.  The second is hosted by AGOL.  Both are feature services.
I have two operational views.  One using the Arc Server data source and one using the AGOL version.
The Operational View using the Arc Server hosted data works great.  However, the Operational View using the AGOL data displays fine in map view but, when you attempt to add a Widget for Summary or Query (other might also have this problem) I get partially through the Widget setup and I get the orange "Data source is not accessible" message icons.  Sometimes I can get the Widgets setup quickly enough that I can close the dialog and the Widget is completed.  But the Widget never display's any data.  And when I go back to configure the Widget again the data source is flagged with the orange icon.
I am logged in as the administrator for the AGOL and Operational Views so sharing should not be an issue.
This has been happening for over a week now.
Any help?
0 Kudos
12 Replies
Kylie
by Esri Regular Contributor
Esri Regular Contributor
Could you try setting your layer to be a static instead of dynamic (in the map widget configuration), and see if you still see the issue?
0 Kudos
BenStaud
New Contributor II
It did not help.  I still get the orange icons.  The count routine in summary will work but, the statistics in summary will not calculate and the query set-up dialog crashes almost upon opening.
0 Kudos
Kylie
by Esri Regular Contributor
Esri Regular Contributor
Could you share your hosted service and your op view using it with me? The easiest way is to create a group, share the service and op view with the group, and invite my ArcGIS Online user kylie_org to that group.
0 Kudos
HiranZani2
New Contributor III
I noticed the same issue. The bug seems to be associate with specific AGOL accounts rather than the feature service. The crash happens when an query or statitical widget is added...
0 Kudos
Kylie
by Esri Regular Contributor
Esri Regular Contributor
Hi Hiran -- Could you give me some more information about the accounts you are and aren't seeing it with? Also, could you share a map, the services, and an operation view with me (kylie_org) where I might be able to repro this? The easiest way to share is create a group, share the items with the group, and invite my user to the group.
0 Kudos
Kylie
by Esri Regular Contributor
Esri Regular Contributor
Hi Ben -- I just saw you did share some content with me... however, it looks like it is the map and op views, but not the hosted services. Could you share the services with me as well so that I can try and repro?
0 Kudos
mahmoudfadel2
New Contributor II

Hi Kylie Donia6I0Xl.jpg,

i need to extend the functionality of "Layers filter map tool" in dashboard by js api .

what i need to change in the default behavior is to have the abilty to filter more than one layer in the same time , also to make the condition between filters AND not OR

Could you help ?

Thanks

0 Kudos
HiranZani2
New Contributor III
Hi Kyle - I have shared with you both the OP View and the feature service. The error persists even with the OD 10.2 update. As I told you, works normally in old AGOL accounts. But when I add a query or a statics widget it suddenly disconnect the data source. I appreciate your help. Many thanks.
0 Kudos
DanielStauning
Esri Contributor
Hiran,

This behavior is being caused by a setting in the ArcGIS Online organization "Allow only standard SQL queries." If you disable this setting it will resolve your issue; My Organization > Edit Settings > Security > uncheck the box for "Allow only standard SQL queries." You'll have to be an administrator to do so.

The underlying problem is the 'where' parameter of 1=1 being invalid for query operations when executed with Output Statistics with this setting enabled. 1=1 is often used in the 'where' parameter to return all records when querying a dataset; this is how Operations Dashboard automatically formats the request for widgets that use statistics like sum and average. The fact that the widget configuration is failing because of this setting I consider to be a bug which I will document.

I hope this resolves your issue, please feel free to follow up to let us know if this work around does the trick.

- Daniel
0 Kudos