|
POST
|
Well for what it's worth, the dirty area and error layers should only appear in a map as sublayers of a UtilityNetworkLayer. So if you're searching through all the layers in order, you should be able to find a positive match and exit your loop before getting to the problematic tables. If not, you can just catch the exception and continue.
... View more
06-21-2018
02:38 PM
|
0
|
0
|
1231
|
|
POST
|
Hi John, I can confirm that this is an issue. We had intended GetControllerDatasets() to be used with user tables and not the system tables. Could you tell us more about what you are trying to accomplish? (At this point, our proposed solution is to have Table.IsControllerDatasetSupported() return false for these tables, which would fix the bug, but maybe not give you the behavior that you are looking for). --Rich
... View more
06-21-2018
10:47 AM
|
0
|
2
|
1231
|
|
POST
|
Hi Emiliano, Sorry, we do not have any experience with the entity framework. -Rich
... View more
06-20-2018
10:44 AM
|
0
|
0
|
1021
|
|
POST
|
So there's an Oracle limitation with 1000 clauses in an "in" clause, but you're failing with a much smaller number of records, right? Do you have a reproducible case that you can send to support? --Rich
... View more
06-18-2018
09:01 AM
|
0
|
2
|
2021
|
|
POST
|
This isn't something we've seen before. In theory, we know what is causing this; the error code tells us that the Variant's type isn't valid. In practice, we don't know what could be causing this. If you have a consistent, or sometimes consistent, reproducible case, could you please log it with support? Thanks, --Rich
... View more
06-15-2018
09:12 AM
|
0
|
0
|
1514
|
|
POST
|
Hi Bart, I wrote a few lines of code and was able to select 500 features using FeatureLayer.Select(queryFilter, SelectionCombinationMethod.Add), where the queryFilter returned 200 rows at a time. This was with a feature service workspace. Could you tell me more about what kind of data source you were using, and how you went about selecting the records? Code snippets would be fine. Thanks, --Rich
... View more
06-14-2018
10:38 AM
|
0
|
4
|
2021
|
|
POST
|
Luke, I'm not sure I understand the question. You can get a Table object from a Geodatabase object using OpenDataset<Table>. This is true if the Geodatabase object comes from a file geodatabase, an enterprise client-server geodatabase or a feature service geodatabase. What am I missing? --Rich
... View more
06-14-2018
10:07 AM
|
0
|
7
|
4108
|
|
POST
|
Hi John, If you have a row and want to get the asset type, you can always call UtilityNetwork.CreateElement(), followed by Element.AssetType. That's certainly guaranteed. But if you're trying to create a row and want to fill in the asset type, the best answer for now is to use the field called ASSETTYPE. I'm not aware of a case where this would not work. I agree that the API should provide a more formal mechanism for getting the asset type field name. I'll put it in the backlog for a future release. --Rich
... View more
06-08-2018
10:31 PM
|
0
|
0
|
907
|
|
POST
|
Hi Devon, No, you cannot change the spatial reference of a feature class with the C# SDK. All DDL (data definition language) takes place through Python or geoprocessing. The QueryDescription class is used for exposing spatial data as a temporary in-memory table, not for changing what is stored in the geodatabase. --Rich
... View more
06-07-2018
12:40 PM
|
0
|
1
|
3361
|
|
POST
|
Luke, If you publish a table as part of a feature service, you can use another layer on that service to get a Geodatabase pointer. Once you have that, you can use gdb.OpenDataset<Table>(name) as you would expect. The only thing to look out for is the feature service will change the name of the table that is exposed. --Rich
... View more
06-05-2018
03:28 PM
|
1
|
9
|
4108
|
|
POST
|
It's in our roadmap to be sure, but unfortunately no plans for the short-term.
... View more
05-31-2018
08:45 AM
|
0
|
2
|
2952
|
|
POST
|
The best practice is definitely to call Dispose on Row and Feature objects. Keeping these objects around in memory can cause the system to hold onto file handles or database connections.
... View more
05-31-2018
08:42 AM
|
0
|
0
|
2605
|
|
POST
|
No, we haven't yet added support for metadata to the ArcGIS Pro API.
... View more
05-30-2018
04:21 PM
|
0
|
4
|
2952
|
|
POST
|
As an aside, the FeatureClass, RowCursor, and Row classes all implement System.IDisposable. For correct object lifetime management, you should wrap usage of those variables in a using block. You may have simply removed that code to simplify the sample, but I wasn't sure. (This does not have any impact on the actual delete bug). We're planning on clarifying this in the geodatabase conceptual documentation in the next release.
... View more
05-30-2018
10:01 AM
|
0
|
2
|
2605
|
|
POST
|
As a workaround, you should be able to use the EditOperation.Delete(MapMember, Int64) override, using the layer and ObjectID.
... View more
05-30-2018
09:52 AM
|
0
|
1
|
2605
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 12-13-2024 11:22 AM | |
| 2 | 01-29-2026 09:34 AM | |
| 2 | 01-28-2026 08:20 AM | |
| 1 | 12-10-2025 09:15 AM | |
| 2 | 11-30-2025 12:23 PM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|