Answered

Cannot delete Lookup field

(0) Share

Report

Posted on by mcorning

332

My entity is in the Twilight Zone. A few weeeks ago i was experimenting (unsuccessfully) with Lookup fields that took a reference to Lookup Entities. Today, i tried to clean up those experiments by removing the Lookup Entity and its fields in dependent Entities.

However, since i believe this old Lookup field type is obsolete (it no longer appears as a possible data type), the editor doesn't know what to do the field. After i select the Lookup field and try to delete it, nothing happens (except that Delete gets highlighted.

Delete doesn't

so i suspect my best option for this and any other similar situatioin, is to replace the dependent Entity and refer to custom Picklists instead of Lookup fields (as soon as i can get custom Picklists to behave themselves). yes?

Categories:

Building Power Apps

I have the same question (0)

All responses (2)

Answers (2)

Verified answer

mcorning 332 on at

Like (0)

Report
Copy link

Link copied!

I think my assessment above is rather inaccurate, if not misleading. Lookup fields have not perished from the earth. It just looks like it. And you cannot delete them in the Fields UI because you didn't create them, CDS did; so the only way to get rid of them is to remove the Relation to another entity that created the Lookup field in the first place.

So i will mark this post as the Solution to my original question.

I have posted related information and new questions in another post in this Forum under the Subject: LookUp fields in use cases other than editing.

Was this reply helpful? Yes No
Verified answer

mcorning 332 on at

Like (0)

Report
Copy link

Link copied!

More apologies. A mystery remains. The problem with my current entity that holds a Lookup field is that...there is no parent entity in the Relations view.

I should note that i used this table reference technique at a time that preceeded my knowledge of support for custom Picklists.

Anyway, to make matters worse, when i try to remove the LookupDementiaDiagnosis table (that was going to provide the value to the lookup field), i get this (expected) exception:

Catch-22
So I cannot delete the field, so i cannot delete the table. I can delete the Dementia Diagnosis table, and if that was the only entity dependent on the Lookup entity, I'd be happy...but since i duplicated the Dementia Diagnosis entity so that I could successfully change three fields from Text to custom Picklists, I still cannot remove the Lookup table...and so it goes.

Bottom line: I will delete Dementia Diagnosis2 so that i can delete LookupDementiaDiagnosis. Then i will manually reproduce the Dementia Diagnosis entity using custom Picklists. whew.

Now this will be the Solution post.

Was this reply helpful? Yes No