Recently, while importing a solution to target instance, we got an error saying “The datafieldname attribute sab_disablerecordon for control is not valid for create” and the solution import failed.
After investigating this issue, we figured out that in the source environment, the field ” sab_disablerecordon ” was used on Quick create form for that entity. Also, this field is a calculated…
Continue Reading Ajit Patra’s Article on their blog
D365 CE: Error while importing solution “The datafieldname attribute ‘FieldName’ for control is not valid for create”
Recently, while importing a solution to target instance, we got an error saying “The datafieldname attribute sab_disablerecordon for control is not valid for create” and the solution import failed. After investigating this issue, we figured out that in the source environment, the field ” sab_disablerecordon ” was used on Quick create form for that entity….
Blog Syndicated with Ajit Patra’s Permission
More About This Author
Array
Dyn365CE16 August 2021[Limitation]PowerAutomate: Unable to use Custom Connector with actions having parameterized GET requests. Error: “Fix Invalid expression(s) for the input parameter(s) of operation ‘ActionName'”.
Dyn365CE16 August 2021Dataverse: Create Custom API and Implement using plugin C#
Dyn365CE11 June 2021Microsoft Teams Integration with D365 on custom entity
Dyn365CE10 June 2021D365: Why my Power Automates are not being triggered
