AddColumns fails when adding column to collection from ShowColumns

[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.

[CarlosFigueira]

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

[Stefan_J]

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.

[lesaltzm]

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.

[NasserA]

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.

[NasserA · Accepted solution]

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.

[roel-occ]

Hi there

I'm still seeing the same error message.

Best regards