Features Missing After Check-out?

1364
6
08-16-2010 07:37 AM
EricHajek1
Occasional Contributor
Hi all,

I'm having an issue with checking out features from an SDE database to .axf. Here's the deal:
I've got a feature class with a bunch of different subtypes in it, but when I export it the usual way (through the data manager toolbar, the way I've been doing it for months), some of the features just don't get exported. Usually its by subtype, so for instance, all the headwalls and plugs will export fine, but the inlets won't export at all. There are no definition queries, wierd symbology or form behavior that should be causing anything like this, and I can't see to figure out why some features export, and others refuse to. I've used different MXDs, applied / not applied custom forms, exported the entire feature class / just a small extent, nothing seems to affect it.
It had been working fine for months, and the trouble started when I deleted four fields from the feature class. They were just text fields that had no relationships or anything associated with them. If I export the feature class's features to a shapefile, I can then successfully export all the features, but of course can't use the custom forms anymore / check in edits to the SDE how I'd like to.

This happens with ArcPad 8 and 10, on different computers, using 9.3.1 to check out.

If anyone has run into an issue like this and gotten it fixed I'd love to hear from you!
Thanks,
Eric
Tags (3)
0 Kudos
6 Replies
EricHajek1
Occasional Contributor
I think I have this figured out.

I think what's happening is that the check-out process is enforcing validation rules, even though I don't have that box checked. Instead of giving an error and failing to check out, it just leaves troublesome features out. After I manually corrected some of the attributes of the features that weren't checking out, it seems to be mostly working again. Still no idea why it just sort of started happening, but oh well. If anyone has any idea of the exact cause, I'd love to hear it, because my domains / subtypes should allow for the values that were failing this hidden validation.
Eric
PetePedrazzini
New Contributor III
I have related problem but I dont have any validation rules. Some point or polygon features missing for no particular reason. I can see them in ArcMap but when check-out they not there.
0 Kudos
by Anonymous User
Not applicable
I am having the same issue.  We are using ArcInfo 9.3.1 and ArcPad 7.1 and the ArcPad toolbar.  I am checking out of a personal geodatabase, I select my features i want to check out and go through all the steps and it successfully checks out, but then I find that some selected features are not checked out.  Anybody have a clue whats causing this, it worked fine for the last year and nothing has changed with the feature class.  Thanks
Kyle
0 Kudos
MikeGeorge
New Contributor II
I have experienced the same problem.  Using ArcGIS 9.3.1 SP2, and AP 8 Data Manager, then deploying to a Topcon GMS-2 running AP 7.1.1, I would check out to a .axf and many of the assets from the feature class would not be present in the AP project.  I was able to trace the problem to the domains and subtypes that were built after some of the features had already been created in the feature class.  If a feature had an attribute in any field, that did not match the current coded domain or subtype, even if the validate features check box was unchecked in the 'Get Data for ArcPad' window, those features would not be checked out in the ArcPad .axf.  Also, if the attribute was blank, even if the field accepted "Null" values, those features also would not check out.  Once I was able to fix each and every attribute in every field, whether or not that field was checked out, to either match the coded domain/subtype, or set it back to "Null," only then would those features correctly show up in ArcPad.  This was a major problem for the collection project I was managing.  It wasn't until the data was checked back in that I was able to even discover the problem because the field operator assumed the feature did not exist, recollected the asset, and then it became a duplicate of an already existing feature in ArcMap.

I hope this offers some additional help to those that are experience this same issue.
0 Kudos
RobertHernandez3
New Contributor

Hi Everyone,

I've been having somewhat of the same problem, however my issue is that the attributes with a related object would not checkout in ArcPad. Those records without a related object checked out just fine. Currently using Arcpad 10.2 along with ArcMap 10.2. Any help or suggestions would be highly appreciated.

0 Kudos
PetePedrazzini
New Contributor III

I don't know if this is related or not but I recently noticed that features with duplicate key or improperly set domains are not checked out. So I think Eric is right, if features didn't pass validation rules they will not be checked out by data manager. Once issues corrected they check out just fine.

0 Kudos