Answered

AddColumns to an existing collection - getting error that column name already exists, even though it doesn't

(0) Share

Report

Posted on by CU15091556-0

I'm trying to add 2 columns to an existing 1-column collection. In case it matters, the 1-column collection (colVPOSCollectedSkills) is produced with Distinct() to grab an unduplicated list of skills that have been assessed for a selected student. Due to the use of Distinct(), the column name is Value.

I want to add another column (ViewProfics) to this existing collection with the value false. I have tried locating the code as:

a second item within the initial ClearCollect
an additional step immediately after the initial ClearCollect, and
a separate button for testing purposes.

Here are the various code snippets I've tried (separately) in all the locations described above. Every time, though I get the error that the column name already exists, even though it doesn't.

Collect

Collect(
 colVPOSCollectedSkills,
 AddColumns(
 colVPOSCollectedSkills,
 "ViewProfics",
 false
 )
)

ClearCollect

ClearCollect(
 colVPOSCollectedSkills,
 AddColumns(
 colVPOSCollectedSkills,
 "ViewProfics",
 false
 )
)

Collect with the collection value only in the AddColumns function

Collect(
 AddColumns(
 colVPOSCollectedSkills,
 "ViewProfics",
 false
 )
)

AddColumns without any Collect or ClearCollect function

AddColumns(
 colVPOSCollectedSkills,
 "ViewProfics",
 false
)

There are some older posts on this error, but none of them got me to the finish line. Hoping one of you can! Thanks!

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Verified answer

WarrenBelz 154,799 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!
Hi @RB2GSO ,

You need to use a different name for the new collection.

ClearCollect( colVPOSCollectedSkills2, AddColumns( colVPOSCollectedSkills, "ViewProfics", false ) )

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

MVP (Business Applications) Visit my blog Practical Power Apps

Was this reply helpful? Yes No
CU15091556-0 49 on at

Like (0)

Report
Copy link

Link copied!

Thanks @WarrenBelz! That works, so I'm unstuck.

Is that a way to workaround a likely glitch I've created elsewhere or does PowerApps simply not intend to allow us to add columns to an existing collection? The documentation on AddColumns() makes it sounds like it should be a simple thing to tack extra columns on.

I ask because, if I'm doing something boneheaded elsewhere that requires this workaround, I'd love to know it so I don't have to have a bunch of inter-step collections.

Thanks!
Robin

Was this reply helpful? Yes No
WarrenBelz 154,799 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!
@RB2GSO ,

Yes, but it needs to be done by creating a new data set and Power Apps does not seem to like using the same one. You can try this

ForAll( Sequence(CountRows(colVPOSCollectedSkills)), Patch( Index( colVPOSCollectedSkills, Value ), {ViewProfics: false} ) )

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

MVP (Business Applications) Visit my blog Practical Power Apps

Was this reply helpful? Yes No
Suggested answer

HandyK 2 on at

Like (0)

Report
Copy link

Link copied!

In case it helps, I have avoided creating a third collection (first being the initial data, second being the Distinct collection), by adding the columns to the Distinct call:

ClearCollect(colUniqueCollection,
   ForAll(
       Distinct(colInitialCollection, ThisRecord),
       AddColumns(Value, NewColumnName, Expression)
   )
)

So, it would look something like this:

ClearCollect(colVPOSCollectedSkills,
   ForAll(
       Distinct([Your initial collection], ThisRecord),
       AddColumns(Value, ViewProfics, false)
   )
)

It might be worth checking out if it works for your scenario.

Was this reply helpful? Yes No