Skip to main content
To homepage To homepage
Solved

Can't add a new column to semantic model

christian.koeken
Contributor
Forum|alt.badge.img

Dear Support,

I'm having a problem with adding a new column from MDW area to the semantic model (tabular).

I synced the model, I see the new column in Data Movement on the right side, but when I try to add the new column to the table it belongs to in the semantic model I don't get a 'plus’ symbol. 

It is a column I want to add to a fact table.

I tried to reboot the server, but that didn't solve it. I opened another semantic model and tried to add a new column to a table and that worked. But for some reason in this model it won't.

 

Can you help me?

TimeXtender version 6143.1

 

 

Best answer by christian.koeken

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.

 

View original
Did this topic help you find an answer to your question?

8 replies

Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

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

christian.koeken
Contributor
Forum|alt.badge.img

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. 

 

1 Attachments
Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi @christian.koeken 

Could you please try to Synchronize the SSL instance?

 

christian.koeken
Contributor
Forum|alt.badge.img

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? 

 

christian.koeken
Contributor
Forum|alt.badge.img

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 Hauggaard
Community Manager
Forum|alt.badge.img+5

@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?

christian.koeken
Contributor
Forum|alt.badge.img

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 Hauggaard
Community Manager
Forum|alt.badge.img+5

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

Reply


Most helpful members this week

Terms and ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings