Looking at article Working with Geodatabase Field Aliases: Altering Alias Values (safe.com) I am trying to run the same directly to an AGOL hosted feature layer. I have created the requisite "_alias" field to match those that I need alias values for, but no dice. Also tried adding the same fields (matching the attribute manager) to the writer attributes (manual setting) but the result simply created additional fields with the "_alias" suffix. Is this possible with this writer?
Solved
Is the featurewriter able to create field aliases when outputting to AGOL/Esri Enterprise
+5- Contributor
Best answer by kailinatsafe
ridleyj wrote:
I didn't use or test the format writer
Hello @ridleyj, take a look at the attached updated workspace. The aliases should be viewable in ArcGIS Pro now using the following steps:
- Adding the appropriate writer (FGDB writer for example)
- Removing all attributes with '_alias' from the writer feature type user attributes window
If the alias attributes are left in the user attributes section of the writer feature type, they will be written as literal attributes.
Also, as mentioned earlier FME doesn't support writing aliases to feature services as of yet. You will need to use the FGDB or SDE GDB writers to translate alias fields.
One potential idea (untested) could be to write aliases to FGDB and publish or push to AGOL, however I am unsure if the aliases would be maintained or dropped. Let me know if you're still having issues writing aliases. Happy to help, Kailin.
+11- Contributor
I believe aliases are poorly handled in FME. Please see my idea and upvote: https://community.safe.com/s/bridea/a0rDm000000zVtbIAE/improve-handling-of-aliases-for-datasets-that-support-them
1 person upvoted this
+21- Safer
Hello @ridleyj, FGDB supports aliases, but I don't think the AGOL Writer is capable of this yet. FMEENGINE-74436 was filed to add support for aliases on feature services.
Did you reference the 'Advanced' section of the article to see how to add new field aliases using FME? iMark also explains it well here.
Regarding SDE, I wouldn't expect the FeatureWriter to behave any differently than the format writer when it comes to aliases. Are you able to write aliases with the format writer, but not the FeatureWriter? Would you be able to share a copy of your workspace and the version/build of FME being used? Happy to help, Kailin.
1 person upvoted this
+5- Contributor
Hi @kailinatsafe
Thanks for reaching out to help.
I did reference the advanced section (by my understanding of it!) and have the attached FMWT test, with sample data, for you to have a look at.
I am using
Version: FME(R) 2022.2.5.0 (20230329 - Build 22795 - WIN64)
OS Locale Name: en_NZ
OS Encoding: windows-1252
Process Encoding: UTF-8
FME API version: 4.0 20220615
Registration Key: 3-912-533-582
Registration: Licensed
Serial Number:
Customer Number:
Home Folder: C:\\Program Files\\FME\\
Operating System: Microsoft Windows 10 64-bit (Build 19041)
+21- Safer
- Best Answer
ridleyj wrote:
I didn't use or test the format writer
Hello @ridleyj, take a look at the attached updated workspace. The aliases should be viewable in ArcGIS Pro now using the following steps:
- Adding the appropriate writer (FGDB writer for example)
- Removing all attributes with '_alias' from the writer feature type user attributes window
If the alias attributes are left in the user attributes section of the writer feature type, they will be written as literal attributes.
Also, as mentioned earlier FME doesn't support writing aliases to feature services as of yet. You will need to use the FGDB or SDE GDB writers to translate alias fields.
One potential idea (untested) could be to write aliases to FGDB and publish or push to AGOL, however I am unsure if the aliases would be maintained or dropped. Let me know if you're still having issues writing aliases. Happy to help, Kailin.
+5- Contributor
kailinatsafe wrote:
Hello @ridleyj, take a look at the attached updated workspace. The aliases should be viewable in ArcGIS Pro now using the following steps:
- Adding the appropriate writer (FGDB writer for example)
- Removing all attributes with '_alias' from the writer feature type user attributes window
If the alias attributes are left in the user attributes section of the writer feature type, they will be written as literal attributes.
Also, as mentioned earlier FME doesn't support writing aliases to feature services as of yet. You will need to use the FGDB or SDE GDB writers to translate alias fields.
One potential idea (untested) could be to write aliases to FGDB and publish or push to AGOL, however I am unsure if the aliases would be maintained or dropped. Let me know if you're still having issues writing aliases. Happy to help, Kailin.
Thanks @kailinatsafe , that answers my question - aliases on feature services not supported yet, but FMEENGINE-74436 is filed to add this support. The FGDB options work fine, thanks. Have noted your idea to publish to FGDB and push up/publish to AGOL feature service - this will likely be the approach until the alias option is embedded.
Cheers
Jason.
It seems that FME does not have the capability to write aliases to feature services, even on AGOL. The recommended solution is to use the FGDB or SDE GDB writers to convert alias fields. You can consider publishing to FGDB and then pushing it to AGOL as a temporary fix.
Are you trying to find the best essay-writing services? You only need to look at this site. They have a stellar reputation for producing original, high-quality work that satisfies your academic requirements without any plagiarism. Their group of skilled writers guarantees prompt delivery and client contentment. go to page for the array of services available on the page for a hassle-free academic experience. I recently used their services, and the outcomes amazed me. It's a surefire way to elevate the quality of their academic work and streamline the writing process.
Reply
Rich Text Editor, editor1
Editor toolbars
Press ALT 0 for help
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.