Can I not drop and add column with the same name?

(0) Share

Report

Posted on by martinav

3,347

Why is this broken?

ClearCollect(NextDataItems,RenameColumns(FirstN(Filter(temporary_assign_wo,Updated<>2 And !IsBlank(_SNValve) ),Value(TextInput6.Text)),"SN_List","SN_List_Del"));
AddColumns(NextDataItems,"SN_List","d")

This works fine if I give the new column a different name.

I initially used DropColumns() but it resulted in the same issue. Renaming it out of the way doesnt work either.

Categories:

Building Power Apps

I have the same question (0)

All responses (13)

Answers (1)

Sort by

Al_10 1,691 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!
@martinav

ClearCollect(NextDataItems, AddColumns( DropColumns( AddColumns( FirstN( Filter( temporary_assign_wo, Updated<>2 && !IsBlank(_SNValve) ), Value(TextInput6.Text) ), "SN_List_Del", SN_List ), "SN_List" ), "SN_List", "d" ) );

Was this reply helpful? Yes No
martinav 3,347 on at

Like (0)

Report
Copy link

Link copied!

@Alex_10 ,

Yep, thats what I did the first time. Same result. It is intuitively correct, but no workie.

Its all happy if I change the name... same issue. It MUST be the same name, so I can do a patch back to a SQL list with identical column names.

Was this reply helpful? Yes No
Al_10 1,691 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!
@martinav

i suspect DropColums does not really deletes the column if datasource is SP, just hides it.

the only solution i have here is taking a full control over the result collection:

Clear(NextDataItems); ForAll( FirstN( Filter( temporary_assign_wo, Updated<>2 && !IsBlank(_SNValve) ), Value(TextInput6.Text) ) As ThisSN, Collect(NextDataItems, { Title: ThisSN.Title, SN_List_Del: ThisSN.SN_List, SN_List: "d" } ) )

Was this reply helpful? Yes No
martinav 3,347 on at

Like (0)

Report
Copy link

Link copied!

@Alex_10 ,

Yea, I was hoping to avoid that. There are like 25 columns. Thats a LOTTA stuff.

Well, anyway.

Thanks

Was this reply helpful? Yes No
WarrenBelz 155,420 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!
Hi @martinav ,

This should work

With( { wList: DropColumns( temporary_assign_wo, "SN_List" ) }, ClearCollect( NextDataItems, AddColumns( FirstN( Filter( wList, Updated <> 2 And !IsBlank(_SNValve) ), Value(TextInput6.Text) ), "SN_List", "d" ) ) )

Note you have a Delegation limitation with Add/Drop columns but you already had that with both of your filter criteria and FirstN

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.

Was this reply helpful? Yes No
martinav 3,347 on at

Like (0)

Report
Copy link

Link copied!
@WarrenBelz ,

Another great idea. However, same result. It still thinks its there. I moved the filter around to make this a bit more simple where its broken.

With( { wList: DropColumns( FirstN( Filter( temporary_assign_wo, Updated <> 2 And !IsBlank(_SNValve) ), Value(TextInput6.Text) ), "SN_List" ) }, ClearCollect( NextDataItems, AddColumns(wList,"SN_List","d") ) )

Result:
Same
Regarding delegation: Its true, but for this purpose, it does not affect the purpose for which I'm using this.

Was this reply helpful? Yes No
WarrenBelz 155,420 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!
Hi @martinav ,

I actually thought that would work, however the long way . . .

ClearCollect( colDrop, DropColumns( temporary_assign_wo, "SN_List" ) ); ClearCollect( NextDataItems, AddColumns( FirstN( Filter( colDrop, Updated <> 2 And !IsBlank(_SNValve) ), Value(TextInput6.Text) ), "SN_List", "d" ) ); Clear(colDrop)

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.

Was this reply helpful? Yes No
martinav 3,347 on at

Like (0)

Report
Copy link

Link copied!

@WarrenBelz ,

I've been down this avenue as well. I'm with you about the 'should work' situation. I suspect this must have something to do with the fact the data comes from an SQL Table? Well, if nothing makes sense, it something that doesnt make sense that is the explanation.

Was this reply helpful? Yes No
WarrenBelz 155,420 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @martinav ,

Got it to work with ShowColumns (RenameColumns fails too in SharePoint) in the first bit - and you are correct that it should work . . .

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.

Was this reply helpful? Yes No
martinav 3,347 on at

Like (0)

Report
Copy link

Link copied!

@WarrenBelz ,
I also have an issue with Patch() with SQL tables. I also cannot patch from a collection into an SQL table if ANY columns in the collection do not exist in the table. It will give the error "ColumnName Does not Exist". Even if I'm not patching to that particular column. It fails. This has been a real PiTA! I have blown like 4 days on this now. I am now going to create ANOTHER collection, specifically created those columns that are necessary to generate SN_List. Then try to Patch() that back into table. I'm losing my bloody mind on this.

Was this reply helpful? Yes No