Latest Contributions by AyanPalit

@RoseAmy Thanks for your good review on Pro 3.5 - there are many exciting features. Sorry for the issue on BUG-000177183. Did you try the suggested workaround: Use the Query Expression, that you would use for Select by Attributes tool in the Definition Query and apply the filter to the SQL Server layer. select all records from the attribute table I realize this is more steps but, better option than downgrading ArcGIS Pro on account of this BUG. ... View more

@CoronaGis Interesting question - thanks for posting. Is the data 3D? Utility Network features are 3D aware, so you can model the riser pipe vertically as in screenshot below. AyanPalit_0-1753110894668.png Here's a video showing this interesting concept:  3D Networks and Vertical Assets ... View more

@COSPNWGuy Thanks for the details.  Looks like DOT users are giving kudos to your ideas. Encourage others to adding your use case in the comments. ... View more

@Alexander_Couch  I assume the LRS dataset is branch-versioned. There are specific requirements around that as well.  Here are some references : When the Version Management capability is enabled, the following requirements exist: All datasets in the map you're publishing must be branch versioned. You cannot publish traditional and branch versioned datasets in the web feature layer. You must own the data you're publishing. That means the credentials you use in the database connection that accesses the data must be those of the data owner. https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/publish-branch-versioned-data.htm  https://pro.arcgis.com/en/pro-app/latest/help/production/roads-highways/share-as-web-layers.htm    ... View more

@COSPNWGuy please post your request as a new idea following Submission Guidelines It will help to understand the use case and the benefits of the requested enhancement.  ... View more

@Alexander_Couch What are the versions of ArcGIS Enterprise and Pro? Recommend reviewing the 'underlying dbms error ora-03114' Looks like, the portal credentials used for publishing, is failing to have full access to the data layers in the Oracle RDBMS.   ... View more

@AYUSHYADAV Was the successful connection with different version of Pro?  So it worked before and the only known change is ArcGIS Pro v3.5? ... View more

@matchjohn The modelling can be simplified : does ships have to be related to ports? what is the use case? what will you gain from this? perhaps eliminate this relationship; port at which ship is docked can be a domain list. one to many between the ships and activities makes sense. Great suggestions  from @MobiusSnake . agree that M:M relationship maintenance has some overhead.   ... View more

@CaseyLott1 Assuming usage of the Calculate Geometry Attributes with Area (geodesic) , Area Unit (Hectares OR International Acres). Since you specify Pro version 3.5.1 - have you run this same calculation in a previous version and results were in line with your expectations? ... View more

@ZacharyUhlmann1 So project was updated in Pro 3.2 and then being opened in Pro 3.3.4. This is fully supported and I would not expect this due to version incompatibility. Perhaps, there is a broken data source. Possible that second user doesn't have all the access that first user had and hence it stalls. Suggest looking at the layer list and using tools like Diagnostic Monitor to identify the issue. You can also log an Esri Technical Support ticket where an analyst can review the aprx file. ... View more

@LRoberts_RDM Yeah, as stated Prune Branch History is new at Pro 3.5. Looks like the error is specific to Water_TN - Check the layer properties > Manage. Is it branch versioned correctly? Here are some tips: The dataset must be registered as branch versioned. The tool can only be run by the data owner. An exclusive schema lock is required to run the tool. Services referencing the input data will need to be stopped using ArcGIS Server Manager. Conduct a test run—Use the tool with the Report Only option enabled. This method will not prune any data; it simply provides a report in the Output Log File result on the number of archived records that could be pruned. Log file review—After running the tool, review the Output Log File result created to see how many archive records are eligible for pruning. Monitor log files for any warnings or errors related to the pruning process and take appropriate action. Timing of running the tool—To reduce system impact, it's best to run the tool during off-peak hours, on weekends, or at times when the feature service referencing the branch-versioned dataset can be stopped. Reference: Prune branch history Please share your findings with the community. ... View more

@AlexandreMatveev shared some tips on your original post. ... View more