After upgrading form Composite 4.1 => 4.2 Update 1 AND updating from XML => SQL.
We have a problem with one of our Datatype. This data type has a non optional Image field. If we try to add a new record (in composite) we get the following error:
FormCompileException:
The non optional binding Afbeelding is missing its binding value
```
FormCompileException:
The non optional binding Afbeelding is missing its binding value
Stack trace:
at Composite.C1Console.Forms.Foundation.FormTreeCompiler.CompilePhases.EvaluatePropertiesPhase.HandleProducerElement(ElementCompileTreeNode element, List`1 newProperties, String defaultOverloadPropertyName)
at Composite.C1Console.Forms.Foundation.FormTreeCompiler.CompilePhases.EvaluatePropertiesPhase.Evaluate(ElementCompileTreeNode node, List`1 newProperties, String defaultOverloadPropertyName)
at Composite.C1Console.Forms.Foundation.FormTreeCompiler.CompilePhases.EvaluatePropertiesPhase.Evaluate(ElementCompileTreeNode node, List`1 newProperties, String defaultOverloadPropertyName)
at Composite.C1Console.Forms.Foundation.FormTreeCompiler.CompilePhases.EvaluatePropertiesPhase.Evaluate(ElementCompileTreeNode node, List`1 newProperties, String defaultOverloadPropertyName)
at Composite.C1Console.Forms.FormTreeCompiler.Compile(XDocument doc, IFormChannelIdentifier channel, Dictionary`2 bindingObjects, Boolean withDebug, St
```
We solved our clients problem by making the image field optional (for now) But we like to have it non optional
Comments: ** Comment from web user: wysocki **
We have a problem with one of our Datatype. This data type has a non optional Image field. If we try to add a new record (in composite) we get the following error:
FormCompileException:
The non optional binding Afbeelding is missing its binding value
```
FormCompileException:
The non optional binding Afbeelding is missing its binding value
Stack trace:
at Composite.C1Console.Forms.Foundation.FormTreeCompiler.CompilePhases.EvaluatePropertiesPhase.HandleProducerElement(ElementCompileTreeNode element, List`1 newProperties, String defaultOverloadPropertyName)
at Composite.C1Console.Forms.Foundation.FormTreeCompiler.CompilePhases.EvaluatePropertiesPhase.Evaluate(ElementCompileTreeNode node, List`1 newProperties, String defaultOverloadPropertyName)
at Composite.C1Console.Forms.Foundation.FormTreeCompiler.CompilePhases.EvaluatePropertiesPhase.Evaluate(ElementCompileTreeNode node, List`1 newProperties, String defaultOverloadPropertyName)
at Composite.C1Console.Forms.Foundation.FormTreeCompiler.CompilePhases.EvaluatePropertiesPhase.Evaluate(ElementCompileTreeNode node, List`1 newProperties, String defaultOverloadPropertyName)
at Composite.C1Console.Forms.FormTreeCompiler.Compile(XDocument doc, IFormChannelIdentifier channel, Dictionary`2 bindingObjects, Boolean withDebug, St
```
We solved our clients problem by making the image field optional (for now) But we like to have it non optional
Comments: ** Comment from web user: wysocki **
Registered in HQ TFS as Issue #4742.
This occurs on both XML- and SQL-based sites. The following Data Reference field types seem to be affected:
* C1 Image File
* C1 Media File
* C1 Media Folder