table control 'expected text value' error on new columns

[PowerAddict]

Can you please share an image of the error you are getting (showing where specifically you are getting the error)? 

---
If you like this reply, please give kudos. And if this solves your problem, please accept this reply as the solution. Thanks!

Hardit(Haman)

[PowerAddict]

Also since the error says that the type is not compatible with the collection, can you share any other formula that you are using to populate the collection prior to this formula?

---
If you like this reply, please give kudos. And if this solves your problem, please accept this reply as the solution. Thanks!

Hardit(Haman)

[Caroline]

@PowerAddict @v-siky-msft It's the part that is drawing from another data source:

[PowerAddict]

And the controls you have for the values that you are trying to patch, are they the same data type?

Two more questions: 

1. Is this the only place in the app where you are collecting items into the Reports collection? If no, then please share the formula. 

2. Is there a specific reason you are using two collects and not combining both into one?

---
If you like this reply, please give kudos. And if this solves your problem, please accept this reply as the solution. Thanks!

Hardit(Haman)

[Caroline]

@PowerAddict yes, it's the only place where I'm collecting to Reports. I used two collects, just because they are two different data sources. I have just combined them and got the same error.

[PowerAddict]

You should be able to use one collect though. Because this way, even if it works, it will add two rows, first with the names, and second with the email, phone and other details. 

Can you go to View->Collections->Report Collection and show me the column headers that are visible there?

---
If you like this reply, please give kudos. And if this solves your problem, please accept this reply as the solution. Thanks!

Hardit(Haman)

[Caroline]

@PowerAddict 

[Caroline · Accepted solution]

So, I thought I'd take out the whole formula and add it one item at a time (again), to try and identify where the error is, and this time it was accepted without any errors. As the collection was looking good, I reloaded the data table (which was still showing [object Object] where the original data source column was an option set), and that is looking fine too.

Thanks for the assistance, @PowerAddict @v-siky-msft