Currently, when adding the same data source to multiple ODX instances, TimeXtender requires each instance to use a unique short name. This often leads to awkward or overly long naming conventions just to differentiate between otherwise identical sources.
It would be much more user-friendly and scalable if TimeXtender allowed reusing the same short name across different ODX instances, with an option to group or filter them by instance. This would allow:
-
Teams to avoid inconsistent or verbose short names like
CRM_EU_ODX1vsCRM_US_ODX2. -
Short names to remain meaningful and clean (
CRM,ERP, etc.), while clarity is maintained through instance-level organization. -
Better alignment with how distributed teams manage similar data sources across environments or regions—especially in global setups or OTAP environments that still need access to production data.
This improvement would help reduce clutter, improve readability, and make large-scale data environments much easier to manage.
