AddColumns fails when adding column to collection from ShowColumns

(3) Share

Report

Posted on by NasserA

Using Office 365 Power Apps Version 3.20013.29

The code below performs the following:

vRequestRecords has the columns: "Title", "ItemType", "ItemName", "RequestType", "Revision", ….. and several others.

The function ShowColumns extracts 4 columns ("ItemType", "ItemName", "RequestType", "Revision") from vRequestRecords.

The function AddColumns then adds 1 column ("Title") to the result of ShowColumns.

Until Friday, January 31,2020, it worked without a problem.

Today, February 3, 2020, it shows the error messages listed.

It looks like a Power Apps bug introduced in a recent Office 365 update.

CODE:

AddColumns(ShowColumns(vRequestRecords, "ItemType", "ItemName", "RequestType", "Revision"),

"Title", ItemType.Value & ": " & ItemName.Value & " (" & RequestType.Value & ")" & " (" & Revision & ")"

)

ERROR MESSAGES:

A column named 'Title' already exists.

The function 'AddColumns' has some invalid arguments.

Categories:

Building Power Apps

I have the same question (0)

All responses (21)

Answers (1)

CarlosFigueira Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Thank you for reporting this issue; I'll pass it to the product team right away.

Was this reply helpful? Yes No
Stefan_J 7 on at

Like (0)

Report
Copy link

Link copied!

I have the same issue here.

Collection A with columns: ID, Title, Date
I use AddCollection(B, ShowColumns(A, "ID", "Title"))

Then: AddCollection(C, AddColumns(B, "Date", Today()))

Error: The columns named Date exists.
In the preview of the collection B I see only the columns ID and Title.

Was this reply helpful? Yes No
McCall Saltzman Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hey all. We've identified the issue (related to performance optimizations for data calls) and will prepare a fix. In the mean time, this can be resolved by not using a name that is present in the original table. Sorry for the inconvenience.

Was this reply helpful? Yes No
NasserA 27 on at

Like (1)

Report
Copy link

Link copied!

There is evidence of this problem being reported and fixed in the past – at least a year ago. Just searching for it in the internet shows a good number of old reports.
Microsoft Power Apps team needs to do a better job at managing code changes and performing tests to filter out previously reported – and fixed – bugs which are now being reintroduced by their own team.
When bugs are reintroduced in a software product, it is a serious issue indicating bad code change controls and inconsistent automated testing.
What old bugs should we bee looking out for next?
This is inexcusable and should be fixed immediately.

Was this reply helpful? Yes No
Verified answer

NasserA 27 on at

Like (1)

Report
Copy link

Link copied!

The problem has been resolved with a product update.
It no longer exists with Office 365 Power Apps Version 3.20022.19.
Hopefully regression testing as been put in place to prevent it from reoccurring again.
Thank you PowerApps team for the prompted solution.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi there

I'm still seeing the same error message.

Best regards

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
Hey all,

Same here, we are at version 3.20023.8 and the issue is still in effect.
We are creating a collection based on an SQL table wit the following formula:
ClearCollect(col_ColName,'[SQL Table]',AddColumns(col_ColName,"Changed",true))
The app keeps indicating that the column already exists in the collection.

Please advise!

Thanks

Was this reply helpful? Yes No
MiLoCore 62 on at

Like (0)

Report
Copy link

Link copied!

running in the same error today evening!
Are there any news about it?
Thanks a lot

Was this reply helpful? Yes No
marpio on at

Like (0)

Report
Copy link

Link copied!

Version 3.21(...) problem still there...

Was this reply helpful? Yes No
james_hathaway 427 on at

Like (1)

Report
Copy link

Link copied!

It seems this BUG has REAPPEARED.

I too am getting the "Column already Exists" error, for a column that most certainly DOES NOT EXIST.

I also agree with @NasserA
This is inexcusable - especially as it was a big that was previously reported and fixed, and yet is back!

Microsoft - Please fix.

James.

Was this reply helpful? Yes No