Answered

Cannot access Lookup Fields in Classic UI - Unknown Entity Name

(0) Share

Report

Posted on by ZiaUddin

For some reason today, we were trying to access a lookup field through the Classic UI under a solution / Entity / Fields area, However, everytime we click on a lookup field - rather than bringing up is definition in a dialog it brings up a dialog window that is titled:

Unknown Entity Name

The entity name doesn't exist. Please specify an existing entity name.

In the modern UI, we can access the lookup field under the Data / Entities / Fields menu which tells the underlying definition but has no ability to set the field as a global filter for a dashboard.

Please advise if you can on this, and many thanks in advance.

Categories:

Microsoft Dataverse with Power Apps

All responses (4)

Answers (1)

Sort by

EricRegnier 8,720 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @ZiaUddin, are you still having this issue? Try to sign out, clear all your browser cache and then open the solution from make.powerapps.com --> Solutions --> select your solution --> click the "Switch to Classic" button in the command bar. Cheers
ZiaUddin 93 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Eric

I have tried this and have had no luck, I thought that maybe this was an issue with MS doing some sort of work in the background, and maybe it would turn to normal but so far still getting the same issue. It is only affecting one of our CDS Environments, we need to access the lookup fields to enable global filtering on our dashboards. Don't understand how this has happened.

Regards,
Zia
EricRegnier 8,720 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

If you’re still having this issue then I would suggest to raise a Microsoft Support Ticket at https://admin.powerplatform.microsoft.com/
cheers
Verified answer

ZiaUddin 93 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi All

Just wanted you to say that this issue has been resolved, we did nothing in the end - for some reason on Monday afternoon it had resolved itself - so I can only imagine the issue is related to those other popular posts regarding this problem, where it seems that MS are doing something in the background, which takes some time to resolve. However, have to say we have not done any upgrades or anything. The only thing I will say is that the night before I removed some calculated fields from an entity for which we did not define any calculations - but I have no idea if there was some obscure relationship.