I've been encountering some unusual behavior when working with Umbraco and initializing my data types using $scope.model.value
.
My custom data type in Umbraco 7.11.1 is based on a complex JSON data model. When I save and publish from the back office, everything seems fine - no error messages or console errors.
However, upon reloading the back office, Umbraco appears to initialize my data type with a partial, malformed JSON string instead of the expected JSON object that was previously saved.
I'm following the standard process for implementing a custom data type through an AngularJS controller:
angular.module('umbraco')
.controller('MyDataType', ['$scope', function ($scope) {
var loadedData = $scope.model.value;
// Working with "loadedData"
$scope.model.value = loadedData;
}])
This issue seems to arise when there is a large amount of data in my JSON model (around 150 characters or more).
Could there be a limit to the data storage capacity for Umbraco data types? Is there something else I might be missing?