Attach CDM Entity (not model.json) to Dataflow

[PaulBerg]

Attaching a model.json to a Dataflow works fine.

I have exported CDM entities to my ADLS Gen2. Output in the ADLS is a folder for the specific entity (in this case, Account) and a metadatafile: Account.cdm.json.

I cant find a way to create a dataflow against the Account.cdm.json file as it would seem the option to attach a CDM folder detects your input string to contain "model.json" and disables the button if you try to attach anything else than that.

Moving the entity from ADLS to Azure SQL DB using Data Factory works just fine though.

[v-alq-msft]

Hi, @PaulBerg 

Based on your description, I assume that you have managed to create a data flow with 'Import Model' and failed to create a dataflow with 'Attach a Common Data Model folder'.

You may refer to Dataflows and Azure Data Lake integration  and Export entity data to Azure Data Lake Storage Gen2 to see if they help. If it still doen't work, I'd like to suggest you open a support ticket here .

Best Regards

Allan

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[PaulBerg]

Thank you for the reply.

Clarification: Successfully managed to use attach a common data model folder using model.json
Failed to do so with Account.cdm.json

Using the model.json i have used "attach a common data model folder" pointed to my ADLS gen2. 

In this particular case the model.json is, as i can understand it, a model of several CDM entities and Dataflows can handle using that just fine.

In public preview right now is the ability to export single Entities or Tables (from D365FO) and from what i can see on the Microsoft CDM github the output files are in the format of "entityname.cdm.json" which cannot be attached using the above method.

I cant find any more detailed documentation of using single exported entities not part of a model for creating dataflows.