Then instead of selecting an existing object from the library, you select "Create" and create a new object, Formtools sets the UUID value of the newly created object in a hidden form field. However, there is a comma prepended to the UUID (see attached screenshot, note the Firebug output, you can see the hidden field with the comma prepended to the UUID. This gets saved to the database and when the user returns to the objectAdmin, there is an error because it just assumes that data will be a UUID and does not do any validation.
So somewhere in the library picker Javascript there is a comma getting added to those objects created using the "Create" button.
Environment
None
Attachments
1
Activity
Show:
Sean Coyne February 11, 2011 at 9:31 PM
I just realized now that its not just Extended Arrays.
We have a UUID property that has ftAllowCreate="true" and when our users "Create" from the parent object edit form, it also prepends the comma.
I have tested array properties and it did not show this behavior, so rather than an Extended Array problem, perhaps its a UUID problem when creating them using the "Create" button for the library formtool?
If you have an extended array, and you create an edit.cfm webskin and use formtools to manage the "data" property like so:
<ft:object stObject="#stobj#" IncludeFieldSet="true" legend="Registration" lfields="parentId,data" />
Then instead of selecting an existing object from the library, you select "Create" and create a new object, Formtools sets the UUID value of the newly created object in a hidden form field. However, there is a comma prepended to the UUID (see attached screenshot, note the Firebug output, you can see the hidden field with the comma prepended to the UUID. This gets saved to the database and when the user returns to the objectAdmin, there is an error because it just assumes that data will be a UUID and does not do any validation.
So somewhere in the library picker Javascript there is a comma getting added to those objects created using the "Create" button.