POST
|
The TableControl and related classes are a great addition to the SDK! However, I'm seeing behaviour whereby the SqlQuery applied to a TableControlContent object ends up getting applied to the MapMember (whether it be a StandaloneTable or a Feature Class). Is this expected behaviour? I would expect the TableControl to display a custom filter without affecting the built-in attribute table's records. It is as though a DefinitionQuery is getting set somewhere behind the scenes. After this, it seems the filter is cached on the MapMember, and subsequent queries in the Addin continually return the same results. Even after closing the the "Road Names Pane", which is a MapImpersonation pane, upon opening a new Pane, the same results are returned despite a change in the SqlQuery. Is this a bug? If so, is there a workaround you can suggest to get around this? I am in the process of refactoring an Addin to replace a custom WPF table with the TableControl and would prefer not to back-out these changes. Thanks, Charlie
... View more
02-11-2019
10:36 AM
|
1
|
1
|
683
|
POST
|
What type of functionality is in your C# code that you would like to call from Python? A more typical code pattern would be to have C# code call Python using the Geoprocessing API as demonstrated in this sample: Github Esri/arcgis-pro-sdk-community-samples: CallScriptFromNet
... View more
09-07-2018
11:22 AM
|
1
|
1
|
3084
|
POST
|
Running the "Create Database Sequence" tool from the Geoprocessing panel works fine. After successfully creating a sequence on the panel, I then delete it using the "Delete Database Sequence" tool on the Geoprocessing panel. Then, from the "History" tab on the Catalog panel, I choose "Send to Python Window" from the right-click context menu of the "Create Database Sequence" history item. After executing the code sent to the Python window I get the following info/error message: arcpy.management.CreateDatabaseSequence(r"C:\Users\gormanch\Documents\Projects\MigrationFromMAP\EGISED6.GISADM.sde", "MY_TEST_SEQ", 20000000, None) Traceback (most recent call last): File "<string>", line 1, in <module> File "c:\program files\arcgis\pro\Resources\arcpy\arcpy\management.py", line 5088, in CreateDatabaseSequence raise e File "c:\program files\arcgis\pro\Resources\arcpy\arcpy\management.py", line 5085, in CreateDatabaseSequence retval = convertArcObjectToPythonObject(gp.CreateDatabaseSequence_management(*gp_fixargs((in_workspace, seq_name, seq_start_id, seq_inc_value), True))) File "c:\program files\arcgis\pro\Resources\arcpy\arcpy\geoprocessing\_base.py", line 496, in <lambda> return lambda *args: val(*gp_fixargs(args, True)) arcgisscripting.ExecuteError: ERROR 999999: Something unexpected caused the tool to fail. Please refer to the error help for potential solutions, or contact Esri Technical Support http://esriurl.com/support. Underlying DBMS error Failed to execute (CreateDatabaseSequence).
... View more
09-06-2018
08:15 AM
|
0
|
0
|
516
|
POST
|
Is there a bug in the Inspector class that stops a Subtype update on a new record? I have a custom panel which uses an Inspector embedded control. The Inspector is set up as follows, with a clear and schema load, as this process if for creating a new record. inspector.Clear(); inspector.LoadSchema(standaloneTable); Upon modifying the Subtype of the record, adding some attribute values, and attempting to save the new record as follows: EditOperation editOp = new EditOperation(); editOp.Name = "Road Name Create"; editOp.Create(inspector.MapMember, inspector); I received an error back that the EditOperation failed due to failing on an Attribute Constraint for another Subtype. It seems after load the Inspector hangs on to the default Subtype, even if it is changed in the Inspector. The Inspector looks as follows when initially loaded using LoadSchema(): Then it is modified to change the Subtype, and add attributes: In the debugger, the Attribute for the Subtype shows the Subtype code for Available: And here is the Subtype definitions:
... View more
08-22-2018
11:01 AM
|
0
|
3
|
1012
|
POST
|
Answering another one of my own for sharing... This was accomplished by creating a python Geoprocessing script that calls into Workflow Manager. An ArcGIS Pro Geoprocessing tool was creating using this script, and this tool was then called using the Geoprocessing.ExecuteToolAsync() method. Arcpy Script: Calling Arcpy Geoprocessing Tool:
... View more
08-21-2018
09:09 AM
|
0
|
0
|
485
|
POST
|
Answering my own question... Rather than create the row on the table directly, an EditOperation was used in which an Inspector was loaded with the modified values. When the EditOperation.Execute() call fails due to an Attribute Rule error, the EditOperation.ErrorMessage property is populated with the Attribute Rule error message. CurrentEditOperation.Name = "Road Name Create"; CurrentEditOperation.Create(AttributeInspector.MapMember, AttributeInspector); bool result = CurrentEditOperation.Execute(); if(!result) { var errorMessage = CurrentEditOperation.ErrorMessage; }
... View more
08-21-2018
08:57 AM
|
0
|
0
|
597
|
POST
|
Currently I am getting the generic error message "Violated attribute constraint rule" when adding a record to a Standalone Table with attribute rules through an Inspector. Is it possible to get the specific error message of the Attribute Rule from the GeodatabaseAttributeRuleException?
... View more
08-20-2018
01:54 PM
|
0
|
1
|
677
|
POST
|
Looking at a workflow where a user would create a job in workflow manager and edit it's extended properties, either from within ArcGIS Pro or from a workflow web interface. Then I would like to access those extended properties from a Job object in the ArcGIS Pro SDK. Is this possible?
... View more
07-26-2018
01:44 PM
|
0
|
1
|
531
|
Title | Kudos | Posted |
---|---|---|
1 | 09-07-2018 11:22 AM | |
1 | 02-11-2019 10:36 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:25 AM
|