Skip to main content
SUBMITTED

Add the Incremental "I" symbol on tables with the automatic incremental setting

Related products:TimeXtender Data Integration
  • April 3, 2024
  • 3 replies
  • 41 views

Forum|alt.badge.img+2

Hi,

Several clients I’ve spoken with find it confusing that tables with the “Automatic” data extraction setting have no visual cue that they are incremental when they inherit the incremental logic from their source table. 

Could you add the incremental I to these tables as well? 

 

The incremental I

 

3 replies

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • April 4, 2024

Hi @pontus.berglund 

How would you want it to look if you have this setup?

Two of the mapped tables are executed incrementally, but the third one isn’t.

I will get an error if I change this table to be set to Incremental load, unless I remove the mapped table that doesn’t use incremental load in the source.

With this setup and the data extraction set to handle deletes it will still work for the ones that do incremental load and ignore it for the one that doesn’t.


Forum|alt.badge.img+2

Hi @Thomas Lind,

In your case I agree that is not as clear cut, but I still think it should have the incremental I.

Landing.Customer is loaded incrementally, in the sense that it is not executed as a full load in a regular execution. Also, if you map this table to a new table in a different data area and have that table have the automatic data extraction setting, it would also be loaded incrementally, suggesting that Landing.Customer is indeed an incrementally loaded table.

The problem less experienced TimeXtender users are facing is that they are not able to identify which of their DW tables are incrementally loaded. A common example they find confusing is when they add conditional lookup fields to their (implicitly) incremental tables, and they end up as NULL since no new data is loaded in the execution. They don’t understand that they need to do a full load since they don’t see the table as incremental.

Additionaly, to address the error when setting Landing.Customer to be explicitly incremental.

If you set your table to have incremental load explicitly, then the error message would say that the ODX table(s) also need to have incremental load, correct? In my opinion, this is an arbitrary limitation set by TimeXtender with no benifit for the user. This limitation does not exist for business units.


Forum|alt.badge.img+1
  • Contributor
  • April 9, 2024

@Thomas Lind, If you want to make a distinction for the hybrid cases you could consider something like “I*” or some other symbol. In any case I would also assume that any mapping without a mark is fully loaded and any deviation from that principle should get some kind of mark.