locked
Import Schema in Dynamics 365 Dataset is not working RRS feed

  • Question

  • Hi Techie!

    I'm using Dynamics 365 as my DataSet. When I do "Import Schema" it's not showing up all columns in Dynamics 365 entity. Few columns are still missing. Can you please guide me here.

    Thanks

    Monday, September 16, 2019 5:04 PM

Answers

  • Hi Santhosh,

    This could potentially be a bug. While I work internally with the teams to check if it could be a bug, here's a workaround that can get you unblocked :

    • Add on any missing system or custom fields that are required as part of our import process using the New column button. When defining each field, it is important that the Name value is used for each field and that the correct data type is selected. The example screenshot below provides an example of all the possible field types that can be added on in this manner:
    • And, for those who prefer working with code, the JSON definition for a schema containing only these fields would look like this:
      • {
            "name": "CDS_Account",
            "properties": {
                "linkedServiceName": {
                    "referenceName": "CDSLinkedService",
                    "type": "LinkedServiceReference"
                },
                "folder": {
                    "name": "CDS"
                },
                "type": "DynamicsEntity",
                "structure": [
                    {
                        "name": "aging90",
                        "type": "Decimal",
                        "description": "D365CE Data Type = Currency"
                    },
                    {
                        "name": "overriddencreatedon",
                        "type": "DateTime",
                        "description": "D365CE Data Type = Date and Time"
                    },
                    {
                        "name": "exchangerate",
                        "type": "Decimal",
                        "description": "D365CE Data Type = Decimal Number"
                    },
                    {
                        "name": "address1_longitude",
                        "type": "Double",
                        "description": "D365CE Data Type = Floating Point Number"
                    },
                    {
                        "name": "entityimage",
                        "type": "String",
                        "description": "D365CE Data Type = Default Image. String must be Base64"
                    },
                    {
                        "name": "originatingleadid",
                        "type": "Guid",
                        "description": "D365CE Data Type = Lookup"
                    },
                    {
                        "name": "description",
                        "type": "String",
                        "description": "D365CE Data Type = Multiple Lines of Text"
                    },
                    {
                        "name": "customertypecode",
                        "type": "Int32",
                        "description": "D365CE Data Type = Option Set"
                    },
                    {
                        "name": "accountid",
                        "type": "Guid",
                        "description": "D365CE Data Type = Primary Key"
                    },
                    {
                        "name": "telephone1",
                        "type": "String",
                        "description": "D365CE Data Type = Single Line of Text"
                    },
                    {
                        "name": "statecode",
                        "type": "Int32",
                        "description": "D365CE Data Type = Status"
                    },
                    {
                        "name": "statuscode",
                        "type": "Int32",
                        "description": "D365CE Data Type = Status Reason"
                    },
                    {
                        "name": "versionnumber",
                        "type": "Int64",
                        "description": "D365CE Data Type = Time Stamp"
                    },
                    {
                        "name": "donotemail",
                        "type": "Boolean",
                        "description": "D365CE Data Type = Two Options"
                    },
                    {
                        "name": "stageid",
                        "type": "Guid",
                        "description": "D365CE Data Type = Unique Identifier"
                    },
                    {
                        "name": "opendeals",
                        "type": "Int32",
                        "description": "D365CE Data Type = Whole Number"
                    }
                ],
                "typeProperties": {
                    "entityName": "account"
                }
            },
            "type": "Microsoft.DataFactory/factories/datasets"
        }

    Ref - https://community.dynamics.com/crm/b/crmchap/posts/working-with-custom-dynamics-365-customer-engagement-dataset-schemas-in-azure-data-factory-v2

    Hope this helps.

    Tuesday, September 17, 2019 6:23 AM

All replies

  • Hi Santhosh,

    This could potentially be a bug. While I work internally with the teams to check if it could be a bug, here's a workaround that can get you unblocked :

    • Add on any missing system or custom fields that are required as part of our import process using the New column button. When defining each field, it is important that the Name value is used for each field and that the correct data type is selected. The example screenshot below provides an example of all the possible field types that can be added on in this manner:
    • And, for those who prefer working with code, the JSON definition for a schema containing only these fields would look like this:
      • {
            "name": "CDS_Account",
            "properties": {
                "linkedServiceName": {
                    "referenceName": "CDSLinkedService",
                    "type": "LinkedServiceReference"
                },
                "folder": {
                    "name": "CDS"
                },
                "type": "DynamicsEntity",
                "structure": [
                    {
                        "name": "aging90",
                        "type": "Decimal",
                        "description": "D365CE Data Type = Currency"
                    },
                    {
                        "name": "overriddencreatedon",
                        "type": "DateTime",
                        "description": "D365CE Data Type = Date and Time"
                    },
                    {
                        "name": "exchangerate",
                        "type": "Decimal",
                        "description": "D365CE Data Type = Decimal Number"
                    },
                    {
                        "name": "address1_longitude",
                        "type": "Double",
                        "description": "D365CE Data Type = Floating Point Number"
                    },
                    {
                        "name": "entityimage",
                        "type": "String",
                        "description": "D365CE Data Type = Default Image. String must be Base64"
                    },
                    {
                        "name": "originatingleadid",
                        "type": "Guid",
                        "description": "D365CE Data Type = Lookup"
                    },
                    {
                        "name": "description",
                        "type": "String",
                        "description": "D365CE Data Type = Multiple Lines of Text"
                    },
                    {
                        "name": "customertypecode",
                        "type": "Int32",
                        "description": "D365CE Data Type = Option Set"
                    },
                    {
                        "name": "accountid",
                        "type": "Guid",
                        "description": "D365CE Data Type = Primary Key"
                    },
                    {
                        "name": "telephone1",
                        "type": "String",
                        "description": "D365CE Data Type = Single Line of Text"
                    },
                    {
                        "name": "statecode",
                        "type": "Int32",
                        "description": "D365CE Data Type = Status"
                    },
                    {
                        "name": "statuscode",
                        "type": "Int32",
                        "description": "D365CE Data Type = Status Reason"
                    },
                    {
                        "name": "versionnumber",
                        "type": "Int64",
                        "description": "D365CE Data Type = Time Stamp"
                    },
                    {
                        "name": "donotemail",
                        "type": "Boolean",
                        "description": "D365CE Data Type = Two Options"
                    },
                    {
                        "name": "stageid",
                        "type": "Guid",
                        "description": "D365CE Data Type = Unique Identifier"
                    },
                    {
                        "name": "opendeals",
                        "type": "Int32",
                        "description": "D365CE Data Type = Whole Number"
                    }
                ],
                "typeProperties": {
                    "entityName": "account"
                }
            },
            "type": "Microsoft.DataFactory/factories/datasets"
        }

    Ref - https://community.dynamics.com/crm/b/crmchap/posts/working-with-custom-dynamics-365-customer-engagement-dataset-schemas-in-azure-data-factory-v2

    Hope this helps.

    Tuesday, September 17, 2019 6:23 AM
  • Hi Santhosh,

    Just wanted to check - was the above suggestion helpful to you? If yes, please consider upvoting and/or marking it as answer. This would help other community members reading this thread.

    Monday, September 23, 2019 8:25 AM