Latest Contributions by AkshayHarshe

@CalebK  Only shared reports can be scheduled to refresh and not the workbooks. You can find if you have scheduled reports by going to the reports tab on the home page and filtering on the scheduled page. Failed scheduled reports can leave behind a blank workbook as it creates a temp workbook to store new analysis until the update is successful. If you are actively seeing blank workbooks appear in your workbook tab, you want to check the active scheduled reports (not paused). I recommend you open those reports and check if they have any errors e.g dataset no longer available or cards in an error state etc.  Then check the reports that were scheduled but are now paused in the same way. Also, see if you have any past updates by clicking the schedule icon on the card and switching to past updates: (Note: This information is retained for a certain # of days) Let me know what you find, as I can't think of anything else that might be causing this. I remember working on the issue you are referring to and yes, the issue is patched and should not affect this one. You should not be able to edit some other user's workbooks. ... View more

@CalebK Sorry to see you are facing this issue. Honestly, I haven't seen that before, that too in ArcGIS Online. unless some of our tests fail. I will take a look and investigate if there are any issues.  By any chance do you remember when this started happening? (maybe look at the date created of the first one). Also, Are there any scheduled reports that are failing to refresh? ... View more

In this case, you do not want to check the "Repeat Identical Features" button in step one. (Enable Location by LAT & LONG on Fuel Point ID (Sheet2.Table1 in give n dataset)) ... View more

@CCGIS Can you clarify your workflow? Are you using the same workflow as @KateMaclachlan has explained in her comment on a reference table with some formatting?   Unfortunately, We can't export the table as Excel at this point. ... View more

@BarbaraSj After looking at the data I am puzzled by your workflow. I think you are going wrong here:   I enable locations for Fueling points (A). I then create a relationship between the two data sets where fueling point ID( is unique on dataset fueling point (A)).  What was the field from the customer data used in the join? From the relationship created, I then enable location for 2 columns:1st time fuel point ID and Last time fuel point ID. When trying to create link maps i get the error the layer used to enable location or create relationship contained multiple features with identical names try using a layer with unique identifiers The customer data doesn't contain latitudes and longitudes for the First and Last Fuel IDs, for you to enable location so I am not sure how this was done. I was able to achieve results with the following workflow Enable Location by LAT & LONG on Fuel Point ID (Sheet2.Table1 in give n dataset)\ On Customer Data.Table1 Enable location -->? Geography twice usingFirst and las fuel Point ID     Use both the Geographies to create a Link map   I am hoping this is what you need. If not, I recommend you prepare Lat/Long fields for First and Last Fueling points instead of IDs in the Customer dataset, then enable location XY on both. ... View more

Sorry, I missed your follow-up comment. You can choose to use "Zoom tools" and Zoom to select after selecting the table. If you wish to do this dynamically, turn on the Cross filters on the map card. ... View more

@ChelseaRozek I believe we missed responding to this question. Are you still facing this issue? It sounds like something with the join.  If you still have this issue please send a sample data if possible and I can take a look.  ... View more

Hi @Eric_Castonguay, Thanks for formally submitting this as an idea. Yes, this has been asked several times by different customers and I will take this to the management to see if we can prioritize this.  ... View more

@BarbaraSj  Thanks for the data, I will look into this and get back to you. (hopefully within a few days or a week). I am optimistic that it is a cardinality issue and we cannot query the entities.  Can you try the steps in point 2 while ensuring that the Fueling Stations A are unique? ... View more

@AndreasDarr One other thing I will have you check is to run the `describeDatastore.bat` file under your <installation directory>\Datastore\tools\ and see if you have any errors. ... View more

Hi @BarbaraSj Thanks for your question. It is a bit hard to mentally visualize data but I think it is complaining because there are multiple joins happening resulting in an output dataset with many-to-many joins where  no single entity that contains all fields that can be queried. In these cases we are not able to flatten the table Enabling location on Fueling points A Join between Fuelling points A and Customer data then Enable location on the First and Last Fuel point IDs (x2) I have a few questions. Does Fueling points(A) geometry have the same cardinality as Point ID? Are First and Last Fueling Point geometries derived from Fueling Points A? Are the First and last Fueling points fields inside the Customer Data (B) table? I will have you try a few things When Enabling location on Fueling points (A) (if they are unique) then check the "Repeat Identical Features" while enabling the location and see if that works.  If the answer to my questions 1,2 & 3 above is "Yes" then instead of joining customer data to Fueling points (A) and enabling location on First & Last Fuelling points can you try the following: Enable Location on Fuelling Points (A) use Repeat Identical features (Like mentioned in 1) Enable Location twice (First & Last Fuelling points) by Geography using Point ID & Fuelling Points (A) as a geometry. Use this dataset to create a Link map. If this doesn't work please send me a sample dataset(s) to try and I can see if there is any issue here. ... View more

@AndreasDarr You should install it on your GIS/hosting server(s). before anything, I suggest you clear cache and browsing data and/or try it in Incognito mode. I am not entirely sure what is going on, you could try upgrading to 2023.3 and see if that fixes something.  Previously, I had success solving this error by rebooting my portal and server machines. You can try that if that is an option for you. If nothing fixes it, I recommend you reach out to support and have someone take a look. More likely it will be something to do with the DS.  ... View more

Hi @AndreasDarr , A few questions: 1. Can you create any content in the portal? e.g. use "Add Item" and create a new feature layer using an SD file. If this is not working, you might have a problem with the server or data store. 2. If you have a multi-machine deployment, install the server part of insights on all the server machines. Also, for 11.1 you can use 2023.3. ... View more