Latest Contributions by Asrujit_SenGupta

As per the documentation, it should work, however like the link mentions: You do not have to keep your geodatabase and ArcGIS clients at the same release, but it is recommended that you do so. Geodatabases and client software are designed to work together, and if you let one get too many releases away from the other, you risk encountering problems or unexpected behavior. Also, make sure that you are using the supported ODBC driver to connect: SQL Server 2017 Microsoft ODBC Driver 17 for SQL Server Any particular reason why the geodatabase needs to be kept at 10.6.1? ... View more

The answer isn't a straight forward Yes or No. As per Esri documentation (sharing SQL Server as example) : Compatibility between ArcGIS clients and geodatabases in SQL Server When your ArcGIS client and geodatabase versions do not match, your database release must be supported for both the ArcGIS and geodatabase versions. See the ArcGIS requirements for Microsoft SQL Server for the ArcGIS client version you want to use. Also ensure that the database client you install on the ArcGIS client machine is supported for your chosen ArcGIS and SQL Server versions. So as per the below links: ArcGIS 11.2 and ArcGIS Pro 3.2 requirements for Microsoft SQL Server Microsoft SQL Server database requirements for ArcGIS 10.6.x and ArcGIS Pro 2.1 and 2.2 If your 10.6.x geodatabase has MS SQL Server 2017 or MS SQL Server 2016 at the backend, it will be supported, as ArcGIS Pro 3.2 supports those two versions as well. Any higher or lower version of SQL Server isn't supported by both together. ... View more

It seems to be available on the Pearson VUE site.   ... View more

I don't see an error message in your post. Share some more details if possible What error message do you encounter? Which Esri software are you trying to install? Are you observing the issue with a particular Esri software only? ... View more

The Bugs you referred: BUG-000136400 When posting edits from child versions in branch versioning, the following error message is returned, "Error: Insufficient permission"  BUG-000150561 Portal for ArcGIS users with an editor role can edit the default branch version although the access is set to be protected.  BUG-000150561 seems related to you issue, but I don't see much info available on the link. Probably contact Esri Tech Support and get an update on the Bug. ... View more

The screenshot in the link you shared seems to be old. I don't see this issue with time. Using ArcGIS Pro 3.1.3. How times are recorded  How times are recorded When editor tracking is enabled, there are two options for how the date and time will be recorded: UTC or Database time. UTC (coordinated universal time) is the default and recommended setting. UTC is required for datasets registered as branch versioned or for any data that will be shared through services with editor tracking enabled. As a best practice, use UTC when your workflow involves data distributed across time zones. Database time is based on the local time zone in which your database resides and should only be used when your data is confined to the same time zone.   ... View more

Just tried with some sample data and ArcGIS Pro 3.1.3. It does let me create a View based on another view in the FGDB, however there is no data available in the View. Not sure if this is a limitation or Bug. Probably log a case with Tech Support and let them check it out. ... View more

Sorry for the delay in replying back. We have been discussing the upgrades and other factors with relevant teams. We plan to upgrade to 2023.1 if everything goes well and then test the required workflows. Will get back if we encounter any issues during testing.  ... View more

What kind of updates are we looking at? What will be our limitations if we use the 9months old sample file directly,  which seems to work with Version 2022.x. Can you share a recent reference file? We upgraded to Version 2022.x today, but plan to upgrade further once we upgrade the ArcGIS Enterprise environment.  Any other tip is appreciated. ... View more

Always had the understanding that ArcSDE\Enterprise gdb does not have reserved words of its own. These are determined by the host RDBMS on which the geodatabase resides. This document for ArcGIS Pro mentions the same: Define fields in tables Additional field name rules and limitations are as follows: Field names cannot contain reserved words, such as all or result. Consult your database management system (DBMS) documentation for additional reserved words. ... View more

Check the Datareader role in SQL Server. An overview of the db_datareader role  Database-level roles  ... View more