ArcGIS Pro 2.6.2: How to import Alias field to the attribute table when performing join?

[JamalNUMAN]

ArcGIS Pro 2.6.2: How to import Alias field to the attribute table when performing join?

In the screenshot below, the excel table contains a row for field physical name and another row for alias field name. How the alias field can be imported as the attribute table when joined?

[DanPatterson]

There is no option within join

Join Field (Data Management)—ArcGIS Pro | Documentation 

especially for an excel file.  Perhaps the alias would be maintained if the table originated in a file gdb with original and alias specified already

[JamalNUMAN]

Thanks Dan.

Do you mean that we are left with one option: as the data is imported from excel to the attribute table by performing join, the alias fields need to be edited here!

The advantage of working in excel first refers to the fact that the environment is much more decent in addition to the fact that reordering fields is possible in contrast with the case in Pro

[DanPatterson]

Excel is not a substitute for a database management system.  you have to work within its limitations.

Work with Microsoft Excel files in ArcGIS Pro—ArcGIS Pro | Documentation 

Perhaps you missed ....

Format a table in Microsoft Excel for use in ArcGIS Pro

1. Make sure the first row of the worksheet is properly formatted, since it will be used for the field names in ArcGIS.

   Follow these best practices for field naming, particularly if you want to join an Excel table to another table:

   • Field names must start with a letter.
   • Field names must contain only letters, numbers, and underscores.
   • Field names must not exceed 64 characters.
2. If you have cells with numeric data, dates, and so on, ensure that the content is consistently formatted—in other words, make sure all numeric data is actually numeric. If there are other types of data in those rows, the field is converted to text when the table is opened in ArcGIS Pro.

These are a constant source of posted problems on this forum.

If you find working within Pro for tabular table onerous, alternatives exist.  NumPy, netCDF are better options since they are truly designed to facilitate "array" construction and processing. Excel is only "array-ish".

[JamalNUMAN]

Thanks Dan