Skip to main content
To homepage To homepage
Question

Mapping from Ingest to Staging seems broken

  • February 17, 2026
  • 2 replies
  • 27 views
nick.van.treuren
Visitor
Forum|alt.badge.img

At our client Heijmans, we're experiencing differences in mappings from the same table in the Ingest.

We're on TDI 7208.1 and Prepare Instance oDataWareHouse version 3655

Using a Salesforce source, we're using the table Object__c where we approximately have 400 fields available. At the moment, we only have about 350 ‘checked’ in the Ingest. However, when adding new fields (of the remaining 50), and transferring and synchronizing the project, the mapping doesn’t update. 

It's even possible to add the same table as a second source and then, the whole list becomes available. 

To give another example, the standard field [odx_timestamp] has been checked in the Ingest, but is only visible in the second mapping in the project.

 

 

 

2 replies

Gabriele Sangrigoli
Starter

Hello Nick 

After synchronizing the project, have you tried executing the transfer task?

After executing the transfer task you should double click on the mapping and find all the unmapped fields. 


I strongly suggest to have a look at these two:

(1) Synchronize Prepare Instance Objects with Ingest Instance Objects | Community 
(2) How to add a new field or column to an existing Ingest Instance data source and Prepare Instance data area | Community​

​​​​​​Try to follow all the necessary steps present in these guides in the right sequence and let me know if it solves the issue, 

Gabriele Sangrigoli 
Data Analyst - Avito AS 

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Thomas Lind
  • Community Manager
  • February 24, 2026

Hi ​@nick.van.treuren 

How do you synchronize the objects against the Ingest Instance.

My preferred method is to use this menu on the Ingest while having the Prepare Instance open.

The reason I prefer this, is that the remapping menu only shows fields that need remapping, otherwise it shows nothing. 

This will help when adding new fields to a existing table. I think this is why it added the extra fields when mapping the same table twice as it do not need a synchronization when adding a new table.

Terms and ConditionsCookie settingsAccessibility statement