Is there a work-around for BUG-000149858 (join name and destination table name contain a percentage symbol after creating a join)?

[AspenN]

We are joining non-spatial tables in a PostgreSQL database to GIS feature classes (based on a common id). When the join occurs, a percentage sign (%) appears in the joined table name and field names. This causes weird behaviors in Pro (sometimes not allowing symbolizing based on joined fields) and doesn't work well when referencing the fields using the JS API. Is there a work-around for this issue? It seems like a pretty common workflow (joining a database table to a feature class) to be having such a serious issue, especially when the bug was first reported in 2014 (10 years ago). 

[MarceloMarques]

@HeathClark - Esri Technical Support status on the BUG.

------------------------------------------------------------------------------------------------------------------------------------------------------
BUG-000149858 - The Join name and Destination table name contain a percentage symbol (%) after creating a join between a feature class and a stand-alone table in ArcGIS Pro.

https://support.esri.com/en-us/bug/the-join-name-and-destination-table-name-contain-a-perc-bug-00014...

Duplicate of BUG-000156380: This bug does not state a problem. The query layer naming of joined tables using the % is general to all enterprise databases. The associated issue, BUG-000156380, indicates a publishing problem that some may be experiencing.

Status: Duplicated.

------------------------------------------------------------------------------------------------------------------------------------------------------

BUG-000156380 - Unable to query the map service from the REST endpoint using the fully qualified name when applying a join with a feature class and a non-registered table.

https://support.esri.com/en-us/bug/unable-to-query-the-map-service-from-the-rest-endpoint-bug-000156...

Status: In Product Plan

Workaround: Instead of a fully qualified name, use only the field name.

------------------------------------------------------------------------------------------------------------------------------------------------------

[TanuHoque]

@HeathClark - 

This defect has presented many challenges. The resolution we are working toward is for map services. Based on current progress, we are working to provide a resolution in one of the upcoming releases in 2024.

[berniejconnors]

It is bad practice to use the SQL wildcard character ("%") in database table names or column names.  Changing your table names and column names would be a good idea but it may not be practical if you have many systems that already reference your tables and columns.

Bernie.

[AspenN]

The % is added automatically during the join process by the software. We are hoping to find a solution to remove the %

[berniejconnors]

xkcd for the win!

https://xkcd.com/2881