Today I was stuck in an uncomfortable situation.

I wrongly created a polymorphic relationship between 3 tables. Wrong for 2 different reasons: the name of the lookup field was wrong, and I also needed 2 tables more (the PACX command to add tables to an existing poly-lookup is not ready yet).

Not so bad, I thought. Let's delete it.

On make.powerapps.com I did the following:

1. Opened the solution where the table that contains the lookup column is defined.
2. Moved to Columns.
3. Selected the polymorphic lookup column and clicked on "Delete from this environment".

But it didn't worked: 😕

I also tried deleting the relationship before deleting the column:

1. Moved to Relationships
2. Selected one of the relationships composing the poly-lookup relation, and clicked on "Delete from this environment".

Same stuff... 😠

Then I tried again on the lookup column:

Now I got a different error 🤬

I'm already tired of headaches. Remembering about the recent threads about make.powerapps.com UI issues, I went by my favorite route.

PACX to the rescue! 💪🏻

Suddenly I remembered an old command I created to remove unwanted columns.

pacx column delete --table ava_presence --schemaName ava_relationshipid

And ✨ it worked like a charm ✨

The column and relationships are both been deleted successfully.

Conclusions

The Power Apps Maker portal is really powerful, but in terms of UI/UX it presents still a few issues that sometimes are tricky to identify and manage properly.

Fortunately for us, the tools provided by the open-source community (typically created by people who work day-by-day on the platform and understand its constraints and untapped potential) help us overcome these limitations, making us more effective and efficient.