Latest Contributions by Robert_LeClair

Is a Graphics Layer or is it a Feature Class from a geodatabase or shapefile in the Contents Pane? ... View more

One thing I would try is close ArcGIS Pro and reload your project file.  When you share the Web Map to your Portal, I'd recommend changing the Map View Coordinate System to WGS 1084 Web Mercator (auxiliary sphere) to publish the web map.  Does the issue persist? Please advise. webmercator.JPG ... View more

Marcel - you can use the Upgrade Dataset GP tool to upgrade your ArcMap annotation to be editable in ArcGIS Pro.  BUT keep in mind once you upgrade your annotation feature class to be read/write in ArcGIS Pro, it will no longer be usable in ArcMap.  You read  more about this topic here. ... View more

If you have the Esri Data Interoperability Extension, you can import PostGIS, PostGIS Raster and PostgreSQL data into your GDB's. ... View more

Hi Rafael - interesting!  What I would recommend is save the *.mxd to a new *.mxd (and delete the old one) to see if there was an issue with the *.mxd itself.  Worth a try. ... View more

I'm thinking the reason you're seeing this result is the For Iterator is not connected to your Combine tool at all and is floating in space.  Secondly, I "think" the reason it's only giving two outputs (EACVCal16 and EAVVVal16) is alphabetically they're the first two and then it stops.  Just a guess.  I'd recommend reading this link to connect the For Iterator to the rest of your model. ... View more

Your call.  If you feel this behavior is needed for workflow, then you can add it certainly.  As you know, I'm not on the ArcGIS Pro Dev Team rather Training Services so have little pull in what gets incorporated into the ArcGIS Pro application.  Like I said for eGDB's, one can do an incremental recovery to restore deleted RC's.  Not as easy with fGDB's. ... View more

Scott - do you have any database views created in your eGDB?  There's some chatter about DBV causing slowness of the Analyze Datasets GP tool.  The analyst and the customer used SDEINTERCEPT to diagnose the issue.  3 DBV's were determined to be processing very slowly.  The user deleted the database views, ran the Analyze Dataset and recreated the DBV's after the tool completed.  The customer saw a marked increase in performance. ... View more

As strange as this sounds, I found something on the internals similar to your question here where disabling the background geoprocessing option in ArcMap fixed another customer's issue with the error message.  Worth a try! ... View more

Hmmmm...might be time for a call to Esri Support Services.  Their number is +1-888-377-4575 ... View more

I discovered a Technical Support article that might address this issue.  Hope this helps! ... View more

When you click "Set Data Source" this will open another window, in the new window try to go to Project->Databases and see if you can set it there via the "Make Default" eGDB.   ... View more

Based upon my testing of deleting the RC and building a new RC with the exact parameters, it seems unlikely unless I'm missing something on the inner workings of the GDB and ArcGIS Pro.  If this is an eGDB, then full and incremental backups of your database would be the best way to recover. ... View more

Pete - this is odd behavior certainly.  Try this, double check your *.sde connection file in the Catalog Pane to verify if sees the eGDB.  Then in the Catalog Pane, under Databases right click the *.sde connection and click "Make Default."  Next, go to "Change data source" in the Layer Properties and under Project->Databases, click the Default Geodatabase, your *.sde connection and reset the data source.  Does the same behavior persist? ... View more