Adding a general option into a drop down list

(0) Share

Report

Posted on by diegoadum

Hi folks,

I have the below expression in my SharePoint form that works amazing.

But, as you can see here, in my new form, which is isolated from SharePoint, I mean, I created in PowerApps studio, it seems something is not making him happy. If I put the cursor over the last word "Cliente" it says "The Specified column "Cliente" does not exist. And if I put the cursor over the previous one, it says "A column named "Cliente" already exists". So I'm wondering why in my previous SharePoint form this works. Of course the setup is the same.

My goal here is to add the sentence "No es cliente crítico" at the beginning of the special customer list.

Here the same image but from the project that is using the form in the SharePoint list. As you can see, there is no errors!!

Categories:

Building Power Apps

All responses (3)

Answers (1)

Sort by

Verified answer

RandyHayes 76,299 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
@diegoadum

You might be seeing a haunting issue that occurs ever so often where you actually need to re-type the formula, and, suddenly it is fine.

However, I might also suggest that you change the order of your formula. Instead of renaming columns and then showing columns, show columns and then rename:

<previous ClearCollect> ; Collect(ListaClientes, RenameColumns(ShowColumns('Clientes Criticos', "Title"), "Title", "Cliente"))

This way you have already eliminated the conflicting column in the ShowColumns and then all you have is Title left...Rename it.

Hope this helps some.
diegoadum 78 on at

Like
a
(0)

Report
Copy link

Link copied!

Thank a lot for your notes. Nevertheless, it makes no senses at all! 😉 I mean, why in one scenario works and then is not working anymore.
RandyHayes 76,299 Super User 2024 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

@diegoadum

I hate to say it, but sometimes PowerApps makes no sense! I've seen situations where simply re-typing the exact same formula fixes a problem. I see, often, situations where changing a field in a collection definition completely breaks everything and the only solution is to save, exit, edit again...and all is working!

These are still little annoyances that are there that you learn happen and know their signs and take the action needed. When I first started, I remember spending hours of time trying to fix an issue like that...finally put it to rest (saved and exited), came back later (edit) and it was all working fine.

Not saying the scenario you are seeing is that...but, just putting it out there for general knowledge.