Unanswered

Flows - Common Data Service (current) Connector

(0) Share

Report

Posted on by mcutchins

I am wondering why sometimes I can see the CDS (current) connector within my Flows and other times I can't. I would like to user the CDS (current) as it is recommended and has a connector I need to include within my Flow, but unsure why and when it appears within a Flow.

Flow A

Flow B

Anyone experience this and know how to get around the issue (besides reaching out to MS; that can take days to resolve)?

Thanks!

All responses (4)

Answers (0)

MJain 2,450 on at

Like (0)

Report

Re: Flows - Common Data Service (current) Connector

Hi @mcutchins ,

It is advised to use flows by creating solution first and then creating flows inside the solutions. This way you will always see CDS (current) connector available inside the flows which is recommended.

Thanks
Community Power Pla... on at

Like (0)

Report

Re: Flows - Common Data Service (current) Connector

it's depending on you connector settings "allowed" , "shared with other Connectors" or disallowed.

Based on the configuration , when the connector is not allowed to be used with others the connector vanish, when you have already connectors in your flow
mcutchins 83 on at

Like (0)

Report

Re: Flows - Common Data Service (current) Connector

So maybe the Flow that contains CDS (current) was based on a template from them?
Pstork1 65,946 Most Valuable Professional on at

Like (0)

Report

Re: Flows - Common Data Service (current) Connector

Its my understanding that the CDS (Current) connector is part of Project Oakdale and should only appear when you are creating flows inside the Teams client. If its appearing elsewhere then its an anomaly.