When entities in a dataflow are mapped to a Common Data Model standard entity, such as Account, the version of that standard entity is included in the dataflow definition (model.json). Existing versions of the Common Data Model standard entities will persist unchanged, so existing dataflows won't be affected. If you'd like to leverage new versions of the Common Data Model standard entities, you can edit existing dataflows, but your changes might affect reports and dashboards that use the dataflow.
Workaround for this is to create Common Data Model manifest file and try changing "jsonSchemaSemanticVersion"
To create Common Data Model manifest file refer this article
Sample code -
{
"jsonSchemaSemanticVersion": "1.0.15",
"imports": [],
"manifestName": "clickstream",
"explanation": "CDM standard entities",
"entities": [{
"type": "LocalEntity",
"entityName": "ReverseIp",
"entityPath": "ReverseIp.cdm.json/ReverseIp"
},
{
"type": "LocalEntity",
"entityName": "Session",
"entityPath": "Session.cdm.json/Session"
},
{
"type": "LocalEntity",
"entityName": "UserAgent",
"entityPath": "UserAgent.cdm.json/UserAgent"
}
]
}
For more information - ADF Adds Support for Inline Datasets and Common Data Model to Data Flows