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
#Dyn365CE2021.04.23D365 CE: Error while importing solution “The datafieldname attribute ‘FieldName’ for control is not valid for create”
#Dyn365CE2020.10.18Azure Function: Web Deploy cannot modify the file on the Destination because it is locked by an external process
#Dyn365CE2020.09.15D365 CE: Error while activating BPF “An attribute with the specified name already exists. Exception Message: Column names in each table must be unique. Column name ‘stageid’ in table ‘EntityName’ is specified more than once.”
#Dyn365CE2020.06.16D365: Implement Try…Catch…Finally in PowerAutomate
