You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Show which field alias is assigned to which asset type to better represent field reuse. (Feedback provided by user of the Data Loading Tools for Water - it was challenging to go back and forth to find which alias is being used for which specific asset type when trying to map a customer's data.)
Workflow could be:
Go to a Feature Classe's Fields.
Click the field being re-used across multiple asset types (e.g. diameter)
3.a. Show a 2 columns table associating alias and asset type.
OR
3.b. Clicking on one of the aliases opens the card for the given asset type using this alias.
It may be challenging to do this since the field alias information is being extracted from the metadata and this information was extracted from the asset package using a script on the mapx. We'd need to discuss how we could potentially do this.
The text was updated successfully, but these errors were encountered:
@avezina I can do the join and lookup on my end since from the breadcrumb I know here you are at when you got to the field card. Unless Ted wants to add it to the CSV directly. Let me know the decision.
Show which field alias is assigned to which asset type to better represent field reuse. (Feedback provided by user of the Data Loading Tools for Water - it was challenging to go back and forth to find which alias is being used for which specific asset type when trying to map a customer's data.)
Workflow could be:
3.a. Show a 2 columns table associating alias and asset type.
OR
3.b. Clicking on one of the aliases opens the card for the given asset type using this alias.
It may be challenging to do this since the field alias information is being extracted from the metadata and this information was extracted from the asset package using a script on the mapx. We'd need to discuss how we could potentially do this.
The text was updated successfully, but these errors were encountered: