I have worked with polyline geometry in Insights without any problems, calculating additional fields and creating different charts:
In addition I have also done aggregation of lines inside polygons, which worked like a charm:
So what is your specific use case and how is your data stored? I used hosted feature services published to my portal.
This months Insights 2.3 was released: Insights for ArcGIS 2.3 released! Model data connections and make predictions which allows you to create link maps from Link analysis—Analyze data in Insights | ArcGIS . This will create polylines from 2 point locations (like migration data).
What is the data source? Hosted feature layer in Portal/AGOL or enterprise geodatabase in DBMS such as Oracle, SQL Server, etc.? Insights should automatically pick up the shape field so no need to enable location, and yes polylines are supported. There might be an issue with your spatial reference or geometry storage type.
When you say it could be an issue with your spatial reference or geometry storage type what do you mean?
Do you mean that a certain storage type is not supported? or are you talking about some kind of corruption issue with the storage .
I am having the exact same problem where I am using data from enterprise geodatabase (Oracle) and insight does not pick up the shape field .
The Storage type on the feature class i am trying to use with Insight is as shown ESRI LOB Spatial type. Any suggestion
or help is appreciated.
Sorry, But I have already done with the feature layer (from the registered database). I am now connecting data directly to an enterprise geodatabase in Oracle DBMS. So I'm not sure with a polyline feature class, we need to enable location or not. If needed, how can we enable? If not, what should I do without publishing as a service?. Here is a sample feature class for your reference.
By the way, in case my feature class had more than 100,000 features, can they be fully displayed on a map by adding data directly from a database connection (not a feature layer)? I saw this error after adding the data (about 162,000 records contained):