Latest Contributions by MelissaJarman

Jimmy - I would recommend you contact support once you get a consistently reproducible case for any type of error that is preventing you from saving. You should be able to work in a user version and validate your edits. There are many conditions in play when performing edits in a user version and working with dirty area management with a UN. While you can get general pointers here, our support group would be able to take a closer look to give you guidance.  ... View more

Sorry I don't have a specific solution to recommend. XML workspace documents do allow schema only option, so this is a reasonable workflow for you to attempt. To troubleshoot this I would try the process of elimination to isolate the culprit that is causing the import to fail. Perhaps exclude the views in your first pass and go from there to see if the cause can be determined.  ... View more

I hadn't thought about doing it that way with the Select By Attribute tool. It looks like this equivalency idea you linked is under consideration. I also found out that you can make a selection in the map view and then use the Attributes pane > Selection tab. When you initially open the Attributes pane it will give a warning about the violation of the attribute domain.  MelissaJarman_0-1637780962883.png     From here you can further use the context menu to change the selection to ONLY include the invalid features.   Snag_879b1509.png  https://pro.arcgis.com/en/pro-app/latest/help/editing/edit-feature-attributes.htm#ESRI_SECTION1_8F13A8C397F349C9BF97D3DF2353E69F ... View more

There are a lot of things that could be going on depending on the amount of data that is included in the XML workspace document from your EGDB. Let us know how many datasets and what types of datasets are included. Are you using any special datsets other than tables and standard feature classes? I noticed it looks like you're doing schema only, but have you tried other data transfer methods such as copy/paste since you are going to FGDB?  Lastly, have you attempted this export and import to XML from the latest version of ArcGIS Pro? ... View more

I can understand why it would be confusing when only 'some' relationship classes have this context menu to add to map. Only certain types of relationship classes will have the right-click context menu to add to a map. Many-to-many relationship classes have an intermediate table and will have the context menu to add to the map - they'll show up as tables. These are also referred to as attributed relationship classes. Here is some supporting documentation for preparing data that mentions attributed relationship classes needing to be present in the map document. Prepare data to publish a feature service Feature services allow queries on related data, but only if the relationship is defined through a geodatabase relationship class. If a published map document has a layer and table related through a geodatabase relationship class, the feature service allows queries on the layer to return objects from the related table. To support queries that return related objects, you must include the table and layer involved in the relationship class in the published map document. If either the origin or destination layer or table is not included in the map document, the feature service ignores the relationship. Note: For attributed relationship classes, include the relationship class table in the map document. ... View more

Attribute rules could work for this to run check on your existing data - validation rules. Data Reviewer also has domain checks for this.   ... View more

What specifically are you trying to do that is being blocked for datasets stored in a SQL Server DBO schema geodatabase? Are you trying to register as branch versioned?   ... View more

Here is the help page for this error: https://pro.arcgis.com/en/pro-app/latest/tool-reference/tool-errors-and-warnings/001001-010000/tool-errors-and-warnings-01976-02000-001987.htm Attribute domains that are assigned to the asset type field cannot be modified after the network topology is initially enabled. This includes attempting to modify the domain assignment for the asset type field or to make changes to the code or description values for existing domains assigned to asset type fields. See Utility network management tasks for common configuration tasks and their required network topology state.   ... View more

This is a late response, but just incase someone else has this same question.  When you are using operations that first require a startReading or startEditing operation to be completed first, the sessionID must match. If performing these operations via the ArcGIS Pro client, the pro client will generate the sessionID and ensure that this same sessionID is used for all REST calls.  When you are using the REST endpoint yourself to issue these calls (through your application), it is your responsibility to generate your own sessionID. You can use an online GUID generator, python module, etc for this GUID. This is dependent on where you are executing these REST calls from. ... View more

Regardless of how you create associations you'll have to have your network features configured with the correct rules to allow for associations + any association roles also need to get set (depending on the association type used). Then you have to decide how you will create your associations. There are many options available for creating associations between network features:  Manually create using the Modify Associations pane Create associations using custom attribute rules that use the edit keyword - Attribute rule dictionary keywords Preset templates - If you want specific types of features to be created with an association between them, it sounds like you could explore creating preset templates. https://pro.arcgis.com/en/pro-app/latest/help/editing/utility-network-reference-for-editing.htm https://pro.arcgis.com/en/pro-app/latest/help/editing/create-a-preset-template.htm   ... View more

Please let us know if the Angle Directed layout does not work to your needs.  ... View more

The development team has been working on the ability to display associations in the Javascript API. The upcoming release of the Javascript API (4.20) is planning on having support for displaying connectivity and attachment associations. This uses the REST API SynthesizeAssocaitionGeometries operation. Containment associations are a bit different as they require the use of display filters to toggled on/off. I am not sure if the actual display filter part is supported in the Javascript API or not. In the ArcGIS Pro environment content features are displayed by default unless the map is configured with display filters. You could use definition queries on the layers with containment associations based on the associationstatus attribute.    Containment associations Control associations visibility Association status attribute What is the planned release schedule for future 4.x releases? ... View more