I'm evaluating Insights 2.1 on Portal 10.5.1.
I am attempting to access spatial data from Lat, Long columns in a table drawn from a SQL Server table view. The source data has approximately 242,000 records (parcel centroids for a local county government). I can load the table without issue into Insights, but if I attempt to enable a location (using the Lat, Long coordinates) I get a message that says "Something went wrong". No more details.
This seems to be a problem with the SIZE of the table to process. I CAN enable location on an subset of the source data using a SQL "select top 10000" table view.
I just want to confirm that this IS a limitation with the number of location features? Is there a work around? I have also added a HOSTED feature service layer and this is able to display successfully, but I cannot link the Hosted feature services to SQL Server business tables.
Is there a better approach to getting large number of geospatially enabled features into Insights, and get them linked up with SQL Server business tables?