+2I’m using the ArcGIS Portal writer to publish point data to a portal. The dataset publishes successfully in FME and all of the points appear on the map, but the attributes don’t show up in the table. Removing specific fields doesn’t seem to help. Has anyone seen anything like this before?
+36Hi there, just before the Portal feature service writer, can you inspect the feature cache records to see the attributes have values. Clicking in the visual preview table and then the Feature Information window is always best.
Then you need to perform Attribute Mapping.
On the writer, check that the User Attribute tab, is it on manual and are the ports red?
You have the option to use “automatic” attribute definition. This assumes you have already used AttributeManager or AttributeRenamer to transform the attribute names. In this process of switching from manual to automation, you may need to drop and create the feature service again
+2Hi, the User Attribute tab has all green arrows. No red in sight! I’ve used the split-half method to see if there are any issues with the data itself getting published; nothing, not even a string field with a single character publishes with data. We have other processes that publish from FME to this portal, so I know it’s possible! Publishing the same data to ArcGIS Online is successful, so really scratching my head on this one.
+2So it turns out that field mapping from FME to Portal is case-sensitive. The fields being published to Portal were in all caps, while the fields getting created in Portal were all lowercase. For some reason, when FME created the fields in lowercase, it couldn’t map the data from the input’s uppercase fields. I added an Attribute Manager transformer to change the input’s fields from uppercase to lowercase, and that fixed the issue.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
