Hi @christian.koeken can you please provide a screen recording showing the issue?

Hi Christian,

I have included a word document with the issue.

I want to add the LDS column to Jobs, but when I try I see the symbol you'll see in the document.

I can add the column to Supplier or Selection or some other dimension table, but that is not right. 

Hi @christian.koeken 

Could you please try to Synchronize the SSL instance?

Hi Christian,

As in my first message, I said I synced the model and that I saw the new column in data movement.

I have tried it again. TimeXtender said 'No changes to synchronize’ and also the same issue.

What if I try the option Synchronize with Remapping? 

Hi Christian,

Here I am again. I think I found the solution myself.

I did a right-click on the Jobs table and choose Edit Table. Then I added the LDS column by selecting the check box. Then I clicked on OK, but then I get 'Object not set to an instance of an object’ error. 

A colleague has added two custom fields to the Jobs table and one of these custom fields isn't well designed. I made a screenshot of the the the two custom fields and then deleted them. 

And now I can add the LDS column.

@christian.koeken good to hear that you found the cause of the error! Can you elaborate what in particular made the custom fields not well-designed? If you redesign and re-add the custom fields does the same issue occur or does it work as expected?

Hi @Christian Hauggaard,

I re-added one of the two custom fields, but the issue still occur :(

The screenshot above is nothing more than concatenate three fields. But If I want to add a new column to the model, I'll get the same issue again.

@christian.koeken thank you for confirming. I have created a support ticket for this in order for us to investigate further