Whenever you implement data movements in TimeXtender some objects get created to support this. TimeXtender gives these objects automatic names which is usually fine. In the case of modern ERPs like Business Central with added features (4PS and other vendors), there are additional tables with extra fields added onto existing BC tables. These usually get rather long table names, sometimes including a GUID, which then cause problems when you pull data into a Data Area or Datawarehouse layer due to the name of the usp_xxx object.
The idea is to add some settings to TimeXtender that allow you to deal with this:
- Do nothing (same as now), may fail if the source table name is too long
- Warning, tell the user that this table may fail if copied to a further layer
- Handle automatically, shorten names in ODX/DWH Data Area automatically if required. This could be as simple as disabling the automatic prefixes that get added.
Given that more and more products will have data stored in systems with less restrictive table names than SQL Server it will be very useful to have some way of dealing with this.
This idea comes from a ticket #26993 , I have seen the same with some other Business Central-based ERPs where you either have BYODB or Data Lake replication.
