Skip to main content
To homepage To homepage

Hi there! 

We have had a small problem recently whereas Table A is on the staging/DSA layer and contains the following columns: 

Column 1 (PK)
Column 2 (PK)
Column 3
Column 4 … etc

Now this table has three sources - three Business Central instances. In two of the sources the original order of columns is Column 1, Column 2 but in the third source the order is Column 2, Column 1.

We get the following error when incremental load is enabled:  "TIMEXTENDER COPY DATA LOOP", "Failure happened on 'Sink' side, Column 2 contains an invalid value. 

We have been able to manage this error previously by ordering the columns in the same way as in the source.

However, now the sources have different orders of the columns and therefore not possible to use that way to get around this. 

Any ideas or suggestions? 

Hi,

from the error it looks like you are using ADF, is that correct? Have you synchronized objects on your ODX / synchronized your Prepare with your Ingest after the field ordering changed? I assume you have synchronized your source / updated metadata.

 

 

Hi,

from the error it looks like you are using ADF, is that correct? Have you synchronized objects on your ODX / synchronized your Prepare with your Ingest after the field ordering changed? I assume you have synchronized your source / updated metadata.

 

Yes to all, unfortunately. 

Hi,

then I would open a support ticket. If your flows are not massive, not using ADF would likely also help.

Hi ​@darrirafn 

I got a Zendesk case with this issue. Perhaps a colleague.

Besides the behavior being wrong you may be able to control the order fields are shown a little bit.

I am not 100% sure it can work, but if you make sure to add the individual fields for all the tables you merge the same way it may show up as in the same order.

Terms and ConditionsCookie settingsAccessibility statement