Latest Contributions by MattSimmons

‎09-30-2013

I found that this is now supported in Flex Viewer 3.4. You need to first set up the relationship class in the database. Second, in the FlexViewer Application Builder, the map service needs to be loaded as a dynamic service as opposed to being loaded as a feature layer. Third, in the pop up for the layer, the "show related records" needs to be set to "On." So when a point is added it's using the edit widget the point is added using the feature layer, but in the popup and/or attribute widget window it's using the dynamic map service. Furthermore, you can use the Attribute Widget to add a related record to a record.

‎09-04-2013

Hi- I have a relationship class set up between two SDE tables. It's a on-to-many, composite relationship. In other words, a single point on the map can have many sampling events associated with it. Those events are linked to the same point using primary key/foreign key relationship. Is there a way in the Flex Viewer that I can handle adding a single point, and then adding more than one event associated to this point? I.e in the Edit widget, when you add a point it adds a single record to the table. Well, on that same Edit widget popup window I want to be able to have an 'Add' button that allows the user to add multiple events that are associated to that one location. Thoughts?

‎07-31-2013

Does your .csv file have coordinates already in it? Your map will need to be in a map projection before you can get coordinates. Start herhttp://resources.arcgis.com/en/help/main/10.1/index.html#//006600000010000000

‎04-10-2013

From the sounds of it, you have a geocoding service already, which you probably have in ArcSDE. You need to publish this to ArcGIS Server first, and then you can configure your web map to consume the geocoding service. Try here: http://resources.arcgis.com/en/help/main/10.1/index.html#//002500000036000000

‎04-09-2013

Maybe a more fundamental understanding of what compressing the database does, when done in ArcCatalog, would help your situation. In your editing workflow you either use, or do not use, versioned editing. Here's a link to understanding versioning at 9.3. http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=understanding%20versioning Assuming you now understand versioning, when you register a feature class as versioned, the adds and deletes tables are created in the database. Adds and deletes tables don't exist if your feature class is not registered as versioned. When edits are made using versioning, the deltas are stored in these adds and deletes tables. Further on in the versioned editing process you will reconcile and post. Reconciling and posting means ArcGIS is "comparing" the edits of the database being edited to its parent database to see if any conflicts exist. Once reconciled, the edits are "posted" (or, committed, in a sense, but not actually committed...read on) to the default database. ArcGIS clients will now see the changes. However, the deltas are still in the adds and deletes tables, but the ArcGIS clients are referencing those tables, so data changes are visualized. If you are using a third-party software (i.e. AutoCAD) to consume your gis data, that software probably won't be referencing the adds and deletes tables and thus the data changes won't be reflected. That's one time that compressing the database comes in. Compressing the database does a number of things. The first of which is that it "trims" the lineage of changes in the data. It trims the state tree which, among other things, saves on space. Another thing that compressing does (albeit a full compress) is that it moves the deltas from the adds and deletes tables to the base tables of the database, ensuring that those third-party programs are seeing all of the data changes. You can compress through ArcCatalog as little or as much as you want, and ArcGIS will do as good of a job as it can in compressing. A full compress will not occur until all versions are reconciled, posted, and deleted; and there are no database replicas referencing the adds and deletes tables. A full compress is achieved when the state_id of SDE.DEFAULT equals 0. A successful compress does not always equal a full compress. A successful compress just means that ArcGIS did as good a job as it could trimming the state tree, considering versions may still exist and replicas have not been synchronized. Read up on database replication here: http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=Scenarios_using_distributed_data As Vince stated, a full compress is not always necessary. To read up on compressing a database at version 9.3, read this: http://webhelp.esri.com/ArcGISdesktop/9.3/index.cfm?TopicName=Compressing_an_ArcSDE_geodatabase_licensed_under_ArcGIS_Server_Enterprise Hope this helps~

‎03-25-2013

Well, whether or not this is a bug I'm not sure, but thanks for replying. I found a workaround. I went to github and pulled up the Search widget xml from one that works and just copied the contents of the xml to mine. All I had to do then, was change the URL to point to my own web service and change the searchable fields and it's working. https://github.com/Esri/arcgis-viewer-flex/blob/develop/src/widgets/Search/SearchWidget_Louisville.xml

‎03-20-2013

I actually just did this about a week ago and it went very smoothly. When you change the machine name in the control panel, your ArcGIS Server instance will automatically update. All of your map services residing on the server will update, as well. There may be a bit of lag time in your DNS server, but that should update automatically, too. Once you change names on the server, open a command window from a different machine and ping the new server name and you should get a reply. If you do not, you may need to use the command ipconfig /flushdns on the non-server machine and then ping it again. You may need your network administrator to help if you run into issues (i.e. remove the server from your domain and then rejoin the domain, which will force the DNS server to recognize the new server name). As for ArcGIS Server, everything should be automatic. On the client side, if you have any applications that point to map services or mxds that point to the old name, you'll need to update those to the new name. Hope this helps~

‎03-20-2013

I have Flex Viewer 3.0 installed on a server running 10.1. I added a web service to a web app in this 3.0 Flex Viewer. Then I added the search widget, and I can select features using the geometry selection tools just fine. The selected features and attributes show up in the results. I then install 3.1, and upgrade this application. The search tool no longer works. There are no changes to the service or anything else I can imagine. Furthermore, as a test, I uninstalled the Flex Viewer, deleted the flexviewers folder completely from inetpub/wwroot. Then I freshly installed Flex Viewer 3.0 and re-set up the application same as before, and the search by geometry works. Then I install 3.1 and again, the search no longer works. It just doesn't select anything. A bug? Also, in both cases (3.0 and 3.1) the "Select by Attribute" icon doesn't exist in my Search widget. Everywhere in the forums and Help, I see screenshots of it (Select Features and Select Attributes) but I don't see it in my installation. Anybody else seen this?

‎03-11-2013

More and more GIS Administrators seem to be using non-ESRI applications to access web services via ArcSDE. In order to use non-ESRI apps a full database compression to state_ID=0 must occur. At version 10 and 10.1, in order to get a full compress, it is sometimes necessary to synchronize changes not only from child two-way to parent, but also from parent (SDE.DEFAULT) to child two-way. This step is necessary to clean up the SDE.VERSIONS table which allows for a full compress to state_ID=0. I spent weeks on this problem, in addition to ESRI Technical Support. THe documentation for this step is only referenced in the ESRI white paper on compression, and only as a special side-note in that documentation. It seems that everywhere else I searched, in addition to the forums, the widely accepted and documented steps to achieve full compress was to 1.) reconcile/post 2.) delete versions 3.) synchronize changes for all replicas from child to parent 4.) compress database, check state_ID. However, at version 10 and 10.1 the steps are actually: 1.) reconcile/post 2.) delete versions 3.) synchronize changes for all replicas from child to parent 4.) synchronize changes from parent back to each child two-way replica (even if there are no changes) 5.) compress database, check state_ID.

‎02-06-2013

It may be that since you're trying to publish a feature dataset that is provided by ESRI into a web feature service, you don't have a local enterprise database with that feature dataset. It would be inefficient for ArcGIS Server to dynamically retrieve the dataset from the ESRI server as updates may be occurring readily, or internet connectivity may be severed; so it needs an on-site database to refer to instead. ESRI designed server 10.1 with this in mind. You would just want to periodically update the on-site feature dataset by refreshing your mxd in ArcMap from time to time, and republishing as a service. It would then recopy the updated feature dataset to the local server.

‎01-17-2013

One more thing: if you are adding fields to the database, you cannot do this to the child replica. This is like a schema change and must occur at the parent (SDE.DEFAULT) level. You must add fields to the parent database prior to any replication or synchronization. This is because once a field is added to the parent database, it will no longer synchronize with the child replicas because the database schemas are no longer identical.

‎01-17-2013

In order to use replication, your "parent" database would be ArcSDE and your child replicas would likely be using SQL Server Express. In this setup, you would create an empty personal gdb on the SQL server via ArcCatalog. (In Database Servers, establish the connection to your SQL Server instance, then right click, and Create New Geodatabase.) Then, you would use the "Create Replica" tool in the ArcGIS toolbox. Using this tool, you first select the feature classes from ArcSDE parent database that you want to replicate to your child database(s), and then select the child database to replicate to. This populates the child replica with the feature classes you selected. Synchronization occurs only after you have made edits to your child replicas. Once you have performed edits to the replica database, you would use "Synchronize changes" (ArcCatalog, rt click the replica -> Distributed Geodatabase -> Synchronize Changes). This pushes only the edits to the parent ArcSDE database. From your description it read as though you understood synchronization backwards.

‎01-16-2013

I have an existing ArcSDE 10.1 database on Oracle 11g, being administered via ArcGIS 10.0 and 10.1. This database is production and is working fine. I then set up a test database to mirror the production database for testing purposes. Used the following procedures: 1.) My DBA created empty tablespace 2.) My DBA created SDE and ARCDATA users, and assigned permissions 3.) My DBA assigned permissions to the tablespace 4.) I used 10.1 GP tool "Enable Enterprise Geodatabase" to set up system tables and install stored procedures. Succeeded. 5.) I copied feature datasets and feature classes from production database to this new test database. Succeeded. 6.) I registered the appropriate feature dataset as versioned (without move edits to base because I'm using replication). Succeeded. 7.) I created new SQL Server Express geodatabase on SQL server in order to replicate. Success. 8.) I created a child replica. Success. 9.) I tested to see if I could still connect to the database, which I could. 10.) I made a test edit to a feature class on the replica using ArcGIS. 11.) I saved the edit. 12.) I synchronized changes successfully. 13.) I ran sdeversion -o describe to check to make sure the state_ID changed from 0 to some other number, which it did. 14.) I disconnected from the database in ArcCatalog to check and see if I could reconnect (THIS IS THE PROBLEM!) 15.) At this point, whenever I attempt to reconnect to ArcSDE using ArcCatalog and it crashes giving the generic ESRI crashed message. SDE logs indicate an exit status of 8, which is a lost client. I have tried these exact steps three separate times, with three brand new instances and each time, at the moment I have a replica that has changes, I can no longer connect to ArcSDE and ArcGIS/Catalog crashes. The following are details of each of the three attempts. The first time: My DBA exported my production database and imported it to test, using ESRI's recommended steps. That export/import contained replicas in the database, with edits. Thus, connections using Desktop crashed the software. The second time: I started with a fresh tablespace, and followed steps 1-15 above, because I though exporting/importing with replicas and edits might be causing corruption and wanted a fresh install. However, same result - once I got everything set up and created a new replica and made an edit using the above steps, ArcGIS crashed when trying to connect. Third time: Suspecting it had to do with replicas and edits, I again followed steps 1-15 above, focusing in on editing the replica to confirm this was where the problem lies. ArcGIS Desktop/Catalog 10 as well as 10.1 both crash upon trying to connect. For the longest time permissions issues were preventing me from copying the data, which to date, have ONLY BEEN RESOLVED by giving the ARCDATA user FULL dba privileges which SHOULD NOT BE, even after following the ESRI recommendations for user privileges. Now that the user has full dba privileges I can actually administer the database but I now have this crashing problem.

‎01-14-2013

Are you sure the data store(s) are registered with ArcGIS Server? I ran into a similar issue where my map service wasn't updating dynamically with edits to feature classes I was making. Turned out that when I initially published the service to Server, the data store(s) weren't registered with Server so it was copying all of the feature classes, images and mxd to a local directory on the server itself. In order to clear that local copy, I had to delete the service, register the data store locations with Server and republish. Once Server knew the communication link between the service and data, the map service became dynamic.

‎01-10-2013

It's probably nothing you are doing - the issue is in ESRI's map export tool. It appears this is the first true map export/print functionality they've tried to deliver with a server release "out of the box" and in the case of map legends in pdf's it's coming up short. We experienced this same issue with legends in pdf's in August 2012, while running server 10.1 and designing a web application using the Silverlight API v 3.0. The developer had several conversations with ESRI support and they provided a workaround that is a bandaid fix... which eludes me for now... I don't know if they plan on improving this in the next server release of API release, but it would be worth contacting someone on the Server or API team at ESRI to get the latest. For us, too, the other formats looked fine but the most common document is a pdf so we needed that legend to look right.

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by MattSimmons

Re: Editor widget to add records in a relationship class?

Editor widget to add records in a relationship class?

Re: Latitude/Longitude

Re: How do I create a ArcGIS Server geocode service tool using my own GeoCoder?

Re: compress sde database

Re: Bug in Search Widget for 3.1 or just me?

Re: Changing the name of the server

Bug in Search Widget for 3.1 or just me?

Documentation for ArcSDE database compression needs to include synchronization in both directions more prominently

Re: Registering data source with server problems

Re: getting data into replica gdb from parent gdb

Re: getting data into replica gdb from parent gdb

ArcGIS crashes when connecting to SDE after edits to replica are made

Re: Can't get map service to show dynamically updated raster data

Re: Printing Tools pdf legend issue

Re: Registering ArcSDE database with ArcGIS Server...

Re: compress sde database

Documentation for ArcSDE database compression need...