Hello,
I have been working on a sewer model from within the ArcMap interface, and I'm running into a consistent bug with respect to my symbology displaying correctly. A lot of the feature symbology I am using is dependent on the "Is Active" field. However, each time I re-open the sewer model from within the ArcMap mxd, the "Is Active" field is dropped from the attributes of my features, and therefore the symbology is messed up. I have found a small workaround where I can remove the "Is Active" field and re-add it in the flex tables, and it will then transfer to the attribute table and display correctly, but I have to do this within each flex table for multiple features (gravity sewer, force main, manholes, pressure junctions, etc). Is there something I'm missing here, or is it really just a bug between the SewerGEMS and ArcMap interface?
Thanks!
Hello Connor,
It seems that what you are experiencing is explained in the following article.
How do I use and display Active Topology for elements on the ArcGIS/ArcMap Platform?
Please let us know if one of the two options in that article help with controlling the active topology in SewerGEMS for ArcMap.
Regards,
Craig Calvin
Bentley Technical Support
Hi Craig, thank you for the reply. This article did have a solution to my issue. Instead of referencing the "Is Active" attribute through the ArcMap symbology editor, I have since turned on SewerGEMS rendering and am defining the symbology through Tools > Layer Symbology. This way I can control how all inactive elements are shown rather than trying to control Active/Inactive elements through the symbology tab under the properties of a feature class. This is a much more streamlined approach, and I will be using this for all of my symbology definitions from here out! I hope this helps someone with the same issue of handling inactive elements. Thanks again.
Hi Connor,
I agree that the built-in "Renderer" option is the best approach to handling the active topology situation in the SewerGEMS for ArcMap platform.
However, I was concerned to hear that your attribute was being dropped after reopening the project, as that is something that you may need to use for other purposes such as annotating a specific field in your hydraulic model. So, I did some testing on that using a sample model in the latest version of SewerGEMS (10.01.00.70) in ArcMap 10.4.1 but could not reproduce the problem.
I suspect the cause may be due to your workflow/process. So, to start with some background:
With that said, is it possible that the hydraulic model was not re-opened when you reopened the ArcMap project? (MXD file) Or, are you reopening the model from the hydraulic model manager yet the attribute table still does not list the previous attribute that you had added to the GeoTable?
If you find that the field you had added to the GeoTable is no longer added to the GeoTable, this may indicate that the file that stored the configuration of the GeoTable possibly could not be written to. In this case, try reopening SewerGEMS for ArcMap, or ArcMap itself, by right clicking on the shortcut and choosing "Run as Administrator". This will ensure you have read/right permissions in the session.
If this does not help and you would like to pursue the sync issue with the attribute table, please provide further information and screenshots if possible to help us troubleshoot.
Jesse DringoliTechnical Support Manager, OpenFlowsBentley Communities Site AdministratorBentley Systems, Inc.
Hi Jesse, thank you for the reply. Since posting this, I've had a couple of developments. I do believe there was an issue with the connectivity of my mxd file and my model mdb file. This morning I reopened my mxd and received the following Microsoft .NET warning: "Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue. Object reference not set to an instance of an object." It appeared I could not open my model, and that somehow the link was broken. I ended up detaching the model file altogether and re-attaching it through a new .mdb file. Somehow the link was corrupted, and I'm not exactly sure why. This could have been the source of my issues with the attribute fields not matching my geotables. I also noticed that under Tools > Database Utilities, there is an option to Synchronize Drawing. Would that work to update the attribute tables correctly? Also, are there any measures I should take so that the link isn't broken between my mxd and model again? Another piece of information is that I am running the 10.00.00.40 version of SewerGEMS within version 10.5 of ArcMap. and I saw on the compatibility table that I should need a newer version of SewerGEMS. Would that be a potential source of error as well? Thanks!
I am not sure why you encountered that error when trying to open your model, but if you need to re-add the model and recreate the geodatabase in order to access the model again, that could indeed break the connection between the geotable and ArcMap. This would simply require you to re-add the appropriate field to the geotable, which should then automatically add that field to the geodatabase, making it available to use symbology on. See the link in my previous reply for an alternative to applying color coding.
What were the exact steps taken to reopen the project? (Open MXD, then open the model from the hydraulic model manager?) Do you recall what may have changed between when the project worked and when the error started occurring? Is it possible that one or both programs were upgraded or that any of the involved files (MXD, MDB, STSW, SQLITE) could have been moved? Or, was this the first time you tried reopening the project after saving it? Are you able to re-open it without error now?
Regarding the synchronize drawing command - this should not be necessary to keep the geotable in sync with the geodatabase, but it cannot hurt to try in the event that something appears to be out of sync. First though, confirm whether or not the field in question is present in the geotable. Next, open the attribute table for the respective element type's layer in the table of content (and check to make sure there aren't any duplicate layers) and check if the respective field is present. If so, save the project, close ArcMap, then reopen ArcMap, reopen the project and reopen the hydraulic model. Then, check the above things again.
If the attribute is no longer present in the Geotable, then the "synchronize drawing" command will not bring it back and you will need to re-add it to the Geotable to synchronize things again (to be able to use symbology with the respective field). If that is indeed the case, please try the "run as admin" suggestion, as this would indicate that somehow the change to the geotable was not saving (this is saved to a file called AttributeFlextables.xml under C:\Users\<Username>\AppData\Local\Bentley\SewerGEMS\10).
If the attribute is still present in the geotable but not in the attribute table of the respective element in the ArcMap Table of Contents, check to make sure that there isn't an exclamation point next to that layer, which would indicate a problem with the way that the information was populated in the ArcMap session. If the layer seems to be OK, try the Synchronize Drawing command.
Regarding ArcMap 10.5, yes, official support was added in version 10.00.00.45 as mentioned in Platform Compatibility. I would indeed recommend upgrading; the latest version is 10.01.0.70. If I recall correctly, the version you currently have will integrate with ArcMap 10.5, but we added more "official" support for it in the 10.00.00.45 release. Although I suspect something else may be going on (please check everything above), it is possible that the version may be related to any problems you're experiencing.
Of course, you always have the option to do your modeling work in the Standalone environment, then if you have the need to do something in the GIS environment, you can add the same model there. If you are using the ArcMap environment for something specific, let us know and we might be able to help you accomplish it in the Standalone environment.
Hi Jesse, I just successfully saved the model, closed ArcMap, re-opened ArcMap, then opened the hydraulic model through the hydraulic model manager. I am still noticing that some fields are not showing up in the attributes table that are in the geotable (I've attached a screenshot to this message). You can see the model has successfully opened and loaded, but the side by side comparison of the attributes and geotable is different. My theory is that both of the fields missing are binary (True/False), and for some reason GIS is having trouble reading these when the file is initially loaded. If I remove and re-add the columns, they will then appear in the attribute table. Quite the strange issue. I also don't have the authorization to run progams as admin due to how our network is set up.