Showing results for 
Search instead for 
Did you mean: 
Frequent Visitor

Entity with fields visible from powerapps if with Dynanics 365 connector and not visible with the CDS connector

I developed a powerapps with a working 
Dynamics 365 connector. To improve
performance Microsoft suggested me to switch to CDS
and to put the CDS connector in place of
Dynamics, also because it could soon be
unsupported along with the rules.
Is it possible that entity fields I see them
visible from powerapps if with Dynamics 365
connector but not if I put the CDS connector?
P.S. I have enabled CDS
What could be the reason, what should I check
or what should I do.
Impactful Individual
Impactful Individual

So you are saying you have Entities in Dynamics that you cannot see with the CDS connector? For example, here I have Opportunities from my Sales app listed along my current environment entities, as well as some of the custom entities in my Dynamics environment.


Annotation 2019-12-11 155351.png

You are saying that you cannot see the Dynamics entities in this list?

Super User
Super User

I've attempted to 'update' an App from Dynamics to CDS connector - not a pleasant experience!

As far as I can see, you cannot see things like the IDs of related entities - a major problem if your app uses IDs (e.g. in Filters and LookUps). Also the handling of option sets is completely different (in Dynamics you have use the codes of the options, in CDS you can't see or use the codes of the options).

Moving from Dynamics to CDS is all or nothing - we tried having an App with a combination of Dynamics and CDS connections but they started interfering with each other (CDS entities kept appearing even though we kept removing them and when they appeared, formulas referencing the D365 version of the entity broke).

There are a number of known bugs in the CDS connector (spurious error messages about referencing AttachmentCount properties).

We have decided to hold off migrating until the CDS connector is more stable and we have lots of time available to rewrite most of the formulas in the Apps.

No, if for example your Opportunities 
has the fields: id, Name, description,
that you see on Dynamics you can't see for example one or more of one
of them on CDS.

Hi @BlackRos ,

Do you want to create an entity visible in dynamics365, while not visible in CDS ?

I'm afraid it's not supported in PowerApps currently.

You can not limit whether you could view the entity by choosing different data sources.

Usually, we set the data's permission on different account.

For example, make accountA could view entityA, accountB could view enityB.

And then, you could connect your app with dynamics365 by logging in accountA.

You could connect your app with CDS by logging in accountB.

(PowerApps could connect with data sources that loging in different accounts)

Here's a doc about how to assign different permission to users for your reference:



Best regards,

Community Support Team _ Phoebe Liu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

PA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

Power Query PA Forum 768x460.png

Check it out!

Did you know that you can visit the Power Query Forum in Power BI and now Power Apps

V3_PVA CAmpaign Carousel.png

Community Challenge - Giveaways!

Participate in the Power Virtual Agents Community Challenge

Carousel 2021 Release Wave 2 Plan 768x460.jpg

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

Users online (3,076)